jiebi/CodeConvo huggingface dataset:
Change:
This is a Bug Report Problem: The current documentation is still referring to the non-official Kubernetes container image repository introduced starting from v1.25 () and referring to an outdated version. Proposed Solution: I can take care of the PR updating the content. Page to Update:
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:
hostNetwork: true containers: - name: konnectivity-server-container <del> image: us.gcr.io/k8s-artifacts-prod/kas-network-proxy/proxy-server:v0.0.16 </del> <ins> image: registry.k8s.io/kas-network-proxy/proxy-server:v0.0.32 </ins> command: ["/proxy-server"] args: [ "--logtostderr=true",
Change:
The spelling of the functionality i.e funcationality is wrong, I'm attaching the screenshot for the same. May I open a new PR correcting the spelling? !
Hi you can raise a PR for that but also make sure to check for other errors on that same doc, also you can provide a link to that error instead of attaching a screenshot. /language en
Hey I was working on this issue but has made a PR, I have given a lot of o time to finding the bug and she has raised a PR, Is it not wrong?
Hey I did not check the comments here, you can Raise a PR if you want. I can close it. The issue was clear from the PR description. Let me know if you want me to close it. It wasn't assigned to anyone.
Hey Yes please close your PR, I had given time to find the bug. I'll be grateful to you.
Hi thanks for your response also you can review the previous comments made on any issues and check if there is someone who already mentioned that they want to work on it and if you want to work on it you can ask the author of the issue.
Yeah sure, I will close the PR. Not an issue. Thanks!!
/triage accepted /assign
(nit) /retitle Typo on Guide for scheduling Windows containers in Kubernetes page

Discussion:
## Objectives * Configure an example deployment to run Windows containers on the Windows node <del> * Highlight Windows specific funcationality in Kubernetes </del> <ins> * Highlight Windows specific functionality in Kubernetes </ins> ## Before you begin
Change:
Problem: The text on is not working, it should point to this Check the page for the problem. Page to Update: Proposed Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text CSI ephemeral volumes 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 link on the text CSI ephemeral volumes 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
/triage accepted
/sig storage
/kind documentation

Discussion:
use the volume. The scheduler then schedules Pods onto nodes where the volume is available after the volume has been created. <del> For [CSI ephemeral volumes](/docs/concepts/storage/volumes/#csi), </del> <ins> For [CSI ephemeral volumes](/docs/concepts/storage/ephemeral-volumes/#csi-ephemeral-volumes), </ins> scheduling always happens without considering storage capacity. This is based on the assumption that this volume type is only used by special CSI drivers which are local to a node and do not need
Change:
Add quotes in the flag of command to avoid confusing the shell: Otherwise, this is what user may see:
Link:
/assign
/triage accepted /language en /retitle Unquoted command in kubectl cheat sheet

Discussion:
kubectl cluster-info dump --output-directory=/path/to/cluster-state   # Dump current cluster state to /path/to/cluster-state # View existing taints on which exist on current nodes. <del> kubectl get nodes -o=custom-columns=NodeName:.metadata.name,TaintKey:.spec.taints[*].key,TaintValue:.spec.taints[*].value,TaintEffect:.spec.taints[*].effect </del> <ins> kubectl get nodes -o='custom-columns=NodeName:.metadata.name,TaintKey:.spec.taints[*].key,TaintValue:.spec.taints[*].value,TaintEffect:.spec.taints[*].effect' </ins> # If a taint with that key and effect already exists, its value is replaced as specified. kubectl taint nodes foo dedicated=special-user:NoSchedule
Change:
We can, and should, update the example that appears after We can make this use the shortcode - see Whenever we give examples that the reader could try out by running them, we should prefer using shortcodes.
/language en /triage accepted I recommend switching it to a shortcode per
I'm not sure that there's anything actually wrong with the of that Pod, though. /kind cleanup
Pasting that snippet into my own code gave me errors and it took me some time to figure out that it was due to the copied code being incorrect.
would you be willing to provide a diff for that manifest that shows the fix? It'd help.
Here is what it is currently: and here's how it should be. It's actually and everything within that block that should be shift-tab'd. There's another example on that page which is correct and you can find it by searching for "name: foo"
/assign

Discussion:
Here's an example Pod that uses values from `game-demo` to configure a Pod: <del> ```yaml apiVersion: v1 kind: Pod metadata: name: configmap-demo-pod spec: containers: - name: demo image: alpine command: ["sleep", "3600"] env: # Define the environment variable - name: PLAYER_INITIAL_LIVES # Notice that the case is different here # from the key name in the ConfigMap. valueFrom: configMapKeyRef: name: game-demo           # The ConfigMap this value comes from. key: player_initial_lives # The key to fetch. - name: UI_PROPERTIES_FILE_NAME valueFrom: configMapKeyRef: name: game-demo key: ui_properties_file_name volumeMounts: - name: config mountPath: "/config" readOnly: true volumes: # You set volumes at the Pod level, then mount them into containers inside that Pod - name: config configMap: # Provide the name of the ConfigMap you want to mount. name: game-demo # An array of keys from the ConfigMap to create as files items: - key: "game.properties" path: "game.properties" - key: "user-interface.properties" path: "user-interface.properties" ``` </del> <ins> {{< codenew file="configmap/configure-pod.yaml" >}} </ins> A ConfigMap doesn't differentiate between single line property values and multi-line file-like values.

<ins> apiVersion: v1 kind: Pod metadata: name: configmap-demo-pod spec: containers: - name: demo image: alpine command: ["sleep", "3600"] env: # Define the environment variable - name: PLAYER_INITIAL_LIVES # Notice that the case is different here # from the key name in the ConfigMap. valueFrom: configMapKeyRef: name: game-demo           # The ConfigMap this value comes from. key: player_initial_lives # The key to fetch. - name: UI_PROPERTIES_FILE_NAME valueFrom: configMapKeyRef: name: game-demo key: ui_properties_file_name volumeMounts: - name: config mountPath: "/config" readOnly: true volumes: # You set volumes at the Pod level, then mount them into containers inside that Pod - name: config configMap: # Provide the name of the ConfigMap you want to mount. name: game-demo # An array of keys from the ConfigMap to create as files items: - key: "game.properties" path: "game.properties" - key: "user-interface.properties" path: "user-interface.properties" </ins>  No newline at end of file
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: I have a node in Minikube that's annotated with the key . This looks intended, but doesn't document that annotation. Proposed Solution: Document that annotation; as a side effect, this registers it. has some tips on what the annotation means. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig storage /language en /priority backlog PS. Maybe, as a separate detail, the project should deprecate this annotation. I'm not sure if modern Kubernetes still needs it.
/triage accepted
/assign
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale

Discussion:
This annotation will be added to dynamic provisioning required PVC. <ins> ### volumes.kubernetes.io/controller-managed-attach-detach Used on: Node If a node has set the annotation `volumes.kubernetes.io/controller-managed-attach-detach` on itself, then its storage attach and detach operations are being managed by the _volume attach/detach_ {{< glossary_tooltip text="controller" term_id="controller" >}} running within the {{< glossary_tooltip term_id="kube-controller-manager" text="kube-controller-manager" >}}. The value of the annotation isn't important; if this annotation exists on a node, then storage attaches and detaches are controller managed. </ins> ### node.kubernetes.io/windows-build {#nodekubernetesiowindows-build} Example: `node.kubernetes.io/windows-build: "10.0.17763"`
Change:
Problem: The text on should point to these Check the page for the problem. Page to Update: Proposed Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text PersistentVolumeClaim 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 should point to these Check the page for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text PersistentVolumeClaim 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

Discussion:
title: Persistent Volume Claim id: persistent-volume-claim date: 2018-04-12 <del> full_link: /docs/concepts/storage/persistent-volumes/ </del> <ins> full_link: /docs/concepts/storage/persistent-volumes/#persistentvolumeclaims </ins> short_description: > Claims storage resources defined in a PersistentVolume so that it can be mounted as a volume in a container.
Change:
The link to CustomResourceDefinitions is broken. Rather it should point to
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
/assign
The link should actually be to (at least, that's where I recommend linking to) /kind bug /language en
cool, I will update the PR with

Discussion:
<!-- overview --> This page explains how to add versioning information to <del> [CustomResourceDefinitions](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#customresourcedefinition-v1beta1-apiextensions), to indicate the stability </del> <ins> [CustomResourceDefinitions](/docs/reference/kubernetes-api/extend-resources/custom-resource-definition-v1/), to indicate the stability </ins> level of your CustomResourceDefinitions or advance your API to a new version with conversion between API representations. It also describes how to upgrade an object from one version to another. ## {{% heading "prerequisites" %}}
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. --I decided to try to learn a bit of Kubernetes on my new M1 Mac. It all worked except for the command, as that image does not support ARM. A bit of Googling and a visit to StackOverflow fixed it for me, but it would be better if that information was in the core guide. For others following in my footsteps, I have created a pull request with the ARM image info. Why is this needed ARM-based devices are becoming increasingly popular dev platforms, especially for early prototyping and learning. A Getting Started guide that worked on these hosts would be preferable to one which doesn't. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --I will link this Issue to my pull request. I realize the version number, not just the repo and name, are different from the existing image. However, being on an ARM device, I have no way of testing the original image, so I didn't change it.
I agree, it would be nice that the "getting started" guide is working on both platforms or at least propose an alternative image for ARM. Feel free to link this issue from the PR you made and thanks for taking the time! /triage accepted /priority backlog /language en
Oops, I had a typo in the pull request link. Linked.

Discussion:
Pod runs a Container based on the provided Docker image. ```shell <del> kubectl create deployment hello-node --image=registry.k8s.io/echoserver:1.4 </del> <ins> kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.39 -- /agnhost netexec --http-port=8080 </ins> ``` 2. View the Deployment:
Change:
What would you like to be This issue is a follow-up task from displays some English text: ! To replace this text with localized strings, you can update with from . Specifically, these:
/language ko
/triage accepted Thanks !
/assign

Discussion:
# i18n strings for the Korean translation. # NOTE: Please keep the entries in alphabetical order when editing <ins> # Avoid using conjunction_1. # Must match the context in layouts/shortcodes/release-data.html # Appears on https://kubernetes.io/releases/ # For example the "and" in "Complete 1.25 Schedule and Changelog" [conjunction_1] other = "및" </ins> [caution] other = "주의:"

[community_youtube_name] other = "YouTube" <ins> [cve_id] other = "CVE ID" [cve_issue_url] other = "CVE 깃헙 이슈 URL" [cve_json_external_url] other = "외부 URL" [cve_json_id] other = "id" [cve_json_summary] other = "요약" [cve_json_url] other = "url" [cve_summary] other = "이슈 요약" [cve_table] other = "공식 쿠버네티스 CVE 목록" [cve_url] other = "CVE URL" </ins> [deprecation_title] other = "해당 문서의 쿠버네티스 버전:"

[release_date_format] other = "2006-01-02" <ins> # Deprecated. Planned for removal in a future release. # Use [release_full_details_initial_text] instead. [release_complete] other = "완료" # Replace [release_complete] with [release_full_details_initial_text] [release_full_details_initial_text] other = "전체" [release_schedule] other = "일정" [release_changelog] other = "변경 이력" </ins> [seealso_heading] other = "더 보기"
Change:
This is different from what happens outside of a cluster; when kubectl runs outside a cluster and you don't specify a namespace, the kubectl command acts against the default namespace. On the above documentation, the kubectl does not act against 'default' namespace but the one assigned to the current-context. The kubeconfig files default context may be pointed to 'default' namespace, but that is not the default namespace all the time.
Hey, I had to search to retrieve where the context of what you mentioned, for further info. This is indeed a simplification but might be correct most of the time with default configured kubeconfig contexts. It could be more precise, mentioning the kubeconfig file (keeping in mind that this section is about in-cluster config). /sig cli /triage accepted /priority backlog /language en
/retitle kubectl default namespace not always 'default' but depends on kubeconfig If you can find a better title, just needed to make something a bit more precise than just an issue on kubectl
/assign

Discussion:
namespace of that ServiceAccount (this is the same as the namespace of the Pod) and acts against that namespace. This is different from what happens outside of a cluster; when kubectl runs outside a cluster and you don't specify a namespace, <del> the kubectl command acts against the `default` namespace. </del> <ins> the kubectl command acts against the namespace set for the current context in your client configuration. To change the default namespace for your kubectl you can use the following command: ```shell kubectl config set-context --current --namespace=<namespace-name> ``` </ins> ## Operations
Change:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/architecture/garbage- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/architecture/garbage- is outdated. A link text to this page from other pages have already been fixed. The current page is still "" and it should be fixed "". Comments /language ja /assign
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:
<!-- overview --> ガベージコレクションは、Kubernetesがクラスターリソースをクリーンアップするために使用するさまざまなメカニズムの総称です。これにより、次のようなリソースのクリーンアップが可能になります: <del> * [失敗したPod](/ja/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection) </del> <ins> * [終了したPod](/ja/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection) </ins> * [完了したJob](/ja/docs/concepts/workloads/controllers/ttlafterfinished/) * [owner referenceのないオブジェクト](#owners-dependents) * [未使用のコンテナとコンテナイメージ](#containers-images)

ガベージコレクションは、最後に使用された時間に基づいて、最も古いものから順にイメージを削除します。 kubeletは、ディスク使用量が`LowThresholdPercent`値に達するまでイメージを削除します。 <del> ### コンテナイメージのガベージコレクション {#container-image-garbage-collection} </del> <ins> ### コンテナのガベージコレクション {#container-image-garbage-collection} </ins> kubeletは、次の変数に基づいて未使用のコンテナをガベージコレクションします。

これらの変数に加えて、kubeletは、通常、最も古いものから順に、定義されていない削除されたコンテナをガベージコレクションします。 <del> `MaxPerPodContainer`と`MaxContainer`は、Podごとのコンテナーの最大数(`MaxPerPodContainer`)を保持すると、グローバルなデッドコンテナの許容合計(`MaxContainers`)を超える状況で、互いに競合する可能性があります。 この状況では、kubeletは`MaxPodPerContainer`を調整して競合に対処します。最悪のシナリオは、`MaxPerPodContainer`を1にダウングレードし、最も古いコンテナーを削除することです。 </del> <ins> `MaxPerPodContainer`と`MaxContainers`は、Podごとのコンテナーの最大数(`MaxPerPodContainer`)を保持すると、グローバルなデッドコンテナの許容合計(`MaxContainers`)を超える状況で、互いに競合する可能性があります。 この状況では、kubeletは`MaxPerPodContainer`を調整して競合に対処します。最悪のシナリオは、`MaxPerPodContainer`を1にダウングレードし、最も古いコンテナーを削除することです。 </ins> さらに、削除されたPodが所有するコンテナは、`MinAge`より古くなると削除されます。 {{<note>}}

StatefulSetのPodについては、[StatefulSetからPodを削除するためのタスクのドキュメント](/ja/docs/tasks/run-application/force-delete-stateful-set-pod/)を参照してください。 <del> ### 失敗したPodのガベージコレクション {#pod-garbage-collection} </del> <ins> ### 終了したPodのガベージコレクション {#pod-garbage-collection} </ins> 失敗したPodは人間または{{< glossary_tooltip term_id="controller" text="controller" >}}が明示的に削除するまで存在します。
Change:
(1) The user-facing changes in are not yet reflected in the doc. (2) There are four possible values for the of a rejection ("concurrency-limit", "queue-full", "time-out", and "cancelled") but "cancelled" is not listed in the doc. The relevant page is /sig api-machinery
APF is for "API Priority and Fairness" just for people looking into this issue. /triage accepted /priority important-longterm
Please feel free to change it again if it is not correct. /retitle "API Priority and Fairness" doc must be updated
/assign
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale

Discussion:
queue excess requests, or * `time-out`, indicating that the request was still in the queue when its queuing time limit expired. <ins> * `cancelled`, indicating that the request is not purge locked and has been ejected from the queue. </ins> * `apiserver_flowcontrol_dispatched_requests_total` is a counter vector (cumulative since server start) of requests that began
Change:
You can only get to the localized version of the page by going to the English version, and then clicking on the language dropdown to find a translation. If you are already on a localized version of the site, and the page exists in the selected language, it redirects you to the English version. See this comment for more info: Originally posted by in /area web-development
/area localization
/triage accepted
/priority important-longterm
/assign

Discussion:
[release_full_details_initial_text] other = "Complete" <ins> [release_information_navbar] other = "Release Information" </ins> [release_minor_version] other = "Minor Version"

</a> <div class="dropdown-menu dropdown-menu-right" aria-labelledby="navbarDropdownMenuLink"> {{ $p := . }} <del> <a class="dropdown-item" href="/releases">Release Information</a> </del> <ins> <a class="dropdown-item" href="{{ "releases" | relLangURL }}">{{ i18n "release_information_navbar" . }}</a> </ins> {{ range .Site.Params.versions }} <a class="dropdown-item" href="{{ .url }}{{ $p.RelPermalink }}">{{ .version }}</a> {{ end }} <del> </div> </del>  No newline at end of file <ins> </div> </ins>