jiebi/CodeConvo huggingface dataset:
Code change:
The value is a comma-separated list of the names of namespaces other than the parent's namespace in which objects are found. <del> ### applyset.kubernetes.io/contains-group-resources (alpha) {#applyset-kubernetes-io-contains-group-resources} </del> <ins> ### applyset.kubernetes.io/contains-group-kinds (alpha) {#applyset-kubernetes-io-contains-group-kinds} </ins> Type: Annotation <del> Example: `applyset.kubernetes.io/contains-group-resources: "certificates.cert-manager.io,configmaps,deployments.apps,secrets,services"` </del> <ins> Example: `applyset.kubernetes.io/contains-group-kinds: "certificates.cert-manager.io,configmaps,deployments.apps,secrets,services"` </ins> Used on: Objects being used as ApplySet parents.

Related discussion:
text: I'm not entirely sure if this is a bug, or if the documentation is just inaccurate/lacking some context, but it's at the very least a bit confusing. If you check the documentation for the well-known labels, etc., you can find the documentation for the annotation . ! However, when I try to reference a parent object with the option to without this annotation, it complains about the annotation missing: At this point my parent resource is declared as: It appears that I can set either one of the two ( or ) on the resource and will accept it; only in the latter case it appears to be copying the "resources" annotation to the add the "kinds" annotation. To phrase it another way: Setting the "kinds" annotation seems like the right way to go (but not what the documentation suggests), and setting the "resources" annotation works as well but you'll also end up with the "kinds" annotation afterwards. I expect the documentation and kubectl to align. Point at a resource that doesn't have the required annotations. No response <details</detailsnocloud No response No response No response No response
/sig docs /sig cli
This was changed in the code by and it seems that document needs changes to reflect this. Thank you bringing this issue /triage accepted
I think this should be transferred to the k/website so that the right annotation is recorded. /transfer wbsite
Something went wrong or the destination repo kubernetes/wbsite does not exist. <detailsIn response to : I think this should be transferred to the k/website so that the right annotation is recorded. /transfer wbsite 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
my bad !! /transfer website
/assign
Due to an implementation error with , in k8s v1.29 release this annotation was deprecated and the same is replaced by annotation. made this changes.
PR Raised .
Code change:
* コンテナランタイムがcgroup v2をサポートしていること。例えば、 * [containerd](https://containerd.io/) v1.4以降 * [cri-o](https://cri-o.io/) v1.20以降 <del> * kubeletとコンテナランタイムが[systemd cgroupドライバー](/docs/setup/production-environment/container-runtimes#systemd-cgroup-driver)を使うように設定されていること </del> <ins> * kubeletとコンテナランタイムが[systemd cgroupドライバー](/ja/docs/setup/production-environment/container-runtimes#systemd-cgroup-driver)を使うように設定されていること </ins> ### Linuxディストリビューションのcgroup v2サポート

Related discussion:
text: 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 Why is this needed Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --ref. /language ja
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 want to work on this. Have you already started working on it? It seems that some pages linked from here are not translated yet: dockershim-removal template For now, I'm going to start working on dockershim related contents. Feel free to notify me if this conflicts with your work.
I'll assign myself since you haven't assigned youself to this issue. Please tell me if this conflicts with you work. /assign
Code change:
You need to have a Kubernetes cluster, and the kubectl command-line tool must <del> be configured to communicate with your cluster. If you do not already have a </del> <ins> be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. If you do not already have a </ins> cluster, you can create one by using <del> [minikube](/docs/tasks/tools/#minikube) </del> <ins> [minikube](https://minikube.sigs.k8s.io/docs/tutorials/multi_node/) </ins> or you can use one of these Kubernetes playgrounds: * [Katacoda](https://www.katacoda.com/courses/kubernetes/playground)

Related discussion:
text: Source IP for Services with Type=ClusterIP Packets sent to ClusterIP from within the cluster are never source NAT'd if you're running kube-proxy in iptables mode, (the default). You can query the kube-proxy mode by fetching http://localhost:/proxyMode on the node where kube-proxy is running. kubectl get nodes The output is similar to this: NAME STATUS ROLES AGE VERSION kubernetes-node-6jst Ready <none2h v1.13.0 kubernetes-node-cx31 Ready <none2h v1.13.0 kubernetes-node-jj1t Ready <none2h v1.13.0 When I use kubectl get nodes there is no nodes available except NAME STATUS ROLES AGE VERSION minikube Ready control-plane,master 38m v1.20.2
Let's update to recommend running this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. /retitle Unclear requirements for “Using Source IP” tutorial
/triage accepted
The tutorial uses a cluster as an example setup throughout the document. <sub(The text in the screenshot below is the exact section referred in the issue description)</sub! But as pointed in the description of this issue: the section doesn't clearly state that it requires a multi-node cluster to follow through the doc examples. also, it mentions to create a cluster using which usually is taken as a single node (common) control-plane/worker-node setup. As suggested by the fix/solution would be to update the section to mention that it is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. You could also update the part by linking to this article talking about .
/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
/assign
Code change:
<ins> apiVersion: v1 kind: Pod metadata: name: dapi-test-pod spec: containers: - name: test-container image: k8s.gcr.io/busybox command: [ "/bin/sh", "-c", "echo $(SPECIAL_LEVEL_KEY) $(SPECIAL_TYPE_KEY)" ] env: - name: SPECIAL_LEVEL_KEY valueFrom: configMapKeyRef: name: special-config key: SPECIAL_LEVEL - name: SPECIAL_TYPE_KEY valueFrom: configMapKeyRef: name: special-config key: SPECIAL_TYPE restartPolicy: Never </ins>

Related discussion:
text: 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 Translate tasks/configure-pod-container/configure-pod-configmap/ into Japanese. Why is this needed This page has not been translated. Comments /language ja
/assign
/close
Closing this issue. <detailsIn response to : /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
Code change:
### Scheduled by default scheduler --> <del> ## 如何调度 Daemon Pods </del> <ins> ## Daemon Pods 是如何被调度的 </ins> ### 通过默认调度器调度

Related discussion:
text: “ DaemonSet spec.template.“ “”“”
Mind propose a fix?
/triage accepted
/language zh (I presume)
The label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : /language zh (I presume) 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
yes,this is chinese languge,“”change to“”
/assign
Code change:
other = "后一篇 >>" [layouts_case_studies_list_tell] <del> other = "分享您的故事" </del> <ins> other = "分享你的故事" </ins> [layouts_docs_glossary_aka] other = "亦称作"

Related discussion:
text: 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 zh-cn
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /language zh-cn 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
/sig-docs
/language zh
/triage accepted /assign
Code change:
[handbook-patch-release]: https://git.k8s.io/sig-release/release-engineering/role-handbooks/patch-release-team.md [k-sig-release-releases]: https://git.k8s.io/sig-release/releases [patches]: /patch-releases.md <del> [src]: https://git.k8s.io/community/committee-product-security/README.md </del> <ins> [src]: https://git.k8s.io/community/committee-security-response/README.md </ins> [release-team]: https://git.k8s.io/sig-release/release-team/README.md [security-release-process]: https://git.k8s.io/security/security-release-process.md

Related discussion:
text: This is a Bug Report <!--Required Information--Problem: All the hyperlinks which are pointing to this are broken. Proposed Solution: I suppose it should point to this now. Page to Update: /language en <!--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
Can I work on this?
/assign
Code change:
```json { "name": "k8s-pod-network", <del> "cniVersion": "0.3.0", </del> <ins> "cniVersion": "0.4.0", </ins> "plugins": [ { "type": "calico",

Related discussion:
text: says the minimal supported CNI interface version is 0.4.0 and specification-version 1.0.0 is recommended. Neverthesless the same webpage contains two examples with .
/assign
/language en /triage accepted
Code change:
| Feature | Description | CRDs | Aggregated API | | ------- | ----------- | ---- | -------------- | <del> | Validation | Help users prevent errors and allow you to evolve your API independently of your clients. These features are most useful when there are many clients who can't all update at the same time. | Yes.  Most validation can be specified in the CRD using [OpenAPI v3.0 validation](/docs/tasks/extend-kubernetes/extend-api-custom-resource-definitions/#validation).  Any other validations supported by addition of a [Validating Webhook](/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook-alpha-in-1-8-beta-in-1-9). | Yes, arbitrary validation checks | </del> <ins> | Validation | Help users prevent errors and allow you to evolve your API independently of your clients. These features are most useful when there are many clients who can't all update at the same time. | Yes.  Most validation can be specified in the CRD using [OpenAPI v3.0 validation](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#validation).  Any other validations supported by addition of a [Validating Webhook](/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook-alpha-in-1-8-beta-in-1-9). | Yes, arbitrary validation checks | </ins> | Defaulting | See above | Yes, either via [OpenAPI v3.0 validation](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#defaulting) `default` keyword (GA in 1.17), or via a [Mutating Webhook](/docs/reference/access-authn-authz/admission-controllers/#mutatingadmissionwebhook) (though this will not be run when reading from etcd for old objects). | Yes | | Multi-versioning | Allows serving the same object through two API versions. Can help ease API changes like renaming fields. Less important if you control your client versions. | [Yes](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning) | Yes | | Custom Storage | If you need storage with a different performance mode (for example, a time-series database instead of key-value store) or isolation for security (for example, encryption of sensitive information, etc.) | No | Yes |

Related discussion:
text: 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: At 181 line: Link to OpenAPI v3.0 validation is broken. Yes. Most validation can be specified in the CRD using . Proposed Solution: Yes. Most validation can be specified in the CRD using [OpenAPI v3.0 validation](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#validation). Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign
Code change:
* A compatible Linux host. The Kubernetes project provides generic instructions for Linux distributions based on Debian and Red Hat, and those distributions without a package manager. * 2 GB or more of RAM per machine (any less will leave little room for your apps). <del> * 2 CPUs or more. </del> <ins> * 2 CPUs or more for control plane machines. </ins> * Full network connectivity between all machines in the cluster (public or private network is fine). * Unique hostname, MAC address, and product_uuid for every node. See [here](#verify-mac-address) for more details. * Certain ports are open on your machines. See [here](#check-required-ports) for more details.

Related discussion:
text: Please note: This issue is not suitable for new contributors since you need some familiarity with how Kubernetes works. The Kubernetes website currently lacks a guide on creating Windows/Linux nodes. See for more details. SIG Windows opted to remove the guide that did exist for creating Windows nodes, in PR Write a new task page about creating nodes for all operating systems. This could, potentially, be in a tabbed format as mentions in the issue referenced above. We would also need the entry reflected on the creates the Linux task page by moving / refactoring the existing "join node" contents from the "create a cluster" page: creates the Windows task page by taking the content from at the end of the Windows page we add note/disclaimer whatever that says that CNI on Windows needs special handling and we link to the various CNI choices at: adds tabs in the to choose between OS for joining nodes. /priority backlog /help
This request has been marked as needing help from a contributor. 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 : Problem Statement: /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
/triage accepted Thank you for filing this
/sig cluster-lifecycle
If you know how to set up new nodes (with, at least, the tool): you can work on this issue. You don't need anyone's permission to open a pull request. All we ask is that you read our and that you abide by the project's code of conduct.
/assign
Relevant to
Are you still working on this issue?
/assign sending PR soon.
Code change:
* A compatible Linux host. The Kubernetes project provides generic instructions for Linux distributions based on Debian and Red Hat, and those distributions without a package manager. * 2 GB or more of RAM per machine (any less will leave little room for your apps). <del> * 2 CPUs or more. </del> <ins> * 2 CPUs or more for control plane machines. </ins> * Full network connectivity between all machines in the cluster (public or private network is fine). * Unique hostname, MAC address, and product_uuid for every node. See [here](#verify-mac-address) for more details. * Certain ports are open on your machines. See [here](#check-required-ports) for more details.

Related discussion:
text: /priority important-longterm
Relevant to
/retitle Write new task pages about creating Kubernetes nodes
/cc
Done in PR /close
Closing this issue. <detailsIn response to : Done in PR 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
Code change:
### 当使用 `kubeadm init`时的工作流程 当调用 `kubeadm init` 时，kubelet 的配置会被写入磁盘 `/var/lib/kubelet/config.yaml`， <del> 并上传到集群 `kubee-system` 命名空间的 `kubelet-config` ConfigMap。 </del> <ins> 并上传到集群 `kube-system` 命名空间的 `kubelet-config` ConfigMap。 </ins> kubelet 配置信息也被写入 `/etc/kubernetes/kubelet.conf`，其中包含集群内所有 kubelet 的基线配置。 此配置文件指向允许 kubelet 与 API 服务器通信的客户端证书。 这解决了[将集群级配置传播到每个 kubelet](#propagating-cluster-level-configuration-to-each-kubelet) 的需求。

Related discussion:
text: kubeadm init kubelet kubee-system kubelet-config ConfigMap kubelet kubelet kubelet API kube-system
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
Thanks for the feedback, a fix has been submitted. kube-system kubee-system
Code change:
title: "Production-Grade Container Orchestration" abstract: "Automated container deployment, scaling, and management" cid: home <ins> sitemap: priority: 1.0 </ins> --- {{< blocks/section id="oceanNodes" >}}

Related discussion:
text: 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 The Kubernetes website generates a sitemap. Let's highlight specific pages using priority weighting: (and any localization that copies the priority weight) (and any localization that copies the priority weight) (and any localization that copies the priority weight) Why is this needed: Making this change helps search engines understand what pages the Kubernetes project sees as important. Comments /kind feature
Code change:
* The root filesystem of the Node will be mounted at `/host`. * The container runs in the host IPC, Network, and PID namespaces, although the pod isn't privileged, so reading some process information may fail, <del> and `chroot /host` will fail. </del> <ins> and `chroot /host` may fail. </ins> * If you need a privileged pod, create it manually. Don't forget to clean up the debugging Pod when you're finished with it:

Related discussion:
text: This is a Bug Report Problem: Issue clarified privileges of kubectl debug node (through PR ) including " will fail" but in newer versions of Kubernetes 1.25 on EKS, works, although there may still be permissions issues as before. Proposed Solution: Change to " may fail" 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
Created PR
Code change:
other = "搜索" [version_check_mustbe] <del> other = "您的 Kubernetes 服务器版本必须是 " </del> <ins> other = "你的 Kubernetes 服务器版本必须是 " </ins> [version_check_mustbeorlater] <del> other = "您的 Kubernetes 服务器版本必须不低于版本 " </del> <ins> other = "你的 Kubernetes 服务器版本必须不低于版本 " </ins> [version_check_tocheck] other = "要获知版本信息，请输入 "

Related discussion:
text: 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 zh-cn
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /language zh-cn 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
/sig-docs
/language zh
/triage accepted /assign