jiebi/CodeConvo huggingface dataset:
Change:
One use case for selecting over labels is to constrain the set of nodes onto which a pod can schedule. See the documentation on [node selection](/docs/concepts/scheduling-eviction/assign-pod-node/) for more information. <ins> ## {{% heading "whatsnext" %}} - Learn how to [add a label to a node](/docs/tasks/configure-pod-container/assign-pods-nodes/#add-a-label-to-a-node) - Find [Well-known labels, Annotations and Taints](/docs/reference/labels-annotations-taints/) - See [Recommended labels](/docs/concepts/overview/working-with-objects/common-labels/) - [Enforce Pod Security Standards with Namespace Labels](/docs/tasks/configure-pod-container/enforce-standards-namespace-labels/) - [Use Labels effectively](/docs/concepts/cluster-administration/manage-deployment/#using-labels-effectively) to manage deployments. - Read a blog on [Writing a Controller for Pod Labels](/blog/2021/06/21/writing-a-controller-for-pod-labels/) </ins>

Discussion:
This is a Feature Request What would you like to be Add a “What's next” section to the concept page about Labels and Selector. Update: see for more details on what to put there Why is this needed In , some tasks and references can be incorporated to show usage of labels and selector.
/assign
/language en Where should we link to? (what URLs)
Hi i these links, they might help a new user to understand the extensive use of labels and find references to understand the same : Learn how to Find See to manage deployments. Read a blog on
/good-first-issue /triage accepted If people have questions about how to work on this, it's OK to ask.
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 : /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
Raised a PR here:
hello i would like to work on the issue can anyone one assign this to me?
it's polite to sync with other contributors - see - who have already started work.
Hi , I'm open to other suggestions or to explanations needed on the issue.You can check it out once if you have new references to add other than
Change:
## {{% heading "whatsnext" %}} <del> 独自のクラウドコントローラーマネージャーを構築および開発するには[クラウドコントローラーマネージャーの開発](/docs/tasks/administer-cluster/developing-cloud-controller-manager.md)を参照してください。 </del> <ins> 独自のクラウドコントローラーマネージャーを構築および開発するには[クラウドコントローラーマネージャーの開発](/ja/docs/tasks/administer-cluster/developing-cloud-controller-manager/)を参照してください。 </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. --It is about this page. I guess that Links to can be replaced with . Why is this needed has already been translated into Japanese. Comments /language ja where to update <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/triage accepted
/assign
Change:
ephemeral (rather than durable) entities. Pods are created, assigned a unique ID ([UID](/docs/concepts/overview/working-with-objects/names/#uids)), and scheduled to nodes where they remain until termination (according to restart policy) or <del> deletion. </del> <ins> deletion. </ins> If a {{< glossary_tooltip term_id="node" >}} dies, the Pods scheduled to that node are [scheduled for deletion](#pod-garbage-collection) after a timeout period.

Discussion:
Second sentence of the second paragraph is obviously incomplete. It reads like this . ! It would be good to restore missing bit.
Page is PR introduced the regression; I suggest the second “handles” should instead read “determines what action to take to make the Pod healthy again”. /kind bug /language en /triage accepted /priority backlog Thanks
/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
Change:
请查看 [limitRange 设计文档](https://git.k8s.io/community/contributors/design-proposals/resource-management/admission_control_limit_range.md) 和 [Limit Range 例子](/docs/tasks/configure-pod-container/limit-range/)了解更多细节。 <del> ### MutatingAdmissionWebhook {#mutatingadmissionwebhook} {{< feature-state for_k8s_version="v1.13" state="beta" >}} </del> <ins> ### MutatingAdmissionWebhook {#mutatingadmissionwebhook} {{< feature-state for_k8s_version="v1.13" state="beta" >}} </ins> <!-- This admission controller calls any mutating webhooks which match the request. Matching

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: Page /zh/docs/reference/access-authn-authz/admission-controllers/ display abnormally, these anchor points should start on a new line. Proposed Solution: fix the anchor point format. abnormal format: normal format: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign /language zh
Change:
```yaml tolerations: <del> - key: "key" </del> <ins> - key: "key1" </ins> operator: "Equal" <del> value: "value" </del> <ins> value: "value1" </ins> effect: "NoSchedule" ``` ```yaml tolerations: <del> - key: "key" </del> <ins> - key: "key1" </ins> operator: "Exists" effect: "NoSchedule" ```

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 Update to use a key of rather than , and a value of rather than . Why is this needed Some sections of Taints and Tolerations concept page suggest setting a taint where the key is called and the value is . This is confusing because when the reader sees example commands they are unsure whether represents the literal text or the example. This change will help clear up that confusion. Comments /language en /good first issue
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
It's also OK to use and rather than my suggestion of and . Whichever you prefer.
/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
/assign
Change:
<!-- overview --> <del> このチュートリアルでは、[Minikube](/ja/docs/setup/learning-environment/minikube)とKatacodaを使用して、Kubernetes上でサンプルアプリケーションを動かす方法を紹介します。Katacodaはブラウザで無償のKubernetes環境を提供します。 </del> <ins> このチュートリアルでは、[minikube](/ja/docs/setup/learning-environment/minikube)とKatacodaを使用して、Kubernetes上でサンプルアプリケーションを動かす方法を紹介します。Katacodaはブラウザで無償のKubernetes環境を提供します。 </ins> {{< note >}} <del> [Minikubeをローカルにインストール](https://minikube.sigs.k8s.io/docs/start/)している場合もこのチュートリアルを進めることが可能です。 </del> <ins> [minikubeをローカルにインストール](https://minikube.sigs.k8s.io/docs/start/)している場合もこのチュートリアルを進めることが可能です。 </ins> {{< /note >}}

Discussion:
This is a Feature Request In the documentation available in , as well as in the link, the term is written as . I'd like to suggest updating it to to align with the and . <!-- 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 Change occurrences of to . Why is this needed Using the incorrect casing can be misleading, especially for newcomers. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/assign
/language ja
/triage accepted
Change:
To reflect the change on kubeadm nodes you must do the following: - Log in to a kubeadm node - Run `kubeadm upgrade node phase kubelet-config` to download the latest `kubelet-config` <del> ConfigMap contents into the local file `/var/lib/kubelet/config.conf` </del> <ins> ConfigMap contents into the local file `/var/lib/kubelet/config.yaml` </ins> - Edit the file `/var/lib/kubelet/kubeadm-flags.env` to apply additional configuration with flags - Restart the kubelet service with `systemctl restart kubelet`

Discussion:
Run kubeadm upgrade node phase kubelet-config to download the latest kubelet-config ConfigMap contents into the local file The local file name should be
Page related to issue: /language en
/retitle Incorrect file mentioned in command
/sig cluster-lifecycle
plz I want help to fix this /assign
FYI, the same incorrect filename exists in other places on the same page. Two are in the second blue-barred Note pane below the command, and three are further down in the section
(or other maintainers) Can I get confirmation and go ahead please; if this be a tirage-accepted issue to that i can proceed with the fix.
/triage accepted /kind bug Thanks for spotting this.
I have attempt to make fix for this in
Change:
container, and if users use the [node allocatable](/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable) feature, out of resource decisions are made local to the end user Pod part of the cgroup hierarchy as well as the <del> root node. This [script](/docs/tasks/administer-cluster/memory-available.sh) </del> <ins> root node. This [script](/examples/admin/resource/memory-available.sh) </ins> reproduces the same set of steps that the `kubelet` performs to calculate `memory.available`. The `kubelet` excludes inactive_file (i.e. # of bytes of file-backed memory on inactive LRU list) from its calculation as it assumes that

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: There is a broken link to script in tasks/administer-cluster/out-of- file. At 44 line: Proposed Solution: Move the script file to examples directory. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign
Change:
To apply: 1. Open a pull request adding yourself to a section of the <del> [OWNERS_ALIASES](https://github.com/kubernetes/website/blob/main/OWNERS) </del> <ins> [OWNERS_ALIASES](https://github.com/kubernetes/website/blob/main/OWNERS_ALIASES) </ins> file in the `kubernetes/website` repository. {{< note >}}

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: In and , links go to , which is wrong. They should go to . Proposed Solution: Find , and replace with . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en /kind cleanup /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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: In and , Find , and replace with . Page to Update: <!--Kubernetes Version:--/language en /kind cleanup /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
/triage accepted
/assign
Change:
<ins> apiVersion: v1 kind: Service metadata: name: my-service labels: app: MyApp spec: ipFamilyPolicy: PreferDualStack selector: app: MyApp ports: - protocol: TCP port: 80 </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
/triage accepted
Change:
<ins> --- title: ノードリソースマネージャー content_type: concept weight: 50 --- <!-- overview --> レイテンシーが致命的なワークロードや高スループットのワークロードをサポートするために、Kubernetesは一連のリソースマネージャーを提供します。リソースマネージャーはCPUやデバイス、メモリ(hugepages)などのリソースの特定の要件が設定されたPodのためにノードリソースの調整と最適化を目指しています。 <!-- body --> メインのマネージャーであるトポロジーマネージャーは[ポリシー](/ja/docs/tasks/administer-cluster/topology-manager/)に沿って全体のリソース管理プロセスを調整するKubeletコンポーネントです。 個々のマネージャーの設定は下記のドキュメントで詳しく説明されてます。 - [CPUマネージャーポリシー](/docs/tasks/administer-cluster/cpu-management-policies/) - [デバイスポリシー](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#device-plugin-integration-with-the-topology-manager) - [メモリマネージャーポリシー](/docs/tasks/administer-cluster/memory-manager/) </ins>

Discussion:
This is a Feature Request What would you like to be Translate docs/concepts/policy/node-resource- into Japanese Why is this needed There is no Japanese translation for this page Comments File to translate: Original: /area localization /language ja /assign
/area localization /language ja /assign
404
/triage accepted
Change:
--- title: Kubernetes 安全和信息披露 <del> aliases: [security/] </del> content_type: concept weight: 20 ---

Discussion:
This is a Bug Report Problem: The dockershim alias () now directs to the Chinese localized version () because the same alias exists in multiple files. Proposed Solution: Removal of the alias in the Chinese version of the blog post or updated to be A policy or linter might be worth putting in place for aliases as well to prevent future issues. Page to Update:
/triage accepted /kind bug /language zh
A similar problem occurred some time ago with aliases in security. I just checked a few other files. Aliases field is set: content/zh/docs/reference/issues- content/zh/docs/reference/issues- Aliases field not set (set in version): content/zh/docs/reference/access-authn- Should add a note to the localization or documentation about how to update the field.
/assign
Change:
The flow control API involves two kinds of resources. [PriorityLevelConfigurations](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io) <del> define the available isolation classes, the share of the available concurrency </del> <ins> define the available priority levels, the share of the available concurrency </ins> budget that each can handle, and allow for fine-tuning queuing behavior. [FlowSchemas](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#flowschema-v1beta2-flowcontrol-apiserver-k8s-io) are used to classify individual inbound requests, matching each to a

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: Someone reading was not able to discern the intended meaning of the term "isolation class". See . This term is only used twice, and is used in a way that is synonymous with another term already introduced ("priority level"). I think it would be clearer to replace "isolation class" with "priority level". Proposed Solution: Replace "isolation class" with "priority level". Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--This has been there for a while. <!--Additional Information:--
/assign
/triage accepted
This is what I originally posted in the #api-priority-and-fairness Slack channel. Thanks for filing this on GitHub, Mike. !
Change:
Issues should be sorted into different buckets of work using the following labels and definitions. If an issue doesn't have enough information to identify a problem that can be researched, reviewed, or worked on (i.e. the issue doesn't fit into any of the categories below) you should close the issue with a comment explaining why it is being closed. ### Needs Clarification <del> * Issues that need more information from the original submitter to make them actionable.  Issues with this label that aren't followed up within a week may be closed. </del> <ins> * Issues that need more information from the original submitter to make them actionable.  Issues with this label that aren't followed up within a week may be closed. </ins> ### Actionable * Issues that can be worked on with current information (or may need a comment to explain what needs to be done to make it more clear)

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... [ ] Feature Request [x] Bug Report Problem: For users using K8S versions 1.8 and lower that don't have the fix contained in it may be necessary to set for the OpenStack cloud provider when installing on OpenStack clusters that expose their Cinder endpoint using paths rather than ports to avoid auto-detection errors such as: This includes for users trying out K8S on a devstack environment, and potentially other deployment tools. In this situation it is possible to resolve using: Valid values for are: With being the default. Proposed Solution: Highlight the bs-version parameter as optional (so not minimal configuration) but required in some circumstances. Page to Update:
Change:
TLDs](https://data.iana.org/TLD/tlds-alpha-by-domain.txt). --> 为了缓解这类问题，需要将创建名字空间的权限授予可信的用户。 <del> 如果需要，你可以额外部署第三方的安全控制机制，例如以 [准入 Webhook](/zh-cn/docs/reference/access-authn-authz/extensible-admission-controllers/) </del> <ins> 如果需要，你可以额外部署第三方的安全控制机制， 例如以[准入 Webhook](/zh-cn/docs/reference/access-authn-authz/extensible-admission-controllers/) </ins> 的形式，阻止用户创建与公共 [TLD](https://data.iana.org/TLD/tlds-alpha-by-domain.txt) 同名的名字空间。 {{< /warning >}}

Discussion:
markdown <img width="681" alt="WX20220809- src="https://user-"
page: /triage accepted /assign
namespace
Change:
バグを報告する場合は、そのバグを再現するための詳細な情報を含めてください。 * Kubernetes のバージョン: `kubectl version` <del> * クラウドプロバイダー、OSディストリビューション、ネットワーク構成、Dockerバージョン </del> <ins> * クラウドプロバイダー、OSディストリビューション、ネットワーク構成、コンテナランタイムバージョン </ins> * 問題を再現するための手順

Discussion:
This is a Feature Request What would you like to be We need to update according to the English text, because it is outdated. Why is this needed "Questions", "Stack Overflow" and "Bugs and feature requests" sections are outdated. Questions: Change the URL /docs/reference/kubectl/overview/ to /docs/reference/kubectl/ for . Stack Overflow: Update the statement for how to ask a new question. Bugs and feature requests: Change "Docker version" to "container runtime version". Comments /language ja
/triage accepted
/assign
Change:
### kubelet [kubelet](/docs/admin/kubelet) is the primary node agent. It: * Watches for pods that have been assigned to its node (either by apiserver or via local configuration file) and: <del> * Mounts the pod's required volumes * Downloads the pod's secrets * Run the pod's containers via docker (or, experimentally, rkt). * Periodically executes any requested container liveness probes. * Reports the status of the pod back to the rest of the system, by creating a "mirror pod" if necessary. </del> <ins> * Mounts the pod's required volumes * Downloads the pod's secrets * Run the pod's containers via docker (or, experimentally, rkt). * Periodically executes any requested container liveness probes. * Reports the status of the pod back to the rest of the system, by creating a "mirror pod" if necessary. </ins> * Reports the status of the node back to the rest of the system. ### kube-proxy

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: is used but it has already been deprecated and this is v1 section. ! Proposed Solution: It should be replaced with . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--