jiebi/CodeConvo huggingface dataset:
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 Japanese website, two hyperlinks ( --kubeconfig and cheat sheet ) on the Command line tool (kubectl) page are not getting redirected to the Japanese version of the respective pages. Proposed Solution: The Japanese version of these two pages is already available, so I will simply make these two hyperlinks redirect to the respective Japanese page. Page to Update: https://deploy-preview---kubernetes-io-main- <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--! Comments I want to work on this issue. /assign
/language ja
/triage accepted Thanks for pointing this out You can start solving this issue by assigning yourself. However, it is always recommended to pick those issues of localization that is native to you.
Ok, thank you I'll keep this in my mind from now on .

Discussion:
このツールの名前は、`kubectl` です。 <del> `kubectl`コマンドラインツールを使うと、Kubernetesクラスターを制御できます。環境設定のために、`kubectl`は、`$HOME/.kube`ディレクトリにある`config`という名前のファイルを探します。他の[kubeconfig](/ja/docs/concepts/configuration/organize-cluster-access-kubeconfig/)ファイルは、`KUBECONFIG`環境変数を設定するか、[`--kubeconfig`](/docs/concepts/configuration/organize-cluster-access-kubeconfig/)フラグを設定することで指定できます。 </del> <ins> `kubectl`コマンドラインツールを使うと、Kubernetesクラスターを制御できます。環境設定のために、`kubectl`は、`$HOME/.kube`ディレクトリにある`config`という名前のファイルを探します。他の[kubeconfig](/ja/docs/concepts/configuration/organize-cluster-access-kubeconfig/)ファイルは、`KUBECONFIG`環境変数を設定するか、[`--kubeconfig`](/ja/docs/concepts/configuration/organize-cluster-access-kubeconfig/)フラグを設定することで指定できます。 </ins> この概要では、`kubectl`の構文を扱い、コマンド操作を説明し、一般的な例を示します。サポートされているすべてのフラグやサブコマンドを含め、各コマンドの詳細については、[kubectl](/docs/reference/generated/kubectl/kubectl-commands/)リファレンスドキュメントを参照してください。 <del> インストール方法については、[kubectlのインストールおよびセットアップ](/ja/docs/tasks/tools/install-kubectl/)をご覧ください。クイックガイドは、[cheat sheet](/docs/reference/kubectl/cheatsheet/) をご覧ください。`docker`コマンドラインツールに慣れている方は、[`kubectl` for Docker Users](/docs/reference/kubectl/docker-cli-to-kubectl/) でKubernetesの同等のコマンドを説明しています。 </del> <ins> インストール方法については、[kubectlのインストールおよびセットアップ](/ja/docs/tasks/tools/install-kubectl/)をご覧ください。クイックガイドは、[チートシート](/ja/docs/reference/kubectl/cheatsheet/)をご覧ください。`docker`コマンドラインツールに慣れている方は、[`kubectl` for Docker Users](/docs/reference/kubectl/docker-cli-to-kubectl/)でKubernetesの同等のコマンドを説明しています。 </ins> <!-- body -->
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: Kubernetes defined an annotation, . For example, this annotation is set during rolling restarts. That annotation is unregistered because it doesn't appear inside Proposed Solution: Register the annotation, by documenting it in&hellip; Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig architecture /sig cli /language en
/assign
/lgtm /assign
I am happy to work on this issue once triage accepted, thanks.
Unassigning myself as PR is already raised by
/triage accepted
/priority backlog
PR that is working on this issue .
PRs to fix this are welcome. what are your plans for ?
hi are you still working on the issue?
How about this
Let me know if no one's working on the issue currently then i can raise this PR. I already have this in my local branch
a PR is welcome if you have code for it, nearly always. It's also polite to try to liaise with anyone else who's mentioned that they plan to do work on the same issue. In this case, you can see things have gone quiet. Opening a PR here can't reasonably be seen as thoughtlessly barging in.
Thanks for confirmation .
Raised the PR for this annotation, please take a look. I'll be happy to improve it based on your reviews.

Discussion:
to track changes. That mechanism has been superseded by [Server-side apply](/docs/reference/using-api/server-side-apply/). <ins> ### kubectl.kubernetes.io/restartedAt {#kubectl-k8s-io-restart-at} Type: Annotation Example: `kubectl.kubernetes.io/restartedAt: "2024-06-21T17:27:41Z"` Used on: Deployment, ReplicaSet, StatefulSet, DaemonSet, Pod This annotation contains the latest restart time of a resource (Deployment, ReplicaSet, StatefulSet or DaemonSet), where kubectl triggered a rollout in order to force creation of new Pods. The command `kubectl rollout restart <RESOURCE>` triggers a restart by patching the template metadata of all the pods of resource with this annotation. In above example the latest restart time is shown as 21st June 2024 at 17:27:41 UTC. You should not assume that this annotation represents the date / time of the most recent update; a separate change could have been made since the last manually triggered rollout. If you manually set this annotation on a Pod, nothing happens. The restarting side effect comes from how workload management and Pod templating works. </ins> ### endpoints.kubernetes.io/over-capacity Type: Annotation
Change:
The translated Brazilian Portuguese glossary entry for ingress is slightly out-of-date with its English counterpart. Update the entry so it reflects the latest English version. /language pt /triage accepted /assign

Discussion:
title: Ingress id: ingress date: 2018-04-12 <del> full_link: /docs/concepts/services-networking/ingress/ </del> <ins> full_link: /pt-br/docs/concepts/services-networking/ingress/ </ins> short_description: > Um objeto da API que gerencia o acesso externo aos serviços em um cluster, normalmente HTTP.

<!--more--> <del> Um Ingress pode fornecer as capacidades de um proxy reverso para as aplicações. </del> <ins> Um Ingress pode fornecer balanceamento de carga, terminação SSL e hospedagem virtual baseada em nomes. </ins>
Change:
The PR improperly set the minim version to 1.5 when there is no such version. Public link: Markdown file: ! !
/assign
kubernetes 1.5 release end of life (1 October 2017) already passed so this page needs updation
/kind bug
I guess it is mentioned because in v1.5: As per release It totally depends upon the docs and /sig node what they want to mention. If it is mentioned because of the time this feature went beta this page might be right.
/retitle “Safely Drain a Node” states that you need Kubernetes 1.5 or later /language en That statement is correct and its inclusion does not, to me, feel misleading. /priority awaiting-more-evidence
Just to confirm the version indicates the complete functionality is not available until v1.5 is released? PDB is . Only confusing area is what functionality in the document is for 1.5 and what is available now?
Try this: The page does not say you need to wait for an upcoming release. I think you have misunderstood what is actually a clear statement We could drop the shortcode as we assume everyone is using Kubernetes 1.21 or later.
/triage accepted Drop the version-check would be desireable.
/priority important-longterm
For SIG Docs, this is only a backlog priority I think. We've other work that we'd want to prioritize. Help here is still very welcome!

Discussion:
- kow3ns title: Safely Drain a Node content_type: task <del> min-kubernetes-server-version: 1.5 </del> weight: 310 ---

## {{% heading "prerequisites" %}} <del> {{% version-check %}} This task also assumes that you have met the following prerequisites: </del> <ins> This task assumes that you have met the following prerequisites: </ins> 1. You do not require your applications to be highly available during the node drain, or 1. You have read about the [PodDisruptionBudget](/docs/concepts/workloads/pods/disruptions/) concept,
Change:
A qotation mark is missing at the end of a command, making it wrong. At the page at step 2: The command is: export NODEPORT="$(kubectl get services/kubernetes-bootcamp -o go-template='{{(index 0).nodePort}}') And should be: export NODEPORT="$(kubectl get services/kubernetes-bootcamp -o go-template='{{(index 0).nodePort}}')"
/language en
/triage accepted
/assign
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /sig doc </details
Page to Update: /retitle Unquoted export in "Performing a Rolling Update" tutorial /kind bug
This issue has not been updated in over 1 year, and should be re-triaged. You can: Confirm that this issue is still relevant with (org members only) Close this issue with For more details on the triage process, see /remove-triage accepted

Discussion:
<p>First, check that the app is running. To find the exposed IP address and port, run the <code>describe service</code> command:</p> <p><code><b>kubectl describe services/kubernetes-bootcamp</b></code></p> <p>Create an environment variable called <tt>NODE_PORT</tt> that has the value of the Node port assigned:</p> <del> <p><code><b>export NODE_PORT="$(kubectl get services/kubernetes-bootcamp -o go-template='{{(index .spec.ports 0).nodePort}}')</b></code><br /> </del> <ins> <p><code><b>export NODE_PORT="$(kubectl get services/kubernetes-bootcamp -o go-template='{{(index .spec.ports 0).nodePort}}')"</b></code><br /> </ins> <code><b>echo "NODE_PORT=$NODE_PORT"</b></code></p> <p>Next, do a <code>curl</code> to the the exposed IP and port:</p> <p><code><b>curl http://"$(minikube ip):$NODE_PORT"</b></code></p>
Change:
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

Discussion:
* 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>
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. --Update Japanese translation of Why is this needed It seems be outdated a bit Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/triage accepted

Discussion:
## 設定 <ins> * [例: Javaのマイクロサービスの設定](/docs/tutorials/configuration/configure-java-microservice/) </ins> * [ConfigMapを用いたRedisの設定](/ja/docs/tutorials/configuration/configure-redis-using-configmap/) ## ステートレスアプリケーション

## ステートフルアプリケーション <del> * [StatefulSetの基本](/docs/tutorials/stateful-application/basic-stateful-set/) </del> <ins> * [StatefulSetの基本](/ja/docs/tutorials/stateful-application/basic-stateful-set/) </ins> <del> * [例: 永続ボリュームを使ったWordPressとMySQLのデプロイ](/ja/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume/) </del> <ins> * [例: Persistent Volumeを使用したWordpressとMySQLをデプロイする](/ja/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume/) </ins> <del> * [例: Stateful Setsを使ったCassandraのデプロイ](/docs/tutorials/stateful-application/cassandra/) </del> <ins> * [例: Stateful Setを使用したCassandraのデプロイ](/ja/docs/tutorials/stateful-application/cassandra/) </ins> * [CP(一貫性＋分断耐性)分散システムZooKeeperの実行](/docs/tutorials/stateful-application/zookeeper/) <del> ## クラスター * [AppArmor](/docs/tutorials/clusters/apparmor/) * [seccomp](/docs/tutorials/clusters/seccomp/) </del> ## サービス <ins> * [Connecting Applications with Services](/docs/tutorials/services/connect-applications-service/) </ins> * [Source IPを使う](/ja/docs/tutorials/services/source-ip/) <ins> ## セキュリティ * [クラスターレベルのPod Securityの標準の適用](/docs/tutorials/security/cluster-level-pss/) * [NamespaceレベルのPod Securityの標準の適用](/docs/tutorials/security/ns-level-pss/) * [AppArmor](/docs/tutorials/security/apparmor/) * [seccomp](/docs/tutorials/security/seccomp/) </ins> ## {{% heading "whatsnext" %}} チュートリアルのページタイプについての情報は、[Content Page Types](/docs/contribute/style/page-content-types/)を参照してください。
Change:
Feedback a confusing point about kubectl command on page: <img width="1107" alt="image" src="https://user-""kubectl events " command seems just available in k8s-v1.26 release version, while below v1.26 not work yet. so a brief tip or comment on the page will be easy to understand. FYI.
Page: /language en /kind suggestion
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Page: /language en /kind suggestion 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
In my opinion, the cheat sheet is accurate for Kubernetes v1.26. However, if someone needs to refer to older documentation, they can access it by using the version selector option in the navigation bar. To improve clarity, the cheat sheet could integrate details from and provide explicit links within the content body to the other available versions. This approach would be more effective than simply relying on the version selector in the top navigation. Would folks consider this suggestion beneficial?
/retitle Improve clarity of kubectl Cheat Sheet with version information
I'd like to see a shortcode that renders as helper text to steer people to the right documentation, and a link to available versions. See for an example where I'd use this: we could replace that text with an even more helpful shortcode.
We could add a comment that this is accurate for this version of the docs. /priority backlog
I recommend the simple comment approach. We can still use version shortcodes, eg in the comment. /triage accepted
/assign
FYI

Discussion:
This page contains a list of commonly used `kubectl` commands and flags. <ins> {{< note >}} These instructions are for Kubernetes v{{< skew currentVersion >}}. To check the version, use the `kubectl version` command. {{< /note >}} </ins> <!-- body --> ## Kubectl autocomplete

kubectl config unset users.foo                       # delete user foo <del> # short alias to set/show context/namespace (only works for bash and bash-compatible shells, current context to be set before using kn to set namespace) </del> <ins> # short alias to set/show context/namespace (only works for bash and bash-compatible shells, current context to be set before using kn to set namespace) </ins> alias kx='f() { [ "$1" ] && kubectl config use-context $1 || kubectl config current-context ; } ; f' alias kn='f() { [ "$1" ] && kubectl config set-context --current --namespace $1 || kubectl config view --minify | grep namespace | cut -d" " -f6 ; } ; f' ```
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: Document the EndpointSlice controller ignores nodes with the following labels or Proposed Solution: Document labels Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/kind cleanup /language en
/assign
/sig network /triage accepted

Discussion:
Used on: Node <del> Label that kubeadm applies on the control plane nodes that it manages. </del> <ins> A marker label to indicate that the node is used to run {{< glossary_tooltip text="control plane" term_id="control-plane" >}} components. The kubeadm tool applies this label to the control plane nodes that it manages. Other cluster management tools typically also set this taint. You can label control plane nodes with this label to make it easier to schedule Pods only onto these nodes, or to avoid running Pods on the control plane. If this label is set, [EndpointSlice controller](/docs/concepts/services-networking/topology-aware-routing/#implementation-control-plane) ignores that node while calculating Topology Aware Hints. </ins> ### node-role.kubernetes.io/control-plane {#node-role-kubernetes-io-control-plane-taint} Used on: Node <ins> Taint that kubeadm applies on control plane nodes to restrict placing pods and allow only specific pods to schedule on them. </ins> Example: `node-role.kubernetes.io/control-plane:NoSchedule` <del> Taint that kubeadm applies on control plane nodes to allow only critical workloads to schedule on them. </del> <ins> If this Taint is applied, control plane nodes allow only critical workloads to schedule on them. You can manually remove this taint with the following command on a specific node. ```shell kubectl taint nodes <node-name> node-role.kubernetes.io/control-plane:NoSchedule- ``` </ins> ### node-role.kubernetes.io/master (deprecated) {#node-role-kubernetes-io-master-taint}
Change:
The following step does not work: Now we can test that the app is exposed outside of the cluster using curl, the IP address of the Node and the externally exposed port: Steps are in the following places: (Load Balancing section) (Create a new Service section) Per the Minikube requires that Services of type NodePort be exposed with . Recommend adding a step to run this Minikube command in a separate terminal instance, copy the URL from this command, and curl that URL.
It depends on the minikube driver, but you are right that the step is required if using Docker Desktop (without an IP)
/retitle Explain extra step for exposing Services locally on minikube If some minikube drivers need it, we should mention that. /kind bug /language en /priority backlog /triage accepted
/assign
should we repeat the instructions shown in the existing or just add a link to said document? I think I read somewhere that we should avoid repeating documentation. Or should we rewrite the minikube commands to align them to the tutorial? Thanks!
These tutorials are outdated, as far as I know. Nothing for me here, seems to be documented:
Any of those is fine. I do not have an opinion on which is best.
Help with a fix is very welcome. If you'd like to help but aren't sure how: please ask in #sig-docs on the Kubernetes Slack workspace. If you're not already a member of that workspace, you can visit for an invitation.
/assign
A very nice note has already been in the live documentation as can be seen here. I will create a PR to add a similar note to This should be sufficient in my opinion.

Discussion:
<p>Next, we’ll do a <code>curl</code> to the exposed IP address and port. Execute the command multiple times:</p> <p><code><b>curl http://"$(minikube ip):$NODE_PORT"</b></b></b></code></p> <p>We hit a different Pod with every request. This demonstrates that the load-balancing is working.</p> <ins> {{< note >}}<p>If you're running minikube with Docker Desktop as the container driver, a minikube tunnel is needed. This is because containers inside Docker Desktop are isolated from your host computer.<br> <p>In a separate terminal window, execute:<br> <code><b>minikube service kubernetes-bootcamp --url</b></code></p> <p>The output looks like this: <pre><b>http://127.0.0.1:51082<br>!  Because you are using a Docker driver on darwin, the terminal needs to be open to run it.</b></pre></p> <p>Then use the given URL to access the app:<br> <code><b>curl 127.0.0.1:51082</b></code></p> {{< /note >}} </ins> </div> </div>
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: The description about emptyDir sizeLimit in page mentioned that: But the following code shows that if no size is specified, size limit defaults to node allocatable memory. Here is the information about my local environment and the result: Proposed Solution: Change this description to the following: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/assign /language en /sig storage
Could I ask that why it says that if no size is specified, memory backed volumes are sized to 50% of the memory on a Linux host in the document? Why would memory backed volumes be sized 50% of the memory on a Linux host? Is it because the tmpfs default size=50% of physical RAM?
/remove-sig storage /sig node
/triage accepted
The memory-backed EmptyDir by default consumes a very large amount of memory (documented as , but actually ). I think it's too large for the default. In fact, one pod can occupy most of a node's memory. Is there any way to limits the size of memory-backed EmptyDir by cluster admin?
I'm not aware of any existing mechanisms to automate the setting of for volumes. You may have to devise your own mutating webhook or wait for the mutating admission policy to land. -- my 2 cents.
Thank you for your advice! But it's problem that the whole of cluster can be down easily by few pods and the cluster admin can not control this, IMHO. I have a few idea for this problem: Set the default size of memory-backed EmptyDir fewer. e.g. 50Mi. Enable to be controlled the total size of memory-backed EmptyDir Add taint to node for that memory-backed EmptyDir can use WDYT?
I'd like to discuss about this in . Thanks!!

Discussion:
{{< note >}} If the `SizeMemoryBackedVolumes` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled, you can specify a size for memory backed volumes.  If no size is specified, memory <del> backed volumes are sized to 50% of the memory on a Linux host. </del> <ins> backed volumes are sized to node allocatable memory. </ins> {{< /note>}} #### emptyDir configuration example