jiebi/CodeConvo huggingface dataset:
Change:
translate setup/production-environment/turnkey- into Chinese
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 zh

Discussion:
<ins> --- title: Turnkey 云解决方案 content_type: concept weight: 30 --- <!-- --- title: Turnkey Cloud Solutions content_type: concept weight: 30 --- --> <!-- overview --> <!-- This page provides a list of Kubernetes certified solution providers. From each provider page, you can learn how to install and setup production ready clusters. --> 本页列示 Kubernetes 认证解决方案供应商。 在每一个供应商分页，你可以学习如何安装和设置生产就绪的集群。 <!-- body --> {{< cncf-landscape helpers=true category="certified-kubernetes-hosted" >}} </ins>
Change:
Some solutions are repeted in the list
/triage accepted It is not the solutions that are repeated. It is the icon. This worth a fix. /assign

Discussion:
{{- end -}} <div id="frameHolder"> {{ if ( .Get "category" ) }} <del> <iframe frameborder="0" id="landscape" scrolling="no" src="https://landscape.cncf.io/category={{ .Get "category" }}&format=logo-mode&grouping=category&embed=yes" style="width: 1px; min-width: 100%"></iframe> </del> <ins> <iframe frameborder="0" id="landscape" scrolling="no" src="https://landscape.cncf.io/category={{ .Get "category" }}&format=card-mode&grouping=category&embed=yes" style="width: 1px; min-width: 100%"></iframe> </ins> {{ else }} <del> <iframe frameborder="0" id="landscape" scrolling="no" src="https://landscape.cncf.io/format=logo-mode;embed=yes" style="width: 1px; min-width: 100%" title="CNCF Landscape"></iframe> </del> <ins> <iframe frameborder="0" id="landscape" scrolling="no" src="https://landscape.cncf.io/format=card-mode;embed=yes" style="width: 1px; min-width: 100%" title="CNCF Landscape"></iframe> </ins> {{ end }} <script src="https://landscape.cncf.io/iframeResizer.js"></script> </div>
Change:
Example: kubectl get pod -f error: when paths, URLs, or stdin is provided as input, you may not specify resource arguments as well The example should be "kubectl get -f ".
/triage accepted /kind bug /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 : /triage accepted /kind bug /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

