jiebi/CodeConvo huggingface dataset:
Code change:
<ins> --- title: ReplicaSet id: replica-set date: 2018-04-12 full_link: /ja/docs/concepts/workloads/controllers/replicaset/ short_description: > ReplicaSetは、指定された数のPodレプリカが一度に動作するように保証します。 aka: tags: - fundamental - core-object - workload --- ReplicaSetは、任意の時点で動作しているレプリカPodの集合を保持します。(保持することを目指します。) <!--more--> {{< glossary_tooltip term_id="deployment" >}}などのワークロードオブジェクトは、ReplicaSetの仕様に基づいて、 設定された数の{{< glossary_tooltip term_id="pod" text="Pods" >}}がクラスターで稼働することを保証するために、 ReplicaSetを使用します。 </ins>

Related discussion:
text: This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. It is needed for PR Comments /language ja /assign
/triage accepted
Code change:
<ins> --- title: ReplicaSet id: replica-set date: 2018-04-12 full_link: /ja/docs/concepts/workloads/controllers/replicaset/ short_description: > ReplicaSetは、指定された数のPodレプリカが一度に動作するように保証します。 aka: tags: - fundamental - core-object - workload --- ReplicaSetは、任意の時点で動作しているレプリカPodの集合を保持します。(保持することを目指します。) <!--more--> {{< glossary_tooltip term_id="deployment" >}}などのワークロードオブジェクトは、ReplicaSetの仕様に基づいて、 設定された数の{{< glossary_tooltip term_id="pod" text="Pods" >}}がクラスターで稼働することを保証するために、 ReplicaSetを使用します。 </ins>

Related discussion:
text: This is a Feature Request What would you like to be Create new directory and . Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign
/triage accepted
Code change:
<ins> # *Stop.  This guide has been superseded by [Minikube](../minikube/). The link below is present only for historical purposes* The document has been moved to [here](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/local-cluster/docker.md) </ins>

Related discussion:
text: I wish /docs/getting-started-guides/docker/ I wish this page existed
Code change:
<ins> # *Stop.  This guide has been superseded by [Minikube](../minikube/). The link below is present only for historical purposes* The document has been moved to [here](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/local-cluster/docker.md) </ins>

