jiebi/CodeConvo huggingface dataset:
Change:
cid: docsHome layout: docsportal_home class: gridPage gridPageHome <del> linkTitle: "होम" </del> <ins> linkTitle: "प्रलेखन" </ins> main_menu: true weight: 10 hide_feedback: true

Discussion:
This is a Bug Report While the left hand side navigation menu in Hindi and English is not fully matching and can create some issues for a native hindi reader . <!-- 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: The option in English has been changed to in Hindi which can be an issue while navigating for a native Hindi reader. Proposed Solution: I have 2 options, I can change it to or . Suggestions required Page to Update: Screenshot(can be easily compared up) Hindi ! English <img width="960" alt="image" src=""<!--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 hi
/retitle [hi] Navigation menu displays 'Home' instead of 'Documentation'
It appears that there is already an existing (umbrella) issue , addressing this request for all the different langauges. Additionally, there is already a PR raised specifically for the fix in Hindi language.
Marking this as a duplicate. /triage duplicate
if possible assign it to me i can work on it
You don't need an assignment to work on issues, Anybody is welcome to propose a fix Being said that, If someone will/has already proposed a PR, It's polite to co-author with them (but not mandatory)
This issue although addresses same type of issue as in , but in different place. is addressing specifically for footer across all localizations. And in this issue it is for Navigation menu and that too for specifically Hindi localized page. So, i think its better not to consider it a duplicate. For those, who want to work on it. Changing this key-value pair with value can probably fix it. !
Can I plz solve this issue?

I want try do some localization cjhange to deepen my udnerstanding and help languages team where i can :)
/remove-triage duplicate Based on info provided in
Anyone is free to propose a fix by submitting a pull request; you don't require anybody's permission as we operate in the spirit of open source collaboration. Just a friendly reminder, these changes pertain to Hindi localization, so having familiarity with the Hindi language would be advantageous, although it's not mandatory.
Okay got it. Thanks! I will assign to myself in that case. /assign
I have riased plz review and let me know if its okay. Thanks in advance.
Change:
{{% capture overview %}} <ins> {{< feature-state for_k8s_version="v1.5" state="beta" >}} </ins> This page shows how to limit the number of concurrent disruptions that your application experiences, allowing for higher availability while permitting the cluster administrator to manage the clusters

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: does not mention that PodDisruptionBudget is beta. Proposed Solution: Add a shortcode to Page to Update: There may well be other pages that describe PodDisruptionBudget without mentioning its feature state. <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.18 <!--Additional Information:--/help /kind bug /priority backlog
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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: does not mention that PodDisruptionBudget is beta. Add a shortcode to There may well be other pages that describe PodDisruptionBudget without mentioning its feature state. Kubernetes Version: v1.18 /help /kind bug /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
I don't see on this page -
Looks like it is since .
/assign
Change:
for more information. --> <del> ### 容器运行时类 {#runtimeclass} {{< feature-state for_k8s_version="v1.16" state="alpha" >}} </del> <ins> ### 容器运行时类 {#runtimeclass} {{< feature-state for_k8s_version="v1.16" state="alpha" >}} </ins> [容器运行时类](/docs/concepts/containers/runtime-class/)定义描述了与运行 Pod 相关的开销。此准入控制器将相应地设置 pod.Spec.Overhead 字段。

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:
### はじめに Bashにおけるkubectlの補完スクリプトは`kubectl completion bash`コマンドで生成できます。 <del> シェル内で補完スクリプトをsourceすることでkubectlの自動補完が有効になります。 </del> <ins> 補完スクリプトをシェル内に読み込ませることでkubectlの自動補完が有効になります。 </ins> ただし、補完スクリプトは[**bash-completion**](https://github.com/scop/bash-completion)に依存しているため、事前にインストールしておく必要があります。

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. --Update Why is this needed Reflect the following feedback on this file, too. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/area localization /triage accepted
Change:
The response should be similar to this: ``` <del> NAME       TYPE        CLUSTER-IP      EXTERNAL-IP        PORT(S)        AGE frontend   ClusterIP   10.51.242.136   109.197.92.229     80:32372/TCP   1m </del> <ins> NAME       TYPE           CLUSTER-IP      EXTERNAL-IP        PORT(S)        AGE frontend   LoadBalancer   10.51.242.136   109.197.92.229     80:32372/TCP   1m </ins> ``` 1. Copy the external IP address, and load the page in your browser to view your guestbook.

Discussion:
4 ordered lists have wrong indexes. For example, the number below should be 3. ! Page to update: /language en /kind cleanup
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:
I instrumented the [example webhook](https://github.com/kubernetes-sigs/controller-runtime/tree/master/examples/builtins) with OpenTelemetry (I had to [patch](https://github.com/dashpole/controller-runtime/commit/85fdda7ba03dd2c22ef62c1a3dbdf5aa651f90da) controller-runtime, but it makes a neat demo), and routed traces to Jaeger as well.  I collected traces like this one: <del> <img width="1440" alt="Jaeger screenshot showing API server, admission webhook, and etcd trace" src="https://user-images.githubusercontent.com/3262098/128613167-e7a14cdf-5635-422f-9fd8-f32744ce639d.png"> </del> <ins> ![Jaeger screenshot showing API server, admission webhook, and etcd trace](/images/blog/2021-09-03-api-server-tracing/example-trace-2.png "Jaeger screenshot showing API server, admission webhook, and etcd trace") </ins> Compared with the previous trace, there are two new spans: A teal span from the API Server making a request to the admission webhook, and a brown span from the admission webhook serving the request.  Even if you didn't instrument your webhook, you would still get the span from the API Server making the request to the webhook.

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: adds a blog article but the images are not hosted within ; they should be. Proposed Solution: Create a PR that adds those images (see other articles that use images for examples) into this repo, and change the article's Markdown source to use them. It might be easiest to make a directory for the article, again following how other articles do it. Page to Update: (after the 3rd of September 2021). It's OK to fix it now. Additional Information: /language en /area blog /kind cleanup /priority important-soon
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
/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
Hi, I would like to take this up /assign
Change:
kubectl get nodes -o jsonpath='{.items[*].status.addresses[?(@.type=="ExternalIP")].address}' # List Names of Pods that belong to Particular RC <del> # "jq" command useful for transformations that are too complex for jsonpath, it can be found at https://stedolan.github.io/jq/ </del> <ins> # "jq" command useful for transformations that are too complex for jsonpath, it can be found at https://jqlang.github.io/jq/ </ins> sel=${$(kubectl get rc my-rc --output=json | jq -j '.spec.selector | to_entries | .[] | "(.key)=(.value),"')%?} echo $(kubectl get pods --selector=$sel --output=jsonpath={.items..metadata.name})

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: The download page for is now (previously ) Proposed Solution: Throughout the English pages, replace the old download URL with the new one. <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /priority backlog /triage accepted /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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: The download page for is now (previously ) Throughout the English pages, replace the old download URL with the new one. <!--Kubernetes Version:--/language en /priority backlog /triage accepted /help </details
I want to help with this. /assign
Hello I would like to work on this issue are you working on the issue?
I have riasd PR to help with this issue.
Change:
### Differences from regular containers Init containers support all the fields and features of app containers, <del> including resource limits, volumes, and security settings. However, the </del> <ins> including resource limits, [volumes](/docs/concepts/storage/volumes/), and security settings. However, the </ins> resource requests and limits for an init container are handled differently, as documented in [Resources](#resources).

Discussion:
This is a Bug Report Problem: section of page does not cover all required reference points which are mentioned throughout page. Proposed Solution: Add references of below topics under what's next section of page. learn about service, volume. kubelet, kubectl overview. Garbage Collection that Kubernetes uses to clean up cluster resources. Types of probes. Liveness, Readiness and Startup Probes. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/sig docs /language en /assign
/remove-kind bug /triage accepted I'm not sure how much we need to tell people about Services and Volumes; maybe we should instead signpost readers to learn more about Pods in general - perhaps links to specific fragments of relevant Pod pages? Same for garbage collection really.
Thanks for reply. In that case i will add one link in general to know more about pods and service under What's next section. For garbage collection its already available under what's next section. So i will not add reference link inside page.
Oops! it was my mistake, there is no reference link provided for under what's next section. will add this too.
Hi , Below, i prepared the preview changes what i am planning to do as per my understanding based your comment above. I would like to confirm is these changes you were expecting to do for this issue. ! Please suggest.
Hi Could you please confirm on above comment.
Hi Could you please take a look on Hi Please confirm if these changes sounds good to you. So that i can go ahead and work on it, Thanks.
When adding links, please use links that have words like “volumes”; readers don't need to see the URL. If you send in a pull request we can offer feedback on it directly. Ideally we can accept it as is!
Thanks for your response, i will soon open a PR for it.
Fixed it here .
Change:
![Services overview diagram for iptables proxy](/images/docs/services-iptables-overview.svg) <ins> ### Proxy-mode: ipvs[alpha] **Warning:** This is an alpha feature and not recommended for production clusters yet. In this mode, kube-proxy watches Kubernetes `services` and `endpoints`, call `netlink` interface create ipvs rules accordingly and sync ipvs rules with Kubernetes `services` and `endpoints`  periodically, to make sure ipvs status is consistent with the expectation. When access the `service`, traffic will be redirect to one of the backend `pod`. Similar to iptables, Ipvs is based on netfilter hook function, but use hash table as the underlying data structure and work in the kernal state. That means ipvs redirects traffic can be much faster, and have much better performance when sync proxy rules. Furthermore, ipvs provides more options for load balancing algorithm, such as: - rr: round-robin - lc: least connection - dh: destination hashing - sh: source hashing - sed: shortest expected delay - nq: never queue **Note:** ipvs mode assumed IPVS kernel modules are installed on the node before running kube-proxy. When kube-proxy starts, if proxy mode is ipvs, kube-proxy would validate if IPVS modules are installed on the node, if it's not installed kube-proxy will fall back to iptables proxy mode. ![Services overview diagram for ipvs proxy](/images/docs/services-ipvs-overview.svg) </ins> ## Multi-Port Services Many `Services` need to expose more than one port.  For this case, Kubernetes

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:
following matches only Pods in the `kube-system` namespace. ```shell <del> kubectl get pods --namespace kube-system -o jsonpath="{..image}" </del> <ins> kubectl get pods --namespace kube-system -o jsonpath="{.items[*].spec.containers[*].image}" </ins> ``` ## List Container images using a go-template instead of jsonpath

Discussion:
Hi, I've tested this example : It returns image names double, because "{..image}" recursively search in the output of JSON, So at the first, it will find the "image" word in "" and at the second time, it will find the "image" word in "". It means you will see the image name two times for each pod at least. Please change your example. Best Regards, Alireza Bahmani.
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
Hi What's the URL of the page where you've seen a problem?
here are the links to the: kubernetes docs website page ~ markdown file(s) where it require changes ~
The issue is, the following command produces 2 times (the count of image in a single pod). As mentioned, it is because the command count both the occurrence from the & sections from a single pod json manifest. Ideally it should be:
Following could be one of the fix for it:
/assign
There are other references . These would return duplicate images as well, right? I've updated those as well for now.
Hi yes, I feel those also need to be fixed. Let's wait for to provide their review. :)
Change:
```shell # Add Docker's official GPG key: <del> curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add --keyring /etc/apt/trusted.gpg.d/docker.gpg - </del> <ins> curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key --keyring /etc/apt/trusted.gpg.d/docker.gpg add - </ins> ``` ```shell

Discussion:
[UBUNTU 20.04] specifies the following command: This runs into the following error: Update the command to: Or... use the command which is also mentioned on the
Thanks for reporting this. I wonder if we should also recommend that readers ? /kind bug /triage accepted /priority important-longterm /language en /sig node
That is a possibility. But I think it would be logical to take over the official documentation of docker.
Did PR help here? /triage needs-information /remove-triage accepted
/retitle Incorrect commands for adding PGP keys to APT configuration
/triage accepted /remove-triage needs-information
Change:
| `BalanceAttachedNodeVolumes` | `false` | Alpha | 1.11 | | | `BoundServiceAccountTokenVolume` | `false` | Alpha | 1.13 | 1.20 | | `BoundServiceAccountTokenVolume` | `true` | Beta | 1.21 | | <ins> | `ControllerManagerLeaderMigration` | `false` | Alpha | 1.21 | | </ins> | `CPUManager` | `false` | Alpha | 1.8 | 1.9 | | `CPUManager` | `true` | Beta | 1.10 | | | `CSIInlineVolume` | `false` | Alpha | 1.15 | 1.15 |

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: doesn't list ControllerManagerLeaderMigration although there is a page that mentions it. Proposed Solution: Update / write the documentation for the feature, including a mention of in Page to Update: Additional Information: /sig cloud-provider
I think there's a plan to graduate this to beta; if so, we should definitely look at getting it properly documented.
yup, agreed. I think we can address it once they open a doc for their enhancement /cc /triage accepted
/assign
Change:
- Learn how to [manage Secret using config file](/docs/tasks/configmap-secret/managing-secret-using-config-file/) - Learn how to [manage Secret using kustomize](/docs/tasks/configmap-secret/managing-secret-using-kustomize/) --> <del> - 阅读更多有关 [Secret 概念](/docs/concepts/configuration/secret/) - 了解如何 [使用配置文件管理 Secret](/docs/tasks/configmap-secret/managing-secret-using-config-file/) - 了解如何 [使用 kustomize 管理 Secret](/docs/tasks/configmap-secret/managing-secret-using-kustomize/) </del> <ins> - 阅读更多有关 [Secret 概念](/zh/docs/concepts/configuration/secret/) - 了解如何 [使用配置文件管理 Secret](/zh/docs/tasks/configmap-secret/managing-secret-using-config-file/) - 了解如何 [使用 kustomize 管理 Secret](/zh/docs/tasks/configmap-secret/managing-secret-using-kustomize/) </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 missing in Chinese version. See for more info. Proposed Solution: Add /docs/tasks/configmap-secret/ to zh version with three articles to be translated. [x] /zh/docs/tasks/configmap-secret/managing-secret-using-config-[x] /zh/docs/tasks/configmap-secret/managing-secret-using-[x] /zh/docs/tasks/configmap-secret/managing-secret-using- Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--
/language zh /assign
Change:
replicationcontroller "my-nginx-v4" rolling updated ``` <del> You can also run the [update demo](/docs/tasks/run-application/rolling-update-replication-controller/) to see a visual representation of the rolling update process. </del> ## Troubleshooting If the `timeout` duration is reached during a rolling update, the operation will

Discussion:
This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: [update demo] link doesn't do anything. It links to the same page. Proposed Solution: ? Page to Update:
Change:
title: Container Environment Variables id: container-env-variables date: 2018-04-12 <del> full_link: /docs/concepts/containers/container-environment-variables.md </del> <ins> full_link: /zh/docs/concepts/containers/container-environment/ </ins> short_description: > Container environment variables are name=value pairs that provide useful information into containers running in a Pod.

Discussion:
could you please be more specific? I cannot find the broken link...
if you enter [], you can see next describtion: Pod PodPreset Secret Pod . and you click ‘’ the link is broken
thank you, I'm fixing it now ~
/assign
/language zh