Discussion:
* To specify resources with one or more files:  `-f file1 -f file2 -f file<#>` * [Use YAML rather than JSON](/docs/concepts/configuration/overview/#general-configuration-tips) since YAML tends to be more user-friendly, especially for configuration files.<br/> <del> Example: `kubectl get pod -f ./pod.yaml` </del> <ins> Example: `kubectl get -f ./pod.yaml` </ins> * `flags`: Specifies optional flags. For example, you can use the `-s` or `--server` flags to specify the address and port of the Kubernetes API server.<br/>
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: Submodule need to updatecurrent version lack of i18n translation for Upgrade of can solve this problem, see it in ! <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/kind bug /triage accepted /priority backlog /good-first-issue This issue is a good first issue because the single step needed to fix it is to update the version of the submodule.  has some contextual information; the command to use is .
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 : /kind bug /triage accepted /priority backlog /good-first-issue  has some contextual information; the command to use is . 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
:information_source: Note that PR is already open to address this.
/remove-label "help wanted"

Discussion:
[options_heading] other = "选项" <ins> [post_create_child_page] other = "创建子页面" </ins> [prerequisites_heading] other = "准备开始"
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 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

Discussion:
For example, ```shell <del> kubectl taint nodes node1 key=value:NoSchedule </del> <ins> kubectl taint nodes node1 key1=value1:NoSchedule </ins> ``` <del> places a taint on node `node1`. The taint has key `key`, value `value`, and taint effect `NoSchedule`. </del> <ins> places a taint on node `node1`. The taint has key `key1`, value `value1`, and taint effect `NoSchedule`. </ins> This means that no pod will be able to schedule onto `node1` unless it has a matching toleration. To remove the taint added by the command above, you can run: ```shell <del> kubectl taint nodes node1 key=value:NoSchedule- </del> <ins> kubectl taint nodes node1 key1=value1:NoSchedule- </ins> ``` You specify a toleration for a pod in the PodSpec. Both of the following tolerations "match" the

```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" ```

An empty `key` with operator `Exists` matches all keys, values and effects which means this will tolerate everything. <del> An empty `effect` matches all effects with key `key`. </del> <ins> An empty `effect` matches all effects with key `key1`. </ins> {{< /note >}}
Change:
In the second sentence of the first paragraph under : "This tool it requires that you have Docker installed and configured." Is it better to remove "it"? My suggestion is remove "it" "This tool requires that you have Docker installed and configured."
/triage accepted /language en /kind bug /good-first-issue /priority backlog Thanks - I agree with your suggested fix.
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 : /triage accepted /language en /kind bug /good-first-issue /priority backlog 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

Discussion:
## kind [`kind`](https://kind.sigs.k8s.io/docs/) lets you run Kubernetes on <del> your local computer. This tool it requires that you have </del> <ins> your local computer. This tool requires that you have </ins> [Docker](https://docs.docker.com/get-docker/) installed and configured. The kind [Quick Start](https://kind.sigs.k8s.io/docs/user/quick-start/) page
Change:
In the section, the annotation documentation gives possible values of //, but the description describes and . There's a more-detailed behaviour description in which might be useful to draw from.
Good point, let me send a quick fix.
/triage accepted
/kind cleanup /language en

Discussion:
| Golang marker | OpenAPI extension | Accepted values | Description | Introduced in | |---|---|---|---|---| <del> | `//+listType` | `x-kubernetes-list-type` | `atomic`/`set`/`map` | Applicable to lists. `atomic` and `set` apply to lists with scalar elements only. `map` applies to lists of nested types only. If configured as `atomic`, the entire list is replaced during merge; a single manager manages the list as a whole at any one time. If `granular`, different managers can manage entries separately. | 1.16          | </del> <ins> | `//+listType` | `x-kubernetes-list-type` | `atomic`/`set`/`map` | Applicable to lists. `atomic` and `set` apply to lists with scalar elements only. `map` applies to lists of nested types only. If configured as `atomic`, the entire list is replaced during merge; a single manager manages the list as a whole at any one time. If `set` or `map`, different managers can manage entries separately. | 1.16          | </ins> | `//+listMapKey` | `x-kubernetes-list-map-keys` | Slice of map keys that uniquely identify entries for example `["port", "protocol"]` | Only applicable when `+listType=map`. A slice of strings whose values in combination must uniquely identify list entries. While there can be multiple keys, `listMapKey` is singular because keys need to be specified individually in the Go type. | 1.16 | | `//+mapType` | `x-kubernetes-map-type` | `atomic`/`granular` | Applicable to maps. `atomic` means that the map can only be entirely replaced by a single manager. `granular` means that the map supports separate managers updating individual fields. | 1.17 | | `//+structType` | `x-kubernetes-map-type` | `atomic`/`granular` | Applicable to structs; otherwise same usage and OpenAPI annotation as `//+mapType`.| 1.17 |
Change:
Translate docs/tasks/administer-cluster/enable-disable-api/ into Chinese
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 /assign

Discussion:
<ins> --- title: 启用/禁用 Kubernetes API content_type: task --- <!-- --- title: Enable Or Disable A Kubernetes API content_type: task --- --> <!-- overview --> <!-- This page shows how to enable or disable an API version from your cluster's {{< glossary_tooltip text="control plane" term_id="control-plane" >}}. --> 本页展示怎么用集群的 {{< glossary_tooltip text="控制平面" term_id="control-plane" >}}. 启用/禁用 API 版本。 <!-- steps --> <!-- Specific API versions can be turned on or off by passing `--runtime-config=api/<version>` as a command line argument to the API server. The values for this argument are a comma-separated list of API versions. Later values override earlier values. The `runtime-config` command line argument also supports 2 special keys: --> 通过 API 服务器的命令行参数 `--runtime-config=api/<version>` ， 可以开启/关闭某个指定的 API 版本。 此参数的值是一个逗号分隔的 API 版本列表。 此列表中，后面的值可以覆盖前面的值。 命令行参数 `runtime-config` 支持两个特殊的值（keys）： <!-- - `api/all`, representing all known APIs - `api/legacy`, representing only legacy APIs. Legacy APIs are any APIs that have been explicitly [deprecated](/zh/docs/reference/using-api/deprecation-policy/). For example, to turning off all API versions except v1, pass `--runtime-config=api/all=false,api/v1=true` to the `kube-apiserver`. --> - `api/all`：指所有已知的 API - `api/legacy`：指过时的 API。过时的 API 就是明确地 [弃用](/zh/docs/reference/using-api/deprecation-policy/) 的 API。 例如：为了停用除去 v1 版本之外的全部其他 API 版本， 就用参数 `--runtime-config=api/all=false,api/v1=true` 启动 `kube-apiserver`。 ## {{% heading "whatsnext" %}} <!-- Read the [full documentation](/docs/reference/command-line-tools-reference/kube-apiserver/) for the `kube-apiserver` component. --> 阅读[完整的文档](/zh/docs/reference/command-line-tools-reference/kube-apiserver/), 以了解 `kube-apiserver` 组件。 </ins>  No newline at end of file
Change:
This is a Feature Request What would you like to be Replace the sequence diagram on with the one by . This is the follow-up of . Why is this needed There are several pros to use mermaid to draw the sequence diagram: mermaid format is more readable easy to modify better styling Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/assign
/kind cleanup /language en /triage accepted /priority backlog

Discussion:
max-width: 80%; border: 1px solid rgb(222, 226, 230); border-radius: 5px; <ins> margin-bottom: 1rem; padding-top: 1rem; padding-bottom: 1rem; // mermaid diagram - sequence diagram .actor { fill: #326ce5 !important; } text.actor { font-size: 18px !important; stroke: white !important; fill: white !important; } .activation0 { fill: #c9e9ec !important; } </ins> } /* HEADER */

as a bearer token.  See [above](#putting-a-bearer-token-in-a-request) for how the token is included in a request. <del> ![Kubernetes OpenID Connect Flow](/images/docs/admin/k8s_oidc_login.svg) </del> <ins> {{< mermaid >}} sequenceDiagram participant user as User participant idp as Identity Provider participant kube as Kubectl participant api as API Server user ->> idp: 1. Login to IdP activate idp idp -->> user: 2. Provide access_token,<br>id_token, and refresh_token deactivate idp activate user user ->> kube: 3. Call Kubectl<br>with --token being the id_token<br>OR add tokens to .kube/config deactivate user activate kube kube ->> api: 4. Authorization: Bearer... deactivate kube activate api api ->> api: 5. Is JWT signature valid? api ->> api: 6. Has the JWT expired?(iat+exp) api ->> api: 7. user authorized? api -->> kube: 8. Authorized: Perform<br>action and return result deactivate api activate kube kube --x user: 9. Return result deactivate kube {{< /mermaid >}} </ins> 1.  Login to your identity provider 2.  Your identity provider will provide you with an `access_token`, `id_token` and a `refresh_token`
Change:
The below sentence is there towards the end of this page: (If you didn't already try creating a application and deploying it using a container, you can do that first by following the instructions from the Hello Minikube tutorial). But the "Hello Minkube" tutorial link has nothing about creating any application or deploying it.
This is indeed a documentation bug. The v1.4 echoserver uses NGINX without Good spot, /kind bug /language en /triage accepted /priority backlog
/assign

Discussion:
<div class="row"> <div class="col-md-8"> <p> <del> For your first Deployment, you'll use a Node.js application packaged in a Docker container. (If you didn't already try creating a Node.js application and deploying it using a container, you can do that first by following the instructions from the <a href="/docs/tutorials/hello-minikube/">Hello Minikube tutorial</a>). </del> <ins> For your first Deployment, you'll use a hello-node application packaged in a Docker container that uses NGINX to echo back all the requests. (If you didn't already try creating a hello-node application and deploying it using a container, you can do that first by following the instructions from the <a href="/docs/tutorials/hello-minikube/">Hello Minikube tutorial</a>). </ins> <p> <p>Now that you know what Deployments are, let's go to the online tutorial and deploy our first app!</p>
Change:
In this document () service type External name is explained as follows: ExternalName - Exposes the Service using an arbitrary name (specified by externalName in the spec) by returning a CNAME record with the name. No proxy is used. This type requires v1.7 or higher of kube-dns. This is misleading. The correct explanation could be (from ) as follows: ExternalName: Maps the Service to the contents of the externalName field (e.g. ), by returning a CNAME record with its value. No proxying of any kind is set up. This type requires v1.7 or higher of kube-dns, or coreDNS version 0.0.8 or higher.
/sig network /kind cleanup /triage accepted
Thanks - that's worth fixing /priority backlog
/assign
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-contributor-experience at . /lifecycle stale

Discussion:
<li><i>ClusterIP</i> (default) - Exposes the Service on an internal IP in the cluster. This type makes the Service only reachable from within the cluster.</li> <li><i>NodePort</i> - Exposes the Service on the same port of each selected Node in the cluster using NAT. Makes a Service accessible from outside the cluster using <code>&lt;NodeIP&gt;:&lt;NodePort&gt;</code>. Superset of ClusterIP.</li> <li><i>LoadBalancer</i> - Creates an external load balancer in the current cloud (if supported) and assigns a fixed, external IP to the Service. Superset of NodePort.</li> <del> <li><i>ExternalName</i> - Exposes the Service using an arbitrary name (specified by <code>externalName</code> in the spec) by returning a CNAME record with the name. No proxy is used. This type requires v1.7 or higher of <code>kube-dns</code>.</li> </del> <ins> <li><i>ExternalName</i> - Maps the Service to the contents of the <code>externalName</code> field (e.g. `foo.bar.example.com`), by returning a <code>CNAME</code> record with its value. No proxying of any kind is set up. This type requires v1.7 or higher of <code>kube-dns</code>, or CoreDNS version 0.0.8 or higher.</li> </ins> </ul> <p>More information about the different types of Services can be found in the <a href="/docs/tutorials/services/source-ip/">Using Source IP</a> tutorial. Also see <a href="/docs/concepts/services-networking/connect-applications-service">Connecting Applications with Services</a>.</p> <p>Additionally, note that there are some use cases with Services that involve not defining <code>selector</code> in the spec. A Service created without <code>selector</code> will also not create the corresponding Endpoints object. This allows users to manually map a Service to specific endpoints. Another possibility why there may be no selector is you are strictly using <code>type: ExternalName</code>.</p>
Change:
Links are broken on this page:
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
/retitle Broken link in article /language en /area blog
/assign
will you please test the fix @ https://deploy-preview---kubernetes-io-master-

Discussion:
In order to use the Kubernetes Volume Snapshot feature, you must ensure the following components have been deployed on your Kubernetes cluster: <del> - [Kubernetes Volume Snapshot CRDs](https://github.com/kubernetes-csi/external-snapshotter/tree/master/config/crd) </del> <ins> - [Kubernetes Volume Snapshot CRDs](https://github.com/kubernetes-csi/external-snapshotter/tree/53469c21962339229dd150cbba50c34359acec73/config/crd) </ins> - [Volume snapshot controller](https://github.com/kubernetes-csi/external-snapshotter/tree/master/pkg/common-controller) - CSI Driver supporting Kubernetes volume snapshot beta

#### Install Snapshot Beta CRDs - `kubectl create -f config/crd` <del> - [https://github.com/kubernetes-csi/external-snapshotter/tree/master/config/crd](https://github.com/kubernetes-csi/external-snapshotter/tree/master/config/crd) </del> <ins> - [https://github.com/kubernetes-csi/external-snapshotter/tree/53469c21962339229dd150cbba50c34359acec73/config/crd](https://github.com/kubernetes-csi/external-snapshotter/tree/53469c21962339229dd150cbba50c34359acec73/config/crd) </ins> - Do this once per cluster
Change:
begins by stating: I suggest appending the following sentence: This was not obvious to me. In other programming contexts, multiple handlers per event are allowed; for example, in client-side JavaScript, more than one click handler may be specified.
/kind feature /language en /priority backlog /triage accepted /good-first-issue That's a nice improvement.
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 : /kind feature /language en /priority backlog /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
/assign

Discussion:
This page shows how to attach handlers to Container lifecycle events. Kubernetes supports the postStart and preStop events. Kubernetes sends the postStart event immediately after a Container is started, and it sends the preStop event immediately before the <del> Container is terminated. </del> <ins> Container is terminated. A Container may specify one handler per event. </ins>
Change:
This is a Feature Request What would you like to be Add a caution note to the Concepts document article for Secrets, warning that SSH private keys do not establish fully trusted communication between clients and host servers. Why is this needed SSH key pairs provide a means of establishing authenticated communication between two parties, but not trusted communication between two parties. Trust can only be established via a secondary means, like a file. Without establishing trust, applications which utilize SSH keys by themselves for authentication are susceptible to "man in the middle" attacks. Comments This item was discussed during the first SIG Docs Security subproject meeting.
/sig security /triage accepted
/priority important-longterm Thanks

Discussion:
and the API server does verify if the required keys are provided in a Secret configuration. <ins> {{< caution >}} SSH private keys do not establish trusted communication between an SSH client and host server on their own. A secondary means of establishing trust is needed to mitigate "man in the middle" attacks, such as a `known_hosts` file added to a ConfigMap. {{< /caution >}} </ins> ### TLS secrets Kubernetes provides a builtin Secret type `kubernetes.io/tls` for to storing