jiebi/CodeConvo huggingface dataset:
Change:
app.kubernetes.io/name: load-balancer-example spec: containers: <del> - image: gcr.io/google-samples/node-hello:1.0 </del> <ins> - image: us-docker.pkg.dev/google-samples/containers/gke/hello-app:2.0 </ins> name: hello-world ports: - containerPort: 8080

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: While following the Kubernetes tutorial on exposing an external IP address at , using the command results in an error. The error message indicates a failure to pull the Docker image due to deprecated image format: This issue prevents the tutorial from being completed as described. Proposed Solution: Update the tutorial page to use a newer version of the Docker image that complies with the current Docker Image specifications (OCI Format or Docker Image manifest v2, schema 2). Alternatively, provide a note or warning about this issue with guidance on how to proceed or troubleshoot this specific deprecation issue. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
The image going to be deprecated. so the example has to be updated !
So, what can be the alternate image to use?
This issue might be fixed similar to , I'm happy to draft a PR if no one was working on it already.
Change:
Workarounds: <del> * Regularly [back up etcd](https://coreos.com/etcd/docs/latest/admin_guide.html). The </del> <ins> * Regularly [back up etcd](https://etcd.io/docs/v3.5/op-guide/recovery/). The </ins> etcd data directory configured by kubeadm is at `/var/lib/etcd` on the control-plane node. * Use multiple control-plane nodes. You can read

Discussion:
Problem: The text on is not working, it should point to this Check the page for the problem. Page to Update: Suggested Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the text back up etcd link to and not to this . /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on is not working, it should point to this Check the page for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the text back up etcd link to and not to this . /assign /language en Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
The suggested solution is incorrect because Kubernetes uses etcd v3 and we should not link to etcd v2 docs
Change:
[CoreOS](http://coreos.com) templates for CloudStack are built [nightly](http://stable.release.core-os.net/amd64-usr/current/). CloudStack operators need to [register](http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/templates.html) this template in their cloud before proceeding with these Kubernetes deployment instructions. This guide uses an [Ansible playbook](https://github.com/runseb/ansible-kubernetes). <del> This is a completely automated, a single playbook deploys Kubernetes based on the coreOS [instructions](/docs/getting-started-guides/coreos/coreos_multinode_cluster). </del> <ins> This is completely automated, a single playbook deploys Kubernetes. </ins> This [Ansible](http://ansibleworks.com) playbook deploys Kubernetes on a CloudStack based Cloud using CoreOS images. The playbook, creates an ssh key pair, creates a security group and associated rules and finally starts coreOS instances configured via cloud-init.

Discussion:
A user linked to this guide from an issue: I believe that guide is unmaintained. It still specifies k8s 1.1.2. can we delete?
Thank you. Yes, this guide was unmaintained and community contributed. I am OK with this change. devin-donnelly wrote:
Change:
$($(CertUtil -hashfile .kubectl-convert.exe SHA256)[1] -replace " ", "") -eq $(type .kubectl-convert.exe.sha256) ``` <del> 1. Add the binary in to your `PATH`. </del> <ins> 1. Append or prepend the kubectl binary folder to your `PATH` environment variable. </ins> 1. Verify plugin is successfully installed

Discussion:
Hello, I have recently and I have noticed that there is a slight error at step 3. Namely, the line says: when it really should be: I have tested it a few times and indeed, adding to PATH does not work, while simply adding yields the correct result (i.e. being able to invoke kubectl commands from the command prompt). I know it is a minor issue but for beginners (like myself) it could make the difference between completing the installation or not. Even though I have not tried other methods of installation, I suspect that the same step should also be corrected in section , where it also says "Add the binary in to your PATH." Best regards, Paula
/triage accepted Similar issue exists in . cf. In : !
is kind of techie vernacular (it's how I'd say it in spoken English to a colleague), but in technical docs we can be more precise. /language en
Hi, I would like to work on this issue. /assign
/sig windows
Change:
{{- end -}} <div id="frameHolder"> {{ if ( .Get "category" ) }} <del> <iframe frameborder="0" id="landscape" scrolling="no" src="https://landscape.cncf.io/category={{ .Get "category" }}&format=logo-mode&grouping=category&embed=yes" style="width: 1px; min-width: 100%"></iframe> </del> <ins> <iframe frameborder="0" id="landscape" scrolling="no" src="https://landscape.cncf.io/category={{ .Get "category" }}&format=card-mode&grouping=category&embed=yes" style="width: 1px; min-width: 100%"></iframe> </ins> {{ else }} <del> <iframe frameborder="0" id="landscape" scrolling="no" src="https://landscape.cncf.io/format=logo-mode;embed=yes" style="width: 1px; min-width: 100%" title="CNCF Landscape"></iframe> </del> <ins> <iframe frameborder="0" id="landscape" scrolling="no" src="https://landscape.cncf.io/format=card-mode;embed=yes" style="width: 1px; min-width: 100%" title="CNCF Landscape"></iframe> </ins> {{ end }} <script src="https://landscape.cncf.io/iframeResizer.js"></script> </div>

Discussion:
Some solutions are repeted in the list
/triage accepted It is not the solutions that are repeated. It is the icon. This worth a fix. /assign
Change:
<ins> --- title: 拡張リソースをコンテナに割り当てる content_type: task weight: 40 --- <!-- overview --> {{< feature-state state="stable" >}} このページでは、拡張リソースをコンテナに割り当てる方法について説明します。 ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} この練習を始める前に、[Nodeに拡張リソースをアドバタイズする](/ja/docs/tasks/administer-cluster/extended-resource-node/)の練習を行ってください。これにより、Nodeの1つがドングルリソースをアドバタイズするように設定されます。 <!-- steps --> ## 拡張リソースをPodに割り当てる 拡張リソースをリクエストするには、コンテナのマニフェストに`resources:requests`フィールドを含めます。拡張リソースは、`*.kubernetes.io/`以外の任意のドメインで完全修飾されます。有効な拡張リソース名は、`example.com/foo`という形式になります。ここで、`example.com`はあなたの組織のドメインで、`foo`は記述的なリソース名で置き換えます。 1つのコンテナからなるPodの構成ファイルを示します。 {{< codenew file="pods/resource/extended-resource-pod.yaml" >}} 構成ファイルでは、コンテナが3つのdongleをリクエストしていることがわかります。 次のコマンドでPodを作成します。 ```shell kubectl apply -f https://k8s.io/examples/pods/resource/extended-resource-pod.yaml ``` Podが起動したことを確認します。 ```shell kubectl get pod extended-resource-demo ``` Podの説明を表示します。 ```shell kubectl describe pod extended-resource-demo ``` dongleのリクエストが表示されます。 ```yaml Limits: example.com/dongle: 3 Requests: example.com/dongle: 3 ``` ## 2つ目のPodの作成を試みる 以下に、1つのコンテナを持つPodの構成ファイルを示します。コンテナは2つのdongleをリクエストします。 {{< codenew file="pods/resource/extended-resource-pod-2.yaml" >}} Kubernetesは、2つのdongleのリクエストを満たすことができません。1つ目のPodが、利用可能な4つのdongleのうち3つを使用してしまっているためです。 Podを作成してみます。 ```shell kubectl apply -f https://k8s.io/examples/pods/resource/extended-resource-pod-2.yaml ``` Podの説明を表示します。 ```shell kubectl describe pod extended-resource-demo-2 ``` 出力にはPodがスケジュールできないことが示されます。2つのdongleが利用できるNodeが存在しないためです。 ``` Conditions: Type    Status PodScheduled  False ... Events: ... ... Warning   FailedScheduling  pod (extended-resource-demo-2) failed to fit in any node fit failure summary on nodes : Insufficient example.com/dongle (1) ``` Podのステータスを表示します。 ```shell kubectl get pod extended-resource-demo-2 ``` 出力には、Podは作成されたものの、Nodeにスケジュールされなかったことが示されています。PodはPending状態になっています。 ```yaml NAME                       READY     STATUS    RESTARTS   AGE extended-resource-demo-2   0/1       Pending   0          6m ``` ## クリーンアップ この練習で作成したPodを削除します。 ```shell kubectl delete pod extended-resource-demo kubectl delete pod extended-resource-demo-2 ``` ## {{% heading "whatsnext" %}} ### アプリケーション開発者向け * [コンテナおよびPodへのメモリーリソースの割り当て](/ja/docs/tasks/configure-pod-container/assign-memory-resource/) * [コンテナおよびPodへのCPUリソースの割り当て](/ja/docs/tasks/configure-pod-container/assign-cpu-resource/) ### クラスター管理者向け * [Nodeに拡張リソースをアドバタイズする](/ja/docs/tasks/administer-cluster/extended-resource-node/) </ins>

Discussion:
This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign
/close
Closing this issue. <detailsIn response to : /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Change:
}] } <del> <!-- 1.  Generate the key and certificate for the API server, which are by default saved into file `server-key.pem` and `server.pem` respectively: --> 1.  为 API 服务器生成秘钥和证书，默认会分别存储为`server-key.pem` 和 `server.pem` 两个文件。 </del> <ins> <!-- 7.  Generate the key and certificate for the API server, which are by default saved into file `server-key.pem` and `server.pem` respectively: --> 7.  为 API 服务器生成秘钥和证书，默认会分别存储为`server-key.pem` 和 `server.pem` 两个文件。 </ins> ../cfssl gencert -ca=ca.pem -ca-key=ca-key.pem  --config=ca-config.json -profile=kubernetes 

Discussion:
Link to The secondary list elements in the page are all "1." , they are not in order, it looks weird
/sig docs
Hi can you please elaborate which page are you talking about?
Sorry, I forgot to check the link in my issue, the correct link is
/language zh /triage accepted /retitle [zh] Wrong list numbering in page FYI: Page to update: page: file:
/assign
/assign
This fixes this issue.
please avoid assigning yourself to a issue that is already assigned to somebody else.
Change:
<ins> apiVersion: v1 kind: Pod metadata: name: volume-test spec: containers: - name: container-test image: busybox:1.28 volumeMounts: - name: all-in-one mountPath: "/projected-volume" readOnly: true volumes: - name: all-in-one projected: sources: - secret: name: mysecret items: - key: username path: my-group/my-username - downwardAPI: items: - path: "labels" fieldRef: fieldPath: metadata.labels - path: "cpu_limit" resourceFieldRef: containerName: container-test resource: limits.cpu - configMap: name: myconfigmap items: - key: config path: my-group/my-config </ins>

Discussion:
This is a Feature Request What would you like to be Localize to Spanish Why is this needed Comments /triage accepted /kind feature /language es /sig docs
Hi Rodolfo, I will take it!
/assign
algún avance al respecto?
disculpa. Lo terminaré hoy, gracias por recordarmenlo Victor.
Change:
| `WinOverlay` | `false` | Alpha | 1.14 | 1.19 | | `WinOverlay` | `true` | Beta | 1.20 | | | `WindowsEndpointSliceProxying` | `false` | Alpha | 1.19 | 1.20 | <del> | `WindowsEndpointSliceProxying` | `true` | beta | 1.21 | | </del> <ins> | `WindowsEndpointSliceProxying` | `true` | Beta | 1.21 | | </ins> {{< /table >}} ### Feature gates for graduated or deprecated features

Discussion:
Problem: Incorrect stage values in FeatureGate documentation LegacyNodeRoleBehavior has a stage of as of 1.19, which is not a valid stage. WindowsEndpointSliceProxying has a stage of as of 1.21; all other stage values are capitalized. Feature Until -- -- LegacyNodeRoleBehavior 1.19 WindowsEndpointSliceProxying Proposed Solution: Correct Stage text for listed FeatureGates Page to Update:
~That's not what I see on that page. Can you include a screenshot and confirm the URL you're viewing ?~ ~If possible, it'd be useful to see the HTTP headers that go with the page you screenshotted.~ I see it!
/triage accepted /language en /priority backlog /help
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /triage accepted /language en /priority backlog /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Thanks
Is the change for from to , to and add to ?
AIUI the change for is: change the column from to and the change for is: change the column from to no other changes needed
Change:
Whether this container should allocate a TTY for itself, also requires 'stdin' to be true. Default is false. <del> ### Not allowed {#Not allowed} </del> <ins> ### Not allowed {#Not-allowed} </ins> - **ports** ([]ContainerPort)

Discussion:
This is a Bug Report The issue is outlined in:
/triage accepted
/kind cleanup
Hi Thanks for opening a PR to fix this issue! /assign
Change:
* Learn more about [ownership of Kubernetes objects](/docs/concepts/overview/working-with-objects/owners-dependents/). * Learn more about Kubernetes [finalizers](/docs/concepts/overview/working-with-objects/finalizers/). <del> * Learn about the [TTL controller](/docs/concepts/workloads/controllers/ttlafterfinished/) (beta) that cleans up finished Jobs. </del> <ins> * Learn about the [TTL controller](/docs/concepts/workloads/controllers/ttlafterfinished/) that cleans up finished Jobs. </ins>

Discussion:
This is a Bug Report <!--Required Information--Problem: The feature gate is Stable (GA) in k8s v1.24 (see ) but it is mentioned as under the section in the following line: Proposed Solution: Remove . It should be instead of Page to Update:
/sig docs
/assign
Fixed it here:
/triage accepted
Change:
{{< feature-state for_k8s_version="v1.15" state="stable" >}} <del> Client certificates generated by [kubeadm](/docs/reference/setup-tools/kubeadm/) expire after 1 year. This page explains how to manage certificate renewals with kubeadm. </del> <ins> Client certificates generated by [kubeadm](/docs/reference/setup-tools/kubeadm/) expire after 1 year. This page explains how to manage certificate renewals with kubeadm. It also covers other tasks related to kubeadm certificate management. </ins> ## {{% heading "prerequisites" %}}

Discussion:
The command only has Cobra (CLI) documentation and there are no pointers on what fields are relevant in the configuration passed with --config to it: Add a minimal example + config for the command usage on this page: /sig cluster-lifecycle /kind feature xref
/triage accepted
/language en
Change:
<ins> --- title: Kubernetes 中的代理 --- {% capture overview %} 本文讲述了 Kubernetes 中所使用的代理。 {% endcapture %} {% capture body %} ## 代理 用户在使用 Kubernetes 的过程中可能遇到几种不同的代理（proxy）： 1. [kubectl proxy](/docs/tasks/access-application-cluster/access-cluster/#directly-accessing-the-rest-api)： - 运行在用户的桌面或 pod 中 - 从本机地址到 Kubernetes apiserver 的代理 - 客户端到代理使用 HTTP 协议 - 代理到 apiserver 使用 HTTPS 协议 - 指向 apiserver - 添加认证头信息 1. [apiserver proxy](/docs/tasks/access-application-cluster/access-cluster/#discovering-builtin-services)： - 是一个建立在 apiserver 内部的“堡垒” - 将集群外部的用户与群集 IP 相连接，这些IP是无法通过其他方式访问的 - 运行在 apiserver 进程内 - 客户端到代理使用 HTTPS 协议 (如果配置 apiserver 使用 HTTP 协议，则使用 HTTP 协议) - 通过可用信息进行选择，代理到目的地可能使用 HTTP 或 HTTPS 协议 - 可以用来访问 Node、 Pod 或 Service - 当用来访问 Service 时，会进行负载均衡 1. [kube proxy](/docs/concepts/services-networking/service/#ips-and-vips)： - 在每个节点上运行 - 代理 UDP 和 TCP - 不支持 HTTP - 提供负载均衡能力 - 只用来访问 Service 1. apiserver 之前的代理/负载均衡器： - 在不同集群间的存在形式和实现不同 (如 nginx) - 位于所有客户端和一个或多个 apiserver 之间 - 存在多个 apiserver 时，扮演负载均衡器的角色 1. 外部服务的云负载均衡器： - 由一些云供应商提供 (如AWS ELB、 Google Cloud Load Balancer) - Kubernetes service 为 `LoadBalancer` 类型时自动创建 - 只使用 UDP/TCP 协议 - 不同云供应商的实现不同。 Kubernetes 用户通常只需要关心前两种类型的代理，集群管理员通常需要确保后面几种类型的代理设置正确。 ## 请求重定向 代理已经取代重定向功能，重定向已被弃用。 {% endcapture %} {% include templates/concept.md %} </ins>

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: The bullet points nested under numbered list aren't rendered as bulleted list: <img width="869" alt="screen shot 2017-06-10 at 2 15 49 pm" src="https://user-"Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
The sub-link isn't correct either. For example, kubectl proxy links to but should instead link to I guess it's because is split from () /assign
Change:
are certain circumstances where two jobs might be created, or no job might be created. We attempt to make these rare, but do not completely prevent them. Therefore, jobs should be _idempotent_. <del> The job is responsible for retrying pods, parallelism among pods it creates, and determining the success or failure of the set of pods. A cron job does not examine pods at all. </del> <ins> If `startingDeadlineSeconds` is set to a large value or left unset (the default) and if `concurrentPolicy` is set to `AllowConcurrent`, the jobs will always run at least once. Jobs may fail to run if the CronJob controller is not running or broken for a span of time from before the start time of the CronJob to start time plus `startingDeadlineSeconds`, or if the span covers multiple start times and `concurrencyPolicy` does not allow concurrency. For example, suppose a cron job is set to start at exactly `08:30:00` and its `startingDeadlineSeconds` is set to 10, if the CronJob controller happens to be down from `08:29:00` to `08:42:00`, the job will not start. Set a longer `startingDeadlineSeconds` if starting later is better than not starting at all. The job is only responsible for creating Jobs that match its schedule, and the the Job in turn is responsible for the management of the Pods it represents. </ins> ## Writing a Cron Job Spec

Discussion:
This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: Section "Cron Job Limitations" in is confusing to users. It says: The about is confusing to users. Proposed Solution: A more specific description would be as follows: If startingDeadlineSeconds is set to a large value or unset (the default) and if concurrencyPolicy is AllowConcurrent, then your jobs will always run at least once. Jobs may fail to run if the Cron Controller (part of the kubernetes master) is not running or broken for a span of time from before the start time of the job to start time plus , or if the span covers multiple start times and does not allow concurrency. For example, if you say that your cron job has to start at exactly 08:30:00 and startingDeadlineSeconds is 10, and the , and your cron controller happens to be down from 08:29:00 to 08:42:00, then the job will not start. Set a longer if starting later is better than not starting at all. Page to Update:
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Change:
| kube-etcd                     | etcd-ca                   |                | server, client   | `<hostname>`, `<Host_IP>`, `localhost`, `127.0.0.1` | | kube-etcd-peer                | etcd-ca                   |                | server, client   | `<hostname>`, `<Host_IP>`, `localhost`, `127.0.0.1` | | kube-etcd-healthcheck-client  | etcd-ca                   |                | client           |                                                     | <del> | kube-apiserver-etcd-client    | etcd-ca                   | system:masters | client           |                                                     | </del> <ins> | kube-apiserver-etcd-client    | etcd-ca                   |                | client           |                                                     | </ins> | kube-apiserver                | kubernetes-ca             |                | server           | `<hostname>`, `<Host_IP>`, `<advertise_IP>`, `[1]`  | | kube-apiserver-kubelet-client | kubernetes-ca             | system:masters | client           |                                                     | | front-proxy-client            | kubernetes-front-proxy-ca |                | client           |                                                     |

Discussion:
According to the documentation, the certificate requires , but how can it be needed if etcd doesn't take this into account? Perhaps should be removed for the certificate and then I can create an issue on the kubeadm repo like like I created earlier.
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Page related to issue: /language en
/retitle Inconsistency in doc for kube-apiserver-etcd-client Certificate requirement /sig cluster-lifecycle
/sig api-machinery auth
+1 PRs welcome thanks
sorry but I don't understand what do you mean — just agreement or confirmation about what should be done? :) You seem to confirm that is indeed not required in the certificate, but I'm not sure because there are still no updates in the issue and the documentation is still not changed. So, I can't figure out if I should create an issue in the kubeadm repository.
yes, you can log the issue in k/kubeadm. in terms of updating the docs, i said "prs welcome", thus if you l'd like to help us you can send the docs change / pull request.