jiebi/CodeConvo huggingface dataset:
Change:
app.kubernetes.io/name: mysql app.kubernetes.io/instance: mysql-abcxzy app.kubernetes.io/version: "5.7.21" <del> app.kubernetes.io/managed-by: helm </del> <ins> app.kubernetes.io/managed-by: Helm </ins> app.kubernetes.io/component: database app.kubernetes.io/part-of: wordpress ...

Discussion:
There is a suggested annotation of: But Helm actually : Which will insert a value of "Helm", with a first character in uppercase. According to , labels are case-sensitive, except for the prefix. (You can notice this discrepancy if you are using the plug-in, as your chart with a lower-case word will always be replaced with upper-case, so a three-way-merge diff shows this as changing every time. I also imagine you could find this if you tried to use the label as a selector) Therefore I recommend that the suggested annotation in this document be replaced with: Caveat: I have no idea if the case changed between helm v2 and v3, but v2 is defunct now, so should be safe to make this change.
This is just an example of what could go in, but I think it might be a good first issue. If you want to work on this, assign yourself to this issue. Update all instances of to , including in the table. You should be able to complete this in GitHub without needing to work on a local clone. For instructions, read .
/language en
Let me help with this. /assign
/triage accepted /good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /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
Change:
an owner reference. Owner references help different parts of Kubernetes avoid interfering with objects they don’t control. <ins> {{< note >}} Cross-namespace owner references are disallowed by design. Namespaced dependents can specify cluster-scoped or namespaced owners. A namespaced owner **must** exist in the same namespace as the dependent. If it does not, the owner reference is treated as absent, and the dependent is subject to deletion once all owners are verified absent. Cluster-scoped dependents can only specify cluster-scoped owners. In v1.20+, if a cluster-scoped dependent specifies a namespaced kind as an owner, it is treated as having an unresolvable owner reference, and is not able to be garbage collected. In v1.20+, if the garbage collector detects an invalid cross-namespace `ownerReference`, or a cluster-scoped dependent with an `ownerReference` referencing a namespaced kind, a warning Event with a reason of `OwnerRefInvalidNamespace` and an `involvedObject` of the invalid dependent is reported. You can check for that kind of Event by running `kubectl get events -A --field-selector=reason=OwnerRefInvalidNamespace`. {{< /note >}} </ins> ## Cascading deletion {#cascading-deletion} Kubernetes checks for and deletes objects that no longer have owner

Discussion:
The following information was dropped in and is critical to include in the garbage collection ownerReferences topic:
/triage accepted /sig api-machinery
/priority important-soon
Change:
## Background <del> Docker has a concept of [volumes](https://docs.docker.com/storage/), though it is somewhat looser and less managed. A Docker volume is a directory on disk or in another container. Docker provides volume drivers, but the functionality is somewhat limited. </del> Kubernetes supports many types of volumes. A {{< glossary_tooltip term_id="pod" text="Pod" >}} can use any number of volume types simultaneously. [Ephemeral volume](/docs/concepts/storage/ephemeral-volumes/) types have a lifetime of a pod,

Discussion:
This is a Bug Report Problem: The "background" sections describes volumes as if they all were ephemeral: It also starts with a comparison against Docker, which may or may not still make sense. Proposed Solution: Rewrite and link to the persistent- and (once is merged) to ephemeral- Page to Update:
/sig storage /priority backlog I definitely agree about the Docker stuff - there's no need to focus on a particular runtime, nor on Docker as a local development tool.
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. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale /lifecycle frozen
/triage accepted
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
/triage accepted
/assign
Change:
* [Apply Pod Security Standards at Cluster level](/docs/tutorials/security/cluster-level-pss/) * [Apply Pod Security Standards at Namespace level](/docs/tutorials/security/ns-level-pss/) <ins> * [AppArmor](/docs/tutorials/security/apparmor/) * [seccomp](/docs/tutorials/security/seccomp/) </ins> ## {{% heading "whatsnext" %}} If you would like to write a tutorial, see

Discussion:
This is a Feature Request What would you like to be Post-merge of , move the tutorials under into Merge clusters section into security section here: Why is this needed Issue description is a slight modification from original request in the comment Comments /hold for /cc /sig docs security
this might be a good first issue for new contributors in sig-security-docs /triage accepted
Hi, I would like to work on this issue. /assign
/kind cleanup
Hi , I a query: moving the tutorials from the cluster sub-directory into the security sub-directory, the cluster sub-directory will only have its file so do I need to do something regarding it ( file)? Thanks
Whenever you are free can you please help me with the above mentioned query. Thanks
Change:
frontend-3823415956-k22zn       1/1       Running   0          54m frontend-3823415956-w9gbt       1/1       Running   0          54m frontend-3823415956-x2pld       1/1       Running   0          5s <del> mongo-1068406935-3lswp   1/1       Running   0          56m </del> <ins> mongo-1068406935-3lswp          1/1       Running   0          56m </ins> ``` 1. Run the following command to scale down the number of frontend Pods:

Discussion:
4 ordered lists have wrong indexes. For example, the number below should be 3. ! Page to update: /language en /kind cleanup
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
Change:
</source> # Example: <del> # I0204 06:55:31.872680       5 servicecontroller.go:277] LB already exists and doesn't need update for service kube-system/kube-ui </del> <ins> # I0204 06:55:31.872680       5 servicecontroller.go:277] LB already exists and doesn't need update for service kube-system/kubernetes-dashboard </ins> <source> type tail format multiline

Discussion:
Connect with Proxies references kube ui. It should use the kube dashboard instead.
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:
시스템에 도커를 설치하기 위해서 아래의 커맨드들을 사용한다. {{< tabs name="tab-cri-docker-installation" >}} <del> {{< tab name="Ubuntu 16.04+" >}} </del> <ins> {{% tab name="Ubuntu 16.04+" %}} </ins> ```shell # (도커 CE 설치)

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: Broken layout for tabs on "Container runtimes" page as below. ! Proposed Solution: TBD Page to Update: /language ko <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/retitle Broken layout for tabs on "Container runtimes" page in Korean
This problem is due to incorrect tab code. We should fix this like the below: (Line 71, 125, 126, 180) to
/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 : /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
Hey folks, I'm happy to help you with this /assign
Change:
to use a different pod template and for the Job to have a new name. You cannot update the Job because these fields are not updatable. Therefore, you delete Job `old` but _leave its pods <del> running_, using `kubectl delete jobs/old --cascade=false`. </del> <ins> running_, using `kubectl delete jobs/old --cascade=orphan`. </ins> Before deleting it, you make a note of what selector it uses: ```shell

Discussion:
According to the can get a parameter with a value of "background", "orphan", or "foreground". proposes to use .
Hello Related PRs/issues: So, the page should be updated. /kind bug /language en /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 : Hello is now deprecated in favor of warning: is deprecated (boolean value) and can be replaced with Cascade=false is deprecated in kubectl 1.21, according to Bug /language en /help </details
/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 : /good-first-issue </details
/assign
/assign
To : has already assigned himself/herself, and posted a PR ().
Change:
### Project keys to specific paths and file permissions <del> You can project keys to specific paths and specific permissions on a per-file basis. The [Secrets](/docs/concepts/configuration/secret/#using-secrets-as-files-from-a-pod) guide explains the syntax. </del> <ins> You can project keys to specific paths. Refer to the corresponding section in the [Secrets](/docs/tasks/inject-data-application/distribute-credentials-secure/#project-secret-keys-to-specific-file-paths) guide for the syntax. You can set POSIX permissions for keys. Refer to the corresponding section in the [Secrets](/docs/tasks/inject-data-application/distribute-credentials-secure/#set-posix-permissions-for-secret-keys) guide for the syntax. </ins> ### Optional references

Discussion:
In , it mentions this guide explains the syntax. However the above Secret link doesn't mention anything on "specific paths" & file permission is defined . Appreciate feedback and update (correction) to documentation.
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
/kind bug
/remove-kind bug I think this is a request to mention POSIX permissions for the volume and its files, within the task page “Configure a Pod to Use a ConfigMap”. Is that right ? If that covers everything you want to see changed, please state that so we're sure. If you want another change as well, please be as clear as you can about what improvement you'd like. /language en
The reference needs to be updated/corrected to and on the page Configure a Pod to Use a ConfigMap and subsection !
/assign
Change:
<!-- overview --> <!-- <del> A _Deployment_ provides declarative updates for [Pods](/docs/concepts/workloads/pods/pod/) and [ReplicaSets](/docs/concepts/workloads/controllers/replicaset/). </del> <ins> A _Deployment_ provides declarative updates for {{< glossary_tooltip text="Pods" term_id="pod" >}} and {{< glossary_tooltip term_id="replica-set" text="ReplicaSets" >}}. </ins> --> 一个 Deployment 为 {{< glossary_tooltip text="Pod" term_id="pod" >}} 和 {{< glossary_tooltip term_id="replica-set" text="ReplicaSet" >}}

Discussion:
There are some bugs: ,nginx%3Dnginx%3A1.9.1,-%2D%2Drecord%3Dtrue%0A3 "nginx=nginx:1.9.1" should be changed to "nginx=nginx:1.16.1" ,nginx%3Dnginx%3A1.91,-%2D%2Drecord%3Dtrue "nginx=nginx:1.91" should be changed to "nginx=nginx:1.161" "image updated to 1.9.1" should be changed to "image updated to 1.16.1" The content of this article has many "", it could be changed to "deployment". For example: ,,-%E8%BE%93%E5%87%BA%E7%B1%BB%E4%BC%BC%E4%BA%8E "kubectl rollout history " could be changed to "kubectl rollout history deployment/nginx-deployment"
/language zh
/triage accepted
The label cannot be applied. Only GitHub organization members can add the label. <detailsIn response to : /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
looks like docs is already updated to nginx:1.16.1. Do you mind closing this issue?
There should still be a few places left unfinished.
Could you please edit the issue which needs to be still updated?
Bug1: ,nginx%3Dnginx%3A1.9.1,-%2D%2Drecord%3Dtrue%0A3 "nginx=nginx:1.9.1" should be changed to "nginx=nginx:1.16.1" Bug2: ,nginx%3Dnginx%3A1.91,-%2D%2Drecord%3Dtrue "nginx=nginx:1.91" should be changed to "nginx=nginx:1.161" Bug3: "image updated to 1.9.1" should be changed to "image updated to 1.16.1" Bug4: The content of this article has many "", it could be changed to "deployment".

For example: ,,-%E8%BE%93%E5%87%BA%E7%B1%BB%E4%BC%BC%E4%BA%8E "kubectl rollout history " could be changed to "kubectl rollout history deployment/nginx-deployment"
Thanks for clarifying. /assign
/retitle [zh] Localization bugs / work required for Deployment concept
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
/triage accepted
Change:
[input_placeholder_email_address] other = "ईमेल ऐड्रेस" <ins> [javascript_required] other = "इस विषय को देखने के लिए जावास्क्रिप्ट [सक्रिय](https://www.enable-javascript.com/) होना चाहिए।" </ins> [latest_release] other = "नवीनतम रिलीज़:"

Discussion:
Updated with new strings from Didn't remove any strings from , even if they're missing from
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
/language hi
Completed.
Change:
</tr> </tbody> </table>  No newline at end of file

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: According to and , so updated the generator and opened a PR which replaces most of string with , but and remain in these files: - Proposed Solution: Maybe we need to check/update the generator again, and then generate references again. Or, if the generator is fine, then we might update those files manually. Page to Update: ,,- ,,- ,meta/v1.Duration,-cacheDuration%20indicates%20the
for kubeadm, the change ~must~ can be done here: but we are in code freeze for 1.24, so let's wait until code freeze is lifted (19th of April) /sig cluster-lifecycle
/triage accepted
/sig node
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 /assign
/reopen The kubeadm reference is still on its way to be regenerated. The kubelet credential providers one is yet to be fixed.
Reopened this issue. <detailsIn response to : /reopen The kubeadm reference is still on its way to be regenerated. The kubelet credential providers one is yet to be fixed. 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
But I didn't find the link in this file . ,meta/v1.Duration,-cacheDuration%20indicates%20the page points to There are the only links that still exist in this directory : // For semantics around ctx use and closing/ending streaming RPCs, please refer to for example (Code generated by protoc-gen-gogo.

DO NOT EDIT.) If these links need to be updated, they need to be updated in or repository. This part of the update should be beyond the scope of Kubernetes.
Change:
## Node topology <del> {{< feature-state state="beta" for_k8s_version="v1.18" >}} </del> <ins> {{< feature-state state="stable" for_k8s_version="v1.27" >}} </ins> If you have enabled the `TopologyManager` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/), then

Discussion:
This is a Bug Report <!--Required Information--Problem: The of is mentioned under , which is wrong, As per mention in the the correct Feature state for is . Here is Upstream PR for it: Proposed Solution: Change the Feature State of from to . Page to Update:
/sig node /assign /triage accepted
Fixed it here:
/retitle Wrong feature state shown for TopologyManager
/language en
Change:
英語 | 日本語 --------- | --------- <del> cluster|クラスター orchestrate(動詞)|オーケストレーションする Persistent Volume|KubernetesリソースとしてのPersistentVolumeはママ表記、一般的な用語としての場合は、永続ボリューム Deployment/Deploy|KubernetesリソースとしてのDeploymentはママ表記、一般的な用語としてのdeployの場合は、デプロイ </del> Addon/Add-on|アドオン <del> Quota|クォータ For more information|さらなる情報(一時的) prefix | プレフィックス container | コンテナ directory | ディレクトリ </del> <ins> Aggregation Layer | アグリゲーションレイヤー architecture | アーキテクチャ </ins> binary | バイナリ <ins> cluster|クラスター community | コミュニティ container | コンテナ </ins> controller | コントローラー <del> operator | オペレーター Aggregation Layer | アグリゲーションレイヤー </del> <ins> Deployment/Deploy|KubernetesリソースとしてのDeploymentはママ表記、一般的な用語としてのdeployの場合は、デプロイ directory | ディレクトリ For more information|さらなる情報(一時的) GitHub | GitHub (ママ表記) </ins> Issue | Issue (ママ表記) <ins> operator | オペレーター orchestrate(動詞)|オーケストレーションする Persistent Volume|KubernetesリソースとしてのPersistentVolumeはママ表記、一般的な用語としての場合は、永続ボリューム prefix | プレフィックス </ins> Pull Request | Pull Request (ママ表記) <del> GitHub | GitHub (ママ表記) </del> <ins> Quota|クォータ </ins> registry | レジストリ <del> architecture | アーキテクチャ </del> secure | セキュア <del> stacked | 積層(例: stacked etcd clusterは積層etcdクラスター) </del> a set of ~ | ～の集合 <del> community | コミュニティ </del> <ins> stacked | 積層(例: stacked etcd clusterは積層etcdクラスター) </ins> ### 備考

Discussion:
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'd like to sort "", common words alphabetically in Japanese localization guide. Why is this needed It'll be easier to find a word in the list. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign