jiebi/CodeConvo huggingface dataset:
Change:
<ins> --- linktitle: Historique des versions title: Versions type: docs --- <!-- overview --> Le projet Kubernetes maintient des branches de versions pour les trois versions mineures les plus récentes ({{< skew latestVersion >}}, {{< skew prevMinorVersion >}}, {{< skew oldestMinorVersion >}}). Kubernetes 1.19 et plus récent reçoivent [environ 1 an de support de correctifs](/releases/patch-releases/#support-period). Kubernetes 1.18 et plus ancien ont reçu environ 9 mois de support de correctifs. Les versions de Kubernetes sont exprimées sous la forme **x.y.z**, où **x** est la version majeure, **y** est la version mineure et **z** est la version du correctif, selon la terminologie de [Gestion sémantique de version](https://semver.org/lang/fr/). Plus d'informations dans le document sur la [politique en matière de version](/releases/version-skew-policy/). <!-- body --> ## Historique des versions {{< release-data >}} ## Publication à venir Consultez la [planification](https://github.com/kubernetes/sig-release/tree/master/releases/release-{{< skew nextMinorVersion >}}) pour la prochaine version **{{< skew nextMinorVersion >}}** de Kubernetes ! ## Ressources utiles </ins>

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 blank for the main page content. Proposed Solution: Delete (fall back to English) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language fr
/triage accepted
It have to be deleted and what do you mean by fall back to english? Could you please elaborate?
I guess falling back means the menu link of the French website should lead to (i.e. its English version) instead of since there is no content in the French version. However, I don't understand where this URL () originates from. The partial seems to be incorrect as it always links to the page (despite the website's language currently in use), doesn't it? E.g., there is the content for the locale, but the navigation menu on still leads to the page, not .
/assign
There are 2 issues here: I took a look and indeed, introduced the issue since it a new page under the subfolder. Moreover, is correct, you can get to these translation by going on the page and clicking the language dropdown, and selecting Français but the always redirect to the English version.
/area localization
Both issues were resolved and merged!
Change:
All Kubernetes clusters have two categories of users: service accounts managed by Kubernetes, and normal users. <del> Normal users are assumed to be managed by an outside, independent service. An admin distributing private keys, a user store like Keystone or Google Accounts, even a file with a list of usernames and passwords. In this regard, _Kubernetes does not have objects which represent normal user accounts._ Normal users cannot be added to a cluster through an API call. </del> <ins> It is assumed that a cluster-independent service manages normal users in the following ways: - an administrator distributing private keys - a user store like Keystone or Google Accounts - a file with a list of usernames and passwords In this regard, _Kubernetes does not have objects which represent normal user accounts._ Normal users cannot be added to a cluster through an API call. </ins> Even though normal user cannot be added via an API call, but any user that presents a valid certificate signed by the cluster’s certificate authority (CA) is considered authenticated. In this configuration, Kubernetes determines the username from the common name field in the ‘subject’ of the cert (e.g., “/CN=bob”). From there, the role based access control (RBAC) sub-system would determine whether the user is authorized to perform a specific operation on a resource. You can refer to [creating user certificate request](/docs/reference/access-authn-authz/certificate-signing-requests/#user-csr) for more details about this.

Discussion:
This is a Bug Report Problem: The page at currently contains the confusing sentence fragment: "An admin distributing private keys, a user store like Keystone or Google Accounts, even a file with a list of usernames and passwords." Proposed Solution: Probably, connect the preceding sentence and this fragment. (It looks like the fragment is examples of what the preceding sentence refers to.) Page to Update:
/language en /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 : /language en /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
Change:
<td colspan="2">--dynamic-config-dir string</td> </tr> <tr> <del> <td></td><td style="line-height: 130%; word-wrap: break-word;">The Kubelet will use this directory for checkpointing downloaded configurations and tracking configuration health. The Kubelet will create this directory if it does not already exist. The path may be absolute or relative; relative paths start at the Kubelet's current working directory. Providing this flag enables dynamic Kubelet configuration. The <code>DynamicKubeletConfig</code> feature gate must be enabled to pass this flag. (DEPRECATED: Feature DynamicKubeletConfig is deprecated in 1.22 and will not move to GA. It is planned to be removed from Kubernetes in the version 1.23. Please use alternative ways to update kubelet configuration.)</td> </del> <ins> <td></td><td style="line-height: 130%; word-wrap: break-word;">The Kubelet will use this directory for checkpointing downloaded configurations and tracking configuration health. The Kubelet will create this directory if it does not already exist. The path may be absolute or relative; relative paths start at the Kubelet's current working directory. Providing this flag enables dynamic Kubelet configuration. The <code>DynamicKubeletConfig</code> feature gate must be enabled to pass this flag. (DEPRECATED: Feature DynamicKubeletConfig is deprecated in 1.22 and will not move to GA. It is planned to be removed from Kubernetes in the version 1.24 or later. Please use alternative ways to update kubelet configuration.)</td> </ins> </tr> <tr>

Discussion:
As per the Kubernetes documentation option is deprecated and removed in v1.23. The link for the documentation. But this parameter is still valid. I got the confiramation. Kublet code : configured the kubelet with in my test K8s v1.23 environment. validated in the # sig-cloud-provider. Document should reflect the correct details: The link for the documentation. Configure the kubelet with the option. No response <details</details<detailsopenstack </details<details</details<details</details<details</details<details</details
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. 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 node /sig cloud-provider
This pr has fixed this, waiting website docs to be published.
/kind documentation /remove-kind bug /transfer-issue website
/assign
Change:
* Distribute volume: `volumetype: none` For available volume types and administration options, refer to the <del> [Administration Guide](https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/part-Overview.html). </del> <ins> [Administration Guide](https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/). </ins> For further reference information, see [How to configure Heketi](https://github.com/heketi/heketi/wiki/Setting-up-the-topology).

Discussion:
Problem: The text on is working properly and redirects to the issue is to remove the URL has unnecessary context from the link as follows is For the problem, check the page . Proposed Solution: It should resolve this issue by removing the link context link and editing the text according to enhance the document line. Page to Update: Remove the text from URL and add suitable content. /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on is working properly and redirects to the issue is to remove the URL has unnecessary context /html/AdministrationGuide/part- from the link as follows is It should resolve this issue by removing the link context link and editing the text according to enhance the document line. Remove the text /html/AdministrationGuide/part- from URL [Upgrade path to GA on and add suitable content.]( /assign /language en 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
/retitle Wrong link context on Storage Classes page
/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 : /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:
* Distribute volume: `volumetype: none` For available volume types and administration options, refer to the <del> [Administration Guide](https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/part-Overview.html). </del> <ins> [Administration Guide](https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/). </ins> For further reference information, see [How to configure Heketi](https://github.com/heketi/heketi/wiki/Setting-up-the-topology).

Discussion:
stay In the page, the link at the text "vSphereVolume CSI " should be -csi-migration
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
Are you still working on it?
I submitted PR to solve this issue and put you as the co-author.
Change:
{{ partial "navbar-lang-selector.html" . }} </li> {{ end }} <ins> <li class="search-item nav-item mr-n4 mr-lg-0"> {{ partial "search-input.html" . }} </li> </ins> </ul> </div> <button id="hamburger" onclick="kub.toggleMenu()" data-auto-burger-exclude><div></div></button>

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 Currently Docs search hides when you scroll down the page, but it should not get hidden it must stay there at the top. Why is this needed Search Input should always stay at its place.Also, as a suggestion it can also be called on keyboard shortcut like like this to easily navigation in the docs. Comments !
/sig docs
/area web-development How about putting the search in the top nav? See for a related suggestion.
But, I'm not sure it's a good plan. The top nav already has a bunch of sections, and adding the search might make it look too crowded.
See how does it - I think that's a nice approach. We could drop one of the sections that's in the top nav now, or maybe combine two of them into a menu.
/triage accepted Making this improvement is helpful. /priority backlog though
/assign
Have a review on this PR -
Does it? On my browser, that doesn't happen. ! You can see that this page is scrolled but the search in the left-hand nav is still available for someone to look at it. /priority awaiting-more-evidence /remove-triage accepted
Even though I don't think the issue description is quite right, I still see the value of putting a search in the top nav. That is a place where people would look for it.
I think it more depend on screen size, in my case when i have scroll down the page, then i am not able to see that search button on the left side !
Change:
The kubelet sends this information to the container runtime (using CRI), and the runtime writes the container logs to the given location. <del> You can configure two kubelet [configuration settings](/docs/reference/config-api/kubelet-config.v1beta1/#kubelet-config-k8s-io-v1beta1-KubeletConfiguration), </del> <ins> You can configure two kubelet [configuration settings](/docs/reference/config-api/kubelet-config.v1beta1/), </ins> `containerLogMaxSize` and `containerLogMaxFiles`, using the [kubelet configuration file](/docs/tasks/administer-cluster/kubelet-config-file/). These settings let you configure the maximum size for each log file and the maximum number of files allowed for each container respectively.

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: Url selector #kubelet-config-k8s-io-v1beta1-KubeletConfiguration doesn't make a difference between: and Proposed Solution: Removing the selector from the URLs Page to Update: <!--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
/language en
/assign
/retitle Problems with (generated) reference for kubelet configuration
Change:
Mount propagation allows for sharing volumes mounted by a Container to other Containers in the same Pod, or even to other Pods on the same node. <del> If the MountPropagation feature is disabled, volume mounts in pods are not propagated. </del> <ins> If the "`MountPropagation`" feature is disabled, volume mounts in pods are not propagated. </ins> That is, Containers run with `private` mount propagation as described in the [Linux kernel documentation](https://www.kernel.org/doc/Documentation/filesystems/sharedsubtree.txt). To enable this feature, specify `MountPropagation=true` in the <del> `--feature-gates` command line option. When enabled, the `volumeMounts` field of a Container has a new `mountPropagation` subfield. Its values are: </del> <ins> `--feature-gates` command line option for the API server and kubelets. When enabled, the `volumeMounts` field of a Container has a new `mountPropagation` subfield. Its values are: </ins> * `HostToContainer` - This volume mount will receive all subsequent mounts that are mounted to this volume or any of its subdirectories. This is

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: The documentation states that the MountPropagation=true feature-gate needs to be enabled, but it is unclear where it needs to be set. Kubelet? kube-apiserver? anywhere else? Proposed Solution: Need to document where the flag is useful. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This looks related to . Would you mind taking a look, please?
FYI, I just got it to work. The flag was needed to be applied to the kube-apiserver and kubelet. I did not set the flag on any other services.
IMO, all features should be enabled on all components, otherwise you risk errors. Here it may be enough to enable it on API server and kubelet, but you can't be 100% sure with other features.
I agree, but the bug report was "how do I get the mount propagation feature to work, as the documentation for it was unclear". Having the documentation be updated to be more accurate/specific I think is a good thing.
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
Change:
<ins> apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: test-network-policy namespace: default spec: podSelector: matchLabels: role: db policyTypes: - Ingress - Egress ingress: - from: - ipBlock: cidr: 172.17.0.0/16 except: - 172.17.1.0/24 - namespaceSelector: matchLabels: project: myproject - podSelector: matchLabels: role: frontend ports: - protocol: TCP port: 6379 egress: - to: - ipBlock: cidr: 10.0.0.0/24 ports: - protocol: TCP port: 5978 </ins>

Discussion:
While working through the Killer Shell scenario for NetworkPolicies to prep for my CKA, I used the example but it failed validation. When I looked at their solution it had one tiny difference, they had a - in front of "ports:" and you guys didn't. Based on the reference docs it appears ports does expect an array which would mean that you are missing the hyphen. docs: solution 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
The indentation of list items may be the source of confusion. Once you indent all list items under a given key, the parent element of the 'ports' attribute becomes more evident. The example on the website is correct. I'm not sure about the solution from If you put as the first key of a list item object, if will carry the bar for that list item, if is not the the first key, you will indent it rather than adding another before it. Anyway, I'm fixing the example in hope things become clearer for readers.
Change:
<ins> --- title: API 发起的驱逐 id: api-eviction date: 2021-04-27 full_link: /zh/docs/concepts/scheduling-eviction/pod-eviction/#api-eviction short_description: > API 发起的驱逐是一个先调用 Eviction API 创建驱逐对象，再由该对象体面地中止 Pod 的过程。 aka: tags: - operation --- <!-- --- title: API-initiated eviction id: api-eviction date: 2021-04-27 full_link: /docs/concepts/scheduling-eviction/pod-eviction/#api-eviction short_description: > API-initiated eviction is the process by which you use the Eviction API to create an Eviction object that triggers graceful pod termination. aka: tags: - operation --- --> <!-- API-initiated eviction is the process by which you use the [Eviction API](/docs/reference/generated/kubernetes-api/{{<param "version">}}/#create-eviction-pod-v1-core) to create an `Eviction` object that triggers graceful pod termination. --> API 发起的驱逐是一个先调用 [Eviction API](/docs/reference/generated/kubernetes-api/{{<param "version">}}/create-eviction-pod-v1-core) 创建驱逐对象，再由该对象体面地中止 Pod 的过程。 <!--more--> <!-- You can request eviction either by directly calling the Eviction API using a client of the kube-apiserver, like the `kubectl drain` command. When an `Eviction` object is created, the API server terminates the Pod. API-initiated eviction is not the same as [node-pressure eviction](/docs/concepts/scheduling-eviction/eviction/#kubelet-eviction). --> 你可以通过 kube-apiserver 的客户端，比如 `kubectl drain` 这样的命令，直接调用 Eviction API 发起驱逐。 当 `Eviction` 对象创建出来之后，该对象将驱动 API 服务器终止选定的Pod。 API 发起的驱逐不同于 [节点压力引发的驱逐](/zh/docs/concepts/scheduling-eviction/eviction/#kubelet-eviction)。 </ins>

Discussion:
This is a Feature Request translate /docs/concepts/scheduling-eviction/api- into Chinese What would you like to be /zh/docs/concepts/scheduling-eviction/api- /language zh /assign
/triage accepted
Change:
- `api/legacy`, representing only legacy APIs. Legacy APIs are any APIs that have been explicitly [deprecated](/docs/reference/using-api/deprecation-policy/). <del> For example, to turning off all API versions except v1, pass `--runtime-config=api/all=false,api/v1=true` </del> <ins> For example, to turn off all API versions except v1, pass `--runtime-config=api/all=false,api/v1=true` </ins> to the `kube-apiserver`. ## {{% heading "whatsnext" %}}

Discussion:
At: Very minor typo: "For example, to turning off all API versions except v1, pass --runtime-config=api/all=false,api/v1=true to the kube-apiserver." Sould be (emphasis ): For example, to turn off all API versions except v1, pass --runtime-config=api/all=false,api/v1=true to the kube-apiserver.
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:
* [Using kubeadm to Create a Cluster](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/) --> * [使用 kubeadm 创建集群](/zh-cn/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/)

Discussion:
(kubeadm) []
/triage accepted /kind bug /assign /language zh
Change:
<del> ### Exposed Persistent volumes {#Exposed Persistent volumes} </del> <ins> ### Exposed Persistent volumes {#Exposed-Persistent-volumes} </ins> - **persistentVolumeClaim** (PersistentVolumeClaimVolumeSource)

Discussion:
This is a Bug Report The issue is outlined in:
/triage accepted
/kind cleanup
Hi Thanks for opening a PR to fix this issue! /assign