Related discussion:
text: I wish /docs/admin/dns/ linked correctly to the federation guide, at
Code change:
Attempt to drain the node on which `zk-2` is scheduled. ```shell <del> kubectl drain $(kubectl get pod zk-2 --template {{.spec.nodeName}}) --ignore-daemonsets --force --delete-local-data </del> <ins> kubectl drain $(kubectl get pod zk-2 --template {{.spec.nodeName}}) --ignore-daemonsets --force --delete-emptydir-data </ins> ``` The output:

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: Flag --delete-local-data has been deprecated, This option is deprecated and will be deleted. Use --delete-emptydir-data. I don’t know if it’s a good time to update this flag . If so, I can help update it. Proposed Solution: Update to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/sig cluster-lifecycle
cc
i see the discussion / PR here: using in the kubeadm docs makes sense. /triage accepted /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 : Flag --delete-local-data has been deprecated, This option is deprecated and will be deleted. Use --delete-emptydir-data. I don’t know if it’s a good time to update this flag . If so, I can help update it. /help </details
/assign
Code change:
1. Validate the binary (optional) <del> Download the kubectl-convert checksum file: </del> <ins> Download the `kubectl-convert` checksum file: </ins> ```powershell curl -LO "https://dl.k8s.io/{{< param "fullversion" >}}/bin/windows/amd64/kubectl-convert.exe.sha256" ``` <del> Validate the kubectl-convert binary against the checksum file: </del> <ins> Validate the `kubectl-convert` binary against the checksum file: </ins> - Using Command Prompt to manually compare `CertUtil`'s output to the checksum file downloaded:

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: In , the step No. 3 is talking about the location of binary, but actually in this section ("Install plugin") we should care about the location of binary, not of binary. Proposed Solution: In : And optionally, wrap these words with backquotes in : : kubectl L47: kubectl L62: kubectl L159: kubectl-convert L165: kubectl-convert (L180: kubectl-convert) - Already suggested above. Page to Update: )-,Append%20or%20prepend%20the%20kubectl%20binary%20folder%20to%20your%20PATH%20environment%20variable.,-Verify%20plugin%20is <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en
/triage accepted
/assign
Code change:
{{% tab name="Linux" %}} <!-- <del> 1. Install the `containerd.io` package from the official Docker repositories. Instructions for setting up the Docker repository for your respective Linux distribution and installing the `containerd.io` package can be found at [Install Docker Engine](https://docs.docker.com/engine/install/#server). </del> <ins> 1. Install the `containerd.io` package from the official Docker repositories. Instructions for setting up the Docker repository for your respective Linux distribution and installing the `containerd.io` package can be found at [Install Docker Engine](https://docs.docker.com/engine/install/#server). </ins> --> 1. 从官方Docker仓库安装 `containerd.io` 软件包。可以在 [安装 Docker 引擎](https://docs.docker.com/engine/install/#server)

Related discussion:
text: ! w sudo systemctl enable crio --now
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
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: Typo in zh/docs/setup/production-environment/container-runtimes Proposed Solution: -Page to Update: zh: (en: ) <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/retitle [zh] Typo in docs/setup/production-environment/container-runtimes /kind bug /language zh
Page is a little bit lagging behind. Will fix. /assign
Code change:
/docs/concepts/scheduling-eviction/eviction-policy/     /docs/concepts/scheduling-eviction/node-pressure-eviction/ 301 /docs/concepts/service-catalog/     /docs/concepts/extend-kubernetes/service-catalog/ 301 /docs/concepts/services-networking/networkpolicies/     /docs/concepts/services-networking/network-policies/ 301 <ins> /docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/     /docs/tasks/network/customize-hosts-file-for-pods/ 301 </ins> /docs/concepts/storage/etcd-store-api-object/     /docs/tasks/administer-cluster/configure-upgrade-etcd/ 301 /docs/concepts/storage/volumes/emptyDirapiVersion/     /docs/concepts/storage/volumes/#emptydir/ 301 /docs/concepts/tools/kubectl/object-management-overview/     /docs/concepts/overview/object-management-kubectl/overview/ 301

Related discussion:
text: Affected page: Move this page from Concepts to Tasks (potentially under Tasks Networking). Update to redirect the old URL to the new location (use a 301 code, similar to other entries in this file). /sig docs /language en
/triage accepted /help
/remove-help
I'd like to work on this one to learn something new in website page organizing. Thanks. /assign
Code change:
## kubeadm upgrade guidance <del> The steps for performing a upgrade using kubeadm are outlined in [this document](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/). </del> <ins> The steps for performing an upgrade using kubeadm are outlined in [this document](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/). </ins> For older versions of kubeadm, please refer to older documentation sets of the Kubernetes website. You can use `kubeadm upgrade diff` to see the changes that would be applied to static pod manifests.

Related discussion:
text: says: It should be AN upgrade.
/triage accepted /sig cluster-lifecycle /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 : /triage accepted /sig cluster-lifecycle /help </details
/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 : /good-first-issue </details
Thanks for reporting. I am willing to fix this issue. /assign
/language en
Should I work on this issue
/assign
Code change:
<ins> apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: example-ingress annotations: nginx.ingress.kubernetes.io/rewrite-target: /$1 spec: rules: - host: hello-world.info http: paths: - path: / pathType: Prefix backend: service: name: web port: number: 8080 </ins>  No newline at end of file

Related discussion:
text: This is a Bug Report Problem: it seems that there is wrong indentation example- Proposed Solution: change to: path: / backend: serviceName: web servicePort: 8080 instead of: path: / backend: serviceName: web servicePort: 8080 Page to Update: Additional Information: This is the error thrown: $ kubectl apply -f example- error: error validating "example-": error validating data: [ValidationError([0]): unknown field "backend" in , ValidationError([0][0]): missing required field "backend" in ]; if you choose to ignorethese errors, turn validation off with --validate=false $
Thank you for your submission and have tried to fix it. /kind bug /language en /assign
Code change:
For more information about the authentication process, refer to [Authentication](/docs/reference/access-authn-authz/authentication/#service-account-tokens). <del> ### Authenticating service account credentials in your own code {authenticating-in-code} </del> <ins> ### Authenticating service account credentials in your own code {#authenticating-in-code} </ins> If you have services of your own that need to validate Kubernetes service account credentials, you can use the following methods:

Related discussion:
text: No navigation panel says anything about bound service account tokens. describes service accounts and their non-bound tokens. mentions them in a 4-th level subsection under automation in the admission controller (which omits the fact that the kubelet is also involved in automating bound tokens, see ), but that subsection is omitted from the TOC because it is 4th level. Apparently that 3rd-level branch is only taking responsibility for describing service account automation in the admission controller. Bound service account tokens are an aspect of the authentication functionality that should be described on their own right, in the page on authentication.
/triage accepted
/sig auth
There isn't really a concept page on ServiceAccount. If there were, we could migrate the content to that concept page, and then hyperlink to that new section from its previous home.
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
In fact: /lifecycle frozen
/priority backlog
/sig security
is somewhat relevant
&hellip;until now:
I reckon will close this issue.
Code change:
if you have 3 registered clusters and you create a federated ReplicaSet with `spec.replicas = 9`, then each ReplicaSet in the 3 clusters will have `spec.replicas=3`. <del> To modify the number of replicas in each cluster, you can specify [FederatedReplicaSetPreference](https://github.com/kubernetes/federation/blob/{{page.githubbranch}}/apis/federation/types.go) as an annotation with key `federation.kubernetes.io/replica-set-preferences` on the federated ReplicaSet. </del> <ins> To modify the number of replicas in each cluster, you can add an annotation with key `federation.kubernetes.io/replica-set-preferences` to the federated ReplicaSet. The value of the annoation is a serialized JSON that contains fields shown in the following example: ``` { "rebalance": true, "clusters": { "foo": { "minReplicas": 10, "maxReplicas": 50, "weight": 100 }, "bar": { "minReplicas": 10, "maxReplicas": 100, "weight": 200 } } } ``` The `rebalance` boolean field specifies whether replicas already scheduled and running may be moved in order to match current state to the specified preferences. The `clusters` object field contains a map where users can specify the constraints for replica placement across the clusters (`foo` and `bar` in the example). For each cluster, you can specify the minimum number of replicas that should be assigned to it (default is zero), the maximum number of replicas the cluster can accept (default is unbounded) and a number expressing the relative weight of preferences to place additional replicas to that cluster. </ins> ## Updating a Federated ReplicaSet

Related discussion:
text: ClusterReplicaSetPreferences docs point to a source code file in the main repo This also happens in /docs/tasks/administer-federation/replicaset/
Do you mean FederatedReplicaSetPreference? I can't find ClusterReplicaSetPreference
exactly! FederatedReplicaSetPreference is correct. Sorry for it
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
/remove-lifecycle stale
/assign
Code change:
--> 仅当 `Guaranteed` Pod 中所有容器都被指定了请求和限制并且二者相等时，才保证 Pod 不被驱逐。 这些 Pod 永远不会因为另一个 Pod 的资源消耗而被驱逐。 <del> 如果系统守护进程（例如 `kubelet`、`docker` 和 `journald`） </del> <ins> 如果系统守护进程（例如 `kubelet` 和 `journald`） </ins> 消耗的资源比通过 `system-reserved` 或 `kube-reserved` 分配保留的资源多， 并且该节点只有 `Guaranteed` 或 `Burstable` Pod 使用的资源少于其上剩余的请求， 那么 kubelet 必须选择驱逐这些 Pod 中的一个以保持节点稳定性并减少资源匮乏对其他 Pod 的影响。

Related discussion:
text: There is a bug: ,%E8%AE%BE%E4%B8%BA%20%2D997%E3%80%82 ""'s hyperlink status is 404, it should be changed 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
/language zh /kind bug
/assign
Code change:
cgroupDriver: systemd ``` <ins> {{< note >}} Starting with v1.22 and later, when creating a cluster with kubeadm, if the user does not set the `cgroupDriver` field under `KubeletConfiguration`, kubeadm defaults it to `systemd`. {{< /note >}} </ins> If you configure `systemd` as the cgroup driver for the kubelet, you must also configure `systemd` as the cgroup driver for the container runtime. Refer to the documentation for your container runtime for instructions. For example:

Related discussion:
text: This section: I would add information like here: Note: In v1.22, if the user is not setting the cgroupDriver field under KubeletConfiguration, kubeadm will default it to systemd.
this section: already links to: PRs welcome with proposed improvements. /help /sig cluster-lifecycle
If someone wants to help here, I'm not sure what steps they should follow to assist. Because of that: /remove-help
/language en
I think the suggestion is to add something about to container-runtimes pages but I don't think that fits well on that page because it only covers the container runtime side. What could be though is that there's a note/reminder to ensure they are always the same. I can work on that if we agree what's what we want here.
hmm, looks like this is already covered too.
some additional feedback in
/triage accepted
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]:
/assign
Code change:
<ins> --- title: "通过 gcloud 安装 kubectl" description: "用各个特定操作系统标签页中包含的 gcloud 指令片段安装 kubectl。" headless: true --- <!-- --- title: "gcloud kubectl install" description: "How to install kubectl with gcloud snippet for inclusion in each OS-specific tab." headless: true --- --> <!-- You can install kubectl as part of the Google Cloud SDK. --> kubectl 可以作为 Google Cloud SDK 的一部分被安装。 <!-- 1. Install the [Google Cloud SDK](https://cloud.google.com/sdk/). 1. Run the `kubectl` installation command: --> 1. 安装 [Google Cloud SDK](https://cloud.google.com/sdk/)。 1. 运行安装 `kubectl` 的命令： ```shell gcloud components install kubectl ``` <!-- 1. Test to ensure the version you installed is up-to-date: --> 1. 验证一下，确保安装的是最新的版本： ```shell kubectl version --client ``` </ins>  No newline at end of file

Related discussion:
text: This is a Feature Request translate content/docs/tasks/tools/install-kubectl- into Chinese What would you like to be content/zh/docs/tasks/tools/install-kubectl- /assign /language zh
/triage accepted
Code change:
cat <<EOF >./kustomization.yaml configMapGenerator: - name: game-config-5 <del> labels: game-config: config-5 </del> <ins> options: labels: game-config: config-5 </ins> files: - game-special-key=configure-pod-container/configmap/game.properties EOF

Related discussion:
text: This is a Bug Report While applying written in is triggering an error Whereas by removing the labels from the and Applying the kustomization directory to create the ConfigMap object get created successfully. <!--Required Information--Problem: cat <<EOF Here is the configmap created previously. Proposed Solution: Update it with suitable answer. Refer : for kustomization update. 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
/sig docs /language en
The unknown field was in this commit and it was not supported refer to the code We can add labels via refer to I can help open a PR to update the code sections.
Code change:
* `apiserver_flowcontrol_priority_level_request_count_watermarks` is a histogram vector of high or low water marks of the number of requests broken down by the labels `phase` (which takes on the <del> values `waiting` and `executing`) and `priorityLevel`; the label </del> <ins> values `waiting` and `executing`) and `priority_level`; the label </ins> `mark` takes on values `high` and `low`.  The water marks are accumulated over windows bounded by the times when an observation was added to

Related discussion:
text: Keep the doc consistent with
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