jiebi/CodeConvo huggingface dataset:
Change:
Helm Charts repository ( ) is obsolete. This sentence should be removed or updated. might be appropriate.
If this issue is validated, may I take this up?
/triage accepted
/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 : /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
/language en
/assign

Discussion:
* Learn more about [debugging a StatefulSet](/docs/tasks/debug-application-cluster/debug-stateful-set/). * Learn more about [deleting a StatefulSet](/docs/tasks/run-application/delete-stateful-set/). * Learn more about [force deleting StatefulSet Pods](/docs/tasks/run-application/force-delete-stateful-set-pod/). <del> * Look in the [Helm Charts repository](https://github.com/kubernetes/charts) </del> <ins> * Look in the [Helm Charts repository](https://artifacthub.io/) </ins> for other stateful application examples.
Change:
This link "" appears to be broken in the line: " <your-registry-serveris your Private Docker Registry FQDN. ( for DockerHub) "
According to , the V1 API has been deprecated.
/triage accepted /assign

Discussion:
This page shows how to create a Pod that uses a Secret to pull an image from a private Docker registry or repository. ## {{% heading "prerequisites" %}} * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} * To do this exercise, you need a [Docker ID](https://docs.docker.com/docker-id/) and password. <!-- steps --> ## Log in to Docker

where: <del> * `<your-registry-server>` is your Private Docker Registry FQDN. (https://index.docker.io/v1/ for DockerHub) </del> <ins> * `<your-registry-server>` is your Private Docker Registry FQDN. Use `https://index.docker.io/v2/` for DockerHub. </ins> * `<your-name>` is your Docker username. * `<your-pword>` is your Docker password. * `<your-email>` is your Docker email.

``` To pull the image from the private registry, Kubernetes needs credentials. <del> The `imagePullSecrets` field in the configuration file specifies that Kubernetes should get the credentials from a Secret named `regcred`. </del> <ins> The `imagePullSecrets` field in the configuration file specifies that Kubernetes should get the credentials from a Secret named `regcred`. </ins> Create a Pod that uses your Secret, and verify that the Pod is running:

kubectl get pod private-reg ``` ## {{% heading "whatsnext" %}} * Learn more about [Secrets](/docs/concepts/configuration/secret/). * Learn more about [using a private registry](/docs/concepts/containers/images/#using-a-private-registry). * Learn more about [adding image pull secrets to a service account](/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account).

* See [Secret](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#secret-v1-core). * See the `imagePullSecrets` field of [PodSpec](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podspec-v1-core).
Change:
Under the Backgrounds section, there's this paragraph: I'm wondering about the last sentence: 'When a pod ceases to exist, the volume is destroyed.' Is that correct? An ephemeral volume may be destroyed, but a persistent volume should exist beyond the lifetime of a pod by definition.
/triage accepted The description is inconsistent.
/kind bug /priority backlog /language en
/assign
Thanks for fixing this!

Discussion:
can use any number of volume types simultaneously. Ephemeral volume types have a lifetime of a pod, but persistent volumes exist beyond the lifetime of a pod. Consequently, a volume outlives any containers <del> that run within the pod, and data is preserved across container restarts. When a pod ceases to exist, the volume is destroyed. </del> <ins> that run within the pod, and data is preserved across container restarts. When a pod ceases to exist, Kubernetes destroys ephemeral volumes; however, Kubernetes does not destroy persistent volumes. </ins> At its core, a volume is just a directory, possibly with some data in it, which is accessible to the containers in a pod. How that directory comes to be, the
Change:
Ingress Ingress Minikube hellow- hellow- typohellow
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

Discussion:
If you are running Minikube locally, you can visit hello-world.info from your browser. --> {{< note >}} <del> 如果你在使用本地 Minikube 环境，你可以从浏览器中访问 hellow-world.info。 </del> <ins> 如果你在使用本地 Minikube 环境，你可以从浏览器中访问 hello-world.info。 </ins> {{< /note >}} <!--

--> {{< note >}} 如果你在本地运行 Minikube 环境，你可以使用浏览器来访问 <del> hellow-world.info 和 hello-world.info/v2。 </del> <ins> hello-world.info 和 hello-world.info/v2。 </ins> {{< /note >}} ## {{% heading "whatsnext" %}}
Change:
Katacoda doesn’t work. Minikube doesn’t work. Is there a good, official, tutorial that does work? Or that is “printed” only without requiring finicky interactive stuff that never works?
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
I tested following the instructions, using Katacoda to host the cluster. I noticed a missing detail. Before you run , you should open a new terminal, start there, and then switch back to the main terminal. Alternatively, we could rely on shell process management and have the reader run . This doesn't work on Windows though. Would you be willing to revise the issue description to include these details I discovered
I didn't have any luck with it on any of several browsers I tried. It failed out on all of them.

Discussion:
{{< kat-button >}} {{< note >}} <del> If you installed minikube locally, run `minikube start`. </del> <ins> If you installed minikube locally, run `minikube start`. Before you run `minikube dashboard`, you should open a new terminal, start `minikube dashboard` there, and then switch back to the main terminal. </ins> {{< /note >}} 2. Open the Kubernetes dashboard in a browser:
Change:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Change so that the first mention of a “API server” is a for the entry in the glossary. Why is this needed Glossary tooltips help novice users (and people evaluating Kubernetes) to quickly grasp concepts they haven't yet encountered. Comments /language en /triage accepted /priority backlog /kind feature /good-first-issue
This request has been marked as suitable for new contributors. 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 : This is a Feature Request <!-- See for guidance on writing an actionable issue description. --<!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Change so that the first mention of a “API server” is a for the entry in the glossary. Glossary tooltips help novice users (and people evaluating Kubernetes) to quickly grasp concepts they haven't yet encountered. Comments /language en /triage accepted /priority backlog /kind feature /good-first-issue 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
/assign

Discussion:
## Enabling Resource Quota Resource Quota support is enabled by default for many Kubernetes distributions.  It is <del> enabled when the API server `--enable-admission-plugins=` flag has `ResourceQuota` as </del> <ins> enabled when the {{< glossary_tooltip text="API server" term_id="kube-apiserver" >}} `--enable-admission-plugins=` flag has `ResourceQuota` as </ins> one of its arguments. A resource quota is enforced in a particular namespace when there is a
Change:
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: In the section of the Operator pattern concept page there is a link to CoreOS' original article about the Operator pattern. Following a series of acquisitions it looks like that article is no longer published. I couldn't find a current URL for it. Proposed Solution: Update the link to point at and mention in the text that this is archived from the original. Page to Update: Additional Information: To edit via GitHub web interface: /kind bug /priority backlog /language en /triage accepted /good-first-issue
This request has been marked as suitable for new contributors. 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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: In the section of the Operator pattern concept page there is a link to CoreOS' original article about the Operator pattern. Update the link to point at and mention in the text that this is archived from the original. To edit via GitHub web interface: /priority backlog /language en /triage accepted /good-first-issue 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
I would like to take this one. This will be my first time contributing to repo, so I might take a while.
/assign
Fixed in /close
Closing this issue. <detailsIn response to : Fixed in /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

Discussion:
you implement yourself * using the [Operator Framework](https://operatorframework.io) * [Publish](https://operatorhub.io/) your operator for other people to use <del> * Read [CoreOS' original article](https://coreos.com/blog/introducing-operators.html) that introduced the Operator pattern </del> <ins> * Read [CoreOS' original article](https://web.archive.org/web/20170129131616/https://coreos.com/blog/introducing-operators.html) that introduced the Operator pattern (this is an archived version of the original article). </ins> * Read an [article](https://cloud.google.com/blog/products/containers-kubernetes/best-practices-for-building-kubernetes-operators-and-stateful-apps) from Google Cloud about best practices for building Operators
Change:
In the 'My Service Missing Endpoints' sub-chapter containerPort is mentioned as Service parameter but in fact this should be changed to targetPort: "If your service has a containerPort specified, but the Pods that are selected don't have that port listed, then they won't be to the endpoints list. Verify that the pod's containerPort matches up with the Service's targetPort" Since Service object does not have containerPort, this should be fixed to targetPort.
As I understand it, this issue is about /kind bug /language en /triage accepted
/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 : /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

Discussion:
``` to list pods that match this selector.  Verify that the list matches the Pods that you expect to provide your Service. <del> If the list of pods matches expectations, but your endpoints are still empty, it's possible that you don't have the right ports exposed.  If your service has a `containerPort` specified, but the Pods that are selected don't have that port listed, then they won't be added to the endpoints list. </del> Verify that the pod's `containerPort` matches up with the Service's `targetPort` #### Network traffic is not forwarded <del> If you can connect to the service, but the connection is immediately dropped, and there are endpoints in the endpoints list, it's likely that the proxy can't contact your pods. There are three things to check: * Are your pods working correctly?  Look for restart count, and [debug pods](#debugging-pods). * Can you connect to your pods directly?  Get the IP address for the Pod, and try to connect directly to that IP. * Is your application serving on the port that you configured?  Kubernetes doesn't do port remapping, so if your application serves on 8080, the `containerPort` field needs to be 8080. </del> <ins> Please see [debugging service](/docs/tasks/debug-application-cluster/debug-service.md) for more information. </ins> ## {{% heading "whatsnext" %}}
Change:
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: ! URL #self-registration-of-nodes #manual-node-administration # # Proposed Solution: {#self-registration-of-nodes} {#manual-node-administration} 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
/language zh /assign

Discussion:
<!-- Kubernetes runs your workload by placing containers into Pods to run on _Nodes_. A node may be a virtual or physical machine, depending on the cluster. Each node <del> is managed by the {{< glossary_tooltip text="control plane" term_id="control-plane" >}} and contains the services necessary to run {{< glossary_tooltip text="Pods" term_id="pod" >}} </del> <ins> contains the services necessary to run {{< glossary_tooltip text="Pods" term_id="pod" >}}, managed by the {{< glossary_tooltip text="control plane" term_id="control-plane" >}}. </ins> Typically you have several nodes in a cluster; in a learning or resource-limited environment, you might have just one.

{{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}}. --> Kubernetes 通过将容器放入在节点（Node）上运行的 Pod 中来执行你的工作负载。 <del> 节点可以是一个虚拟机或者物理机器，取决于所在的集群配置。每个节点由 {{< glossary_tooltip text="控制面" term_id="control-plane" >}} 负责管理， 并包含运行 {{< glossary_tooltip text="Pods" term_id="pod" >}} 所需的服务。 </del> <ins> 节点可以是一个虚拟机或者物理机器，取决于所在的集群配置。 每个节点包含运行 {{< glossary_tooltip text="Pods" term_id="pod" >}} 所需的服务， 这些 Pods 由 {{< glossary_tooltip text="控制面" term_id="control-plane" >}} 负责管理。 </ins> 通常集群中会有若干个节点；而在一个学习用或者资源受限的环境中，你的集群中也可能 只有一个节点。

For self-registration, the kubelet is started with the following options: --> <del> ### 节点自注册 </del> <ins> ### 节点自注册 {#self-registration-of-nodes} </ins> 当 kubelet 标志 `--register-node` 为 true（默认）时，它会尝试向 API 服务注册自己。 这是首选模式，被绝大多数发行版选用。

You can modify Node objects regardless of the setting of `--register-node`. For example, you can set labels on an existing Node, or mark it unschedulable. --> <del> ### 手动节点管理 </del> <ins> ### 手动节点管理 {#manual-node-administration} </ins> 你可以使用 {{< glossary_tooltip text="kubectl" term_id="kubectl" >}} 来创建和修改 Node 对象。
Change:
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: Helm install URL is Wrong ! Proposed Solution: Change it to 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
/language zh /assign

Discussion:
* 如果你正在使用 `hack/local-up-cluster.sh`，请确保设置了 `KUBE_ENABLE_CLUSTER_DNS` 环境变量，然后运行安装脚本。 * [安装和设置 v1.7 或更高版本的 kubectl](/zh/docs/tasks/tools/install-kubectl/)，确保将其配置为连接到 Kubernetes 集群。 * 安装 v2.7.0 或更高版本的 [Helm](https://helm.sh/)。 <del> * 遵照 [Helm 安装说明](https://github.com/kubernetes/helm/blob/master/docs/install.md)。 </del> <ins> * 遵照 [Helm 安装说明](https://helm.sh/docs/intro/install/)。 </ins> * 如果已经安装了适当版本的 Helm，请执行 `helm init` 来安装 Helm 的服务器端组件 Tiller。 <!-- steps -->
Change:
The page for incorrectly calls out waiting behavior as a warning rather than a caution. For more information, see Change the callout for to a caution instead of a warning: /sig docs
/good-first-issue /triage accepted
This request has been marked as suitable for new contributors. 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 : /good-first-issue /triage accepted 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
/assign
As a reminder, anyone can open a pull request on an open issue, whether it’s assigned or not. Also as a reminder, please save issues marked good-first-issue for first time contributors.
/unassign
It would also be good to change the text of the caution slightly - see

Discussion:
Readiness probes runs on the container during its whole lifecycle. {{< /note >}} <del> {{< warning >}} </del> <ins> {{< caution >}} </ins> Liveness probes *do not* wait for readiness probes to succeed. If you want to wait before executing a liveness probe you should use initialDelaySeconds or a startupProbe. <del> {{< /warning >}} </del> <ins> {{< /caution >}} </ins> Readiness probes are configured similarly to liveness probes. The only difference is that you use the `readinessProbe` field instead of the `livenessProbe` field.
Change:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Update to follow v1.19 of the original (English) text. Why is this needed is outdated. Comments /language ja /good-first-issue File to update Original diff between translated and v1.19 Note Currently, we use dev-1.19-ja.1 branch. Please open a PR targeting the branch. ref If you have a question, feel free to ask us at #kubernetes-docs-ja channel.
This request has been marked as suitable for new contributors. 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 : This is a Feature Request <!-- See for guidance on writing an actionable issue description. --Update to follow v1.19 of the original (English) text. is outdated. /language ja /good-first-issue Currently, we use dev-1.19-ja.1 branch. Please open a PR targeting the branch. 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
/triage accepted
/assign

Discussion:
## コンテナイメージ [コンテナイメージ](/docs/concepts/containers/images/)はすぐに実行可能なソフトウェアパッケージで、アプリケーションの実行に必要なものをすべて含んています。コードと必要なランタイム、アプリケーションとシステムのライブラリ、そして必須な設定項目のデフォルト値を含みます。 <del> 設計上、コンテナは不変で、既に実行中のコンテナのコードを変更することはできません。コンテナ化されたアプリケーションがあり変更したい場合は、変更を含んだ新しいコンテナをビルドし、コンテナを再作成して、更新されたイメージから起動する必要があります。 </del> <ins> 設計上、コンテナは不変で、既に実行中のコンテナのコードを変更することはできません。コンテナ化されたアプリケーションがあり変更したい場合は、変更を含んだ新しいイメージをビルドし、コンテナを再作成して、更新されたイメージから起動する必要があります。 </ins> ## コンテナランタイム
Change:
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: In , the link  is broken. Proposed Solution: Update link to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/kind bug /priority backlog /language en
/triage accepted

Discussion:
echo 'complete -F __start_kubectl k' >>~/.bash_profile ``` <del> - If you installed kubectl with Homebrew (as explained [above](#install-with-homebrew-on-macos)), then the kubectl completion script should already be in `/usr/local/etc/bash_completion.d/kubectl`. In that case, you don't need to do anything. </del> <ins> - If you installed kubectl with Homebrew (as explained [here](/docs/tasks/tools/install-kubectl-macos/#install-with-homebrew-on-macos)), then the kubectl completion script should already be in `/usr/local/etc/bash_completion.d/kubectl`. In that case, you don't need to do anything. </ins> {{< note >}} The Homebrew installation of bash-completion v2 sources all the files in the `BASH_COMPLETION_COMPAT_DIR` directory, that's why the latter two methods work. {{< /note >}} <del> In any case, after reloading your shell, kubectl completion should be working. </del>  No newline at end of file <ins> In any case, after reloading your shell, kubectl completion should be working. </ins>