jiebi/CodeConvo huggingface dataset:
Change:
1. Laden Sie die neueste Version mit dem Befehl herunter: ``` <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/$(curl -LS https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl </ins> ``` <del> Um eine bestimmte Version herunterzuladen, ersetzen Sie den Befehlsteil `$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)` mit der jeweiligen Version. </del> <ins> Um eine bestimmte Version herunterzuladen, ersetzen Sie den Befehlsteil `$(curl -LS https://dl.k8s.io/release/stable.txt)` mit der jeweiligen Version. </ins> Um beispielsweise die Version {{< param "fullversion" >}} auf Linux herunterzuladen, verwenden Sie den folgenden Befehl: ``` <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/{{< param "fullversion" >}}/bin/linux/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/linux/amd64/kubectl </ins> ``` 2. Machen Sie die kubectl-Binärdatei ausführbar.

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: There are still references to instead of is the correct advertised download host and will eventually move to be fastly shielding a fully community-owned bucket ref: Proposed Solution: Replace with Also replace any references with using if applicable. Page to Update: Assorted e.g. , <!--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
/assign
hi Not a problem, didn't see anyone assigned to this issue. I am unassigning myself and assigning it to you. /unassign
/assign
Hi, I found a small issue with your proposed changes regarding one of the URLs, which is mentioned twice in the file. While returns as expected, I am getting an nginx-rendered HTML page saying for the new command () instead. As I understand, it happens due to the redirect configured on the new web server. Thus, works fine for me (it returns as expected).
i see Let me update it, thanks your work
Just done, please review all of PRs
Thanks!
And yes: These will need to follow redirects, in the future the tentative plan is it will redirect to a CDN in front of a different bucket created in a fully project / SIG-K8s-Infra controlled GCP or AWS account. I would recommend for downloading with curl more generally, even in docs / usage for other hosts.
Change:
Traffic from the external load balancer is directed at the backend Pods. The cloud provider decides how it is load balanced. <del> Some cloud providers allow you to specify the `loadBalancerIP`. In those cases, the load-balancer is created with the user-specified `loadBalancerIP`. If the `loadBalancerIP` field is not specified, the loadBalancer is set up with an ephemeral IP address. If you specify a `loadBalancerIP` but your cloud provider does not support the feature, the `loadbalancerIP` field that you set is ignored. </del> To implement a Service of `type: LoadBalancer`, Kubernetes typically starts off by making the changes that are equivalent to you requesting a Service of `type: NodePort`. The cloud-controller-manager component then configures the external load balancer to

Discussion:
This is a Bug Report Problem: As per , the has been deprecated since 1.24 but the docs does not mention about the deprecation - Proposed Solution: should mention the deprecation at least. Page to Update:
/triage accepted
Hi , the triage has been accepted and if you want to contribute the change you can assign it to yourself . If not, please let us know here, I'll be happy to add this
Thank you. Please go ahead
Great . Thanks /assign
/sig apps /sig network /sig docs
Continuing the discussion for change: One way we can apply this change is by adding a note: But should we give an example of the annotations ?
Hi , Raised a PR for the Note:
Change:
* kms plugin version: `v1beta1` <del> In response to procedure call Version, a compatible KMS plugin should return v1beta1 as VersionResponse.version </del> <ins> In response to procedure call Version, a compatible KMS plugin should return v1beta1 as VersionResponse.version. </ins> * message version: `v1beta1` <del> All messages from KMS provider have the version field set to current version v1beta1 </del> <ins> All messages from KMS provider have the version field set to current version v1beta1. </ins> * protocol: UNIX domain socket (`unix`) <del> The gRPC server should listen at UNIX domain socket </del> <ins> The gRPC server should listen at UNIX domain socket. </ins> ### Integrating a KMS plugin with the remote KMS The KMS plugin can communicate with the remote KMS using any protocol supported by the KMS. All configuration data, including authentication credentials the KMS plugin uses to communicate with the remote KMS, are stored and managed by the KMS plugin independently. The KMS plugin can encode the ciphertext with additional metadata that may be required before sending it to the KMS for decryption.

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: There are indentation errors in the yaml files of EncryptionConfiguration. For example in the following yaml, lines after "- secrets" should indent two to the right. ! Proposed Solution: Correct the indentation errors. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Is it right to have in the fixed page?
I checked the preview page, and it's still wrong. I've close my PR.
It should looks like this or "secrets" is the subcontent of the second "resources", and "providers" is with the same level of the second "resources". Although I modified the markdown, the rendered webpage is still wrong.
/priority backlog /language en /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 : /priority backlog /language en /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
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-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
/remove-lifecycle rotten /assign
Change:
``` As you can see from the results of the command, the cron job has not scheduled or run any jobs yet. <del> Watch for the job to be created in around one minute: </del> <ins> {{< glossary_tooltip text="Watch" term_id="watch" >}} for the job to be created in around one minute: </ins> ```shell kubectl get jobs --watch

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 Update the to include an explanation of “watch”. Why is this needed The watch verb (and actually watchcollection as well) is K8s-specific jargon. We should help readers understand it. Comments Extra credit for also using the new term in existing pages, using a . /kind feature /wg api-expression
/assign
/priority backlog /triage accepted
Hi PR: for this issue. PTAL
I'm happy for any reviewer (for English) to take a look there.
Change:
Being vulnerable does not necessarily mean that your service will be exploited. Though your services are vulnerable in some ways unknown to you, offenders still need to identify these vulnerabilities and then exploit them. If offenders fail to exploit your service vulnerabilities, you win! In other words, having a vulnerability that can’t be exploited, represents a risk that can’t be realized. <del> {{< figure src="Example.png" alt="Image of an example of offender gaining foothold in a service" class="diagram-large" caption="Figure 1. An Offender gaining foothold in a vulnerable service" >}} </del> <ins> {{< figure src="security_behavior_figure_1.svg" alt="Image of an example of offender gaining foothold in a service" class="diagram-large" caption="Figure 1. An Offender gaining foothold in a vulnerable service" >}} </ins> The above diagram shows an example in which the offender does not yet have a foothold in the service; that is, it is assumed that your service does not run code controlled by the offender on day 1. In our example the service has vulnerabilities in the API exposed to clients. To gain an initial foothold the offender uses a malicious client to try and exploit one of the service API vulnerabilities. The malicious client sends an exploit that triggers some unplanned behavior of the service.

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 image files in need to be converted to an SVG. Currently, they are PNG. The originals are PPT files that can be found at Earlier attempts to convert them to SVG resulted in poor-quality images. Proposed Solution: If anyone has the tools and expertise to convert the PNG/PPT to high-quality SVG that will look the same as the PNGs, we welcome the help. Page to Update: <!--Optional Information (remove the comment tags around the information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign If anyone gets to this first: great!
hey! looking to contribute to this project !..can I?
/triage accepted
I've made progress on this and hope to send in a PR later this week.
Change:
{{< note >}} Kubeadm uses the same `KubeletConfiguration` for all nodes in the cluster. <del> The `KubeletConfiguration` is stored in a [ConfigMap](docs/concepts/configuration/configmap) </del> <ins> The `KubeletConfiguration` is stored in a [ConfigMap](/docs/concepts/configuration/configmap) </ins> object under the `kube-system` namespace. Executing the sub commands `init`, `join` and `upgrade` would result in kubeadm

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: In there is a table broken with GitHub Markdown renderer. ! BTW, the table is not broken with Hugo Markdown renderer. ! Proposed Solution: Page to Update: No Page on to Update. Just a Markdown file on GitHub to update. <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/assign
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
We support viewing the rendered documentation via I don't think this issue is valid.
/priority awaiting-more-evidence /langauge en
Thank for your comment. I will describe a bit more about this issue I opened. [As-is] Yes, although the second row of the Markdown code has 4 columns and other rows have 3 columns, this table is rendered alright by Hugo Markdown renderer. This is a issue about improving consistency of the number of columns in the Markdown code, regardless of the type of Markdown renderer. [To-be]

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 link is broken. Proposed Solution: In Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/assign
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
already logged here: /close /sig cluster-lifecycle
Closing this issue. <detailsIn response to : already logged here: /sig cluster-lifecycle 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> <td> ShutdownGracePeriod specifies the total duration that the node should delay the shutdown and total grace period for pod termination during a node shutdown. <del> Default: "30s"</td> </del> <ins> Default: "0s"</td> </ins> </tr>

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: Visiting provides inaccurate default values for shutdownGracePeriod (30s rather than 0s) and shutdownGracePeriodCriticalPods (10s rather than 0s). Proposed Solution: Correct the documentation to match the actual default values. 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
I would like to take up this ticket.
Change:
--- <del> title: Hello Minikube </del> <ins> title: Bienvenue sur Minikube </ins> content_type: tutorial weight: 5 <del> description: Tutoriel Minikube menu: main: title: "Démarrer" weight: 10 post: > <p>Prêt à mettre les mains dans le cambouis ? Créez un cluster Kubernetes simple qui exécute "Hello World" avec Node.js.</p>>. </del> card: name: tutorials weight: 10

Discussion:
Bonjour, Petit problème de CORS sur cette page: Je suis bien sur un ordinateur et j'ai ceci: !
/retitle [fr] Inactive and deprecated interactive tutorial in "Learn Kubernetes Basics" page /language fr
Katacoda environment for the Kubernetes tutorial has been shut down. Refer the announcement . We have an umbrella issue raised to remove tutorials that rely on Katacoda for all localized documents.
/area localization /kind bug
Does it mean I can suggest a merge request for French?
/triage accepted Ce projet est open source : tout le monde peut y contribuer! / This is an open source project, anyone is welcome to contribute!
Change:
1. इस कमांड से नवीनतम रिलीज डाउनलोड करें: ```powershell <del> curl -LO https://dl.k8s.io/release/{{% param "fullversion" %}}/bin/windows/amd64/kubectl-convert.exe </del> <ins> curl -LO https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/windows/amd64/kubectl-convert.exe </ins> ``` 1. बाइनरी को मान्य करें (वैकल्पिक)

Discussion:
Parent issue: Substitute the outdated shortcode with the new shortcode in the Hindi language documentation. /assign /triage accepted /language hi
PR has been raised to address this issue.
Change:
## Requisitos de plugins de Rede <del> Além de prover a [interface `NetworkPlugin`](https://github.com/kubernetes/kubernetes/tree/{{< param "fullversion" >}}/pkg/kubelet/dockershim/network/plugins.go) </del> <ins> Além de prover a [interface `NetworkPlugin`](https://github.com/kubernetes/kubernetes/tree/v{{< skew currentPatchVersion >}}/pkg/kubelet/dockershim/network/plugins.go) </ins> para configuração da rede do pod, o plugin pode necessitar de suporte específico ao kube-proxy. O proxy iptables obviamente depende do iptables, e o plugin deve garantir que o

Discussion:
Parent issue: Replace the deprecated shortcode with the shortcode in the Brazilian Portuguese localized docs. /assign /triage accepted /language pt
Change:
All of the following are responsibilities of whoever sets up and manages the cluster: 1. Creating the CA key and certificate <del> 2. Distributing the CA certificate to the master nodes, where kube-apiserver is running </del> <ins> 2. Distributing the CA certificate to the control plane nodes, where kube-apiserver is running </ins> 3. Creating a key and certificate for each kubelet; strongly recommended to have a unique one, with a unique CN, for each kubelet 4. Signing the kubelet certificate using the CA key 5. Distributing the kubelet key and signed certificate to the specific node on which the kubelet is running

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: uses the outdated term “master” and “master node”. Proposed Solution: Replace references to the control plane that use the term “master” with the current term: “control plane”. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /kind cleanup /wg naming
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 “Kubelet TLS Bootstrapping” uses outdated wording
I would like to take up this issue
/assign
Change:
{% endcapture %} {% capture whatsnext %} <del> * Learn more about [ConfigMaps](/docs/tasks/configure-pod-container/configmap.html). </del> <ins> * Learn more about [ConfigMaps](/docs/tasks/configure-pod-container/configmap/). * Follow a real world example of [Configuring Redis using a ConfigMap](/docs/tutorials/configuration/configure-redis-using-configmap/). </ins> {% endcapture %}

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... [x ] Feature Request Problem: As discussed in , the 'Real World Example' section of should probably be a separate tutorial. Proposed Solution: Create a new tutorial from the existing content (probably needs additional information). Remove the section from the task doc and replace with a 'What's Next' pointer to new tutorial doc. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
done
Change:
プライベートレジストリを設定するためのソリューションはいくつかあります。ここでは、いくつかの一般的なユースケースと推奨される解決方法を示します。 1. クラスターに独自仕様でない(例えば、オープンソース)イメージだけを実行する。イメージを非公開にする必要がない <del> - Docker hubのパブリックイメージを利用する </del> <ins> - パブリックレジストリのパブリックイメージを利用する </ins> - 設定は必要ない - クラウドプロバイダーによっては、可用性の向上とイメージをPullする時間を短くする為に、自動的にキャッシュやミラーされたパプリックイメージが提供される 1. 社外には非公開の必要があるが、すべてのクラスター利用者には見せてよい独自仕様のイメージをクラスターで実行している <del> - ホストされたプライペートな [Dockerレジストリ](https://docs.docker.com/registry/)を使用 - [Docker Hub](https://hub.docker.com/signup)または他の場所の上でホストされている場合がある - 上記のように各Node上のdocker/config.jsonを手動で構成する </del> <ins> - ホストされたプライペートレジストリを使用 - プライベートレジストリにアクセスする必要があるノードには、手動設定が必要となる場合がある </ins> - または、オープンな読み取りアクセスを許可したファイヤーウォールの背後で内部向けプライベートレジストリを実行する - Kubernetesの設定は必要ない - イメージへのアクセスを制御できるホストされたコンテナイメージレジストリサービスを利用する

Discussion:
This is a Feature Request What would you like to be We need to update according to the English text, because it is outdated. Why is this needed is outdated. Comments /language ja /assign
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
Change:
| `EvenPodsSpread` | `true` | Beta | 1.18 | 1.18 | | `EvenPodsSpread` | `true` | GA | 1.19 | - | | `ExecProbeTimeout` | `true` | GA | 1.20 | - | <ins> | `ExternalPolicyForExternalIP` | `true` | GA | 1.18 | - | </ins> | `GCERegionalPersistentDisk` | `true` | Beta | 1.10 | 1.12 | | `GCERegionalPersistentDisk` | `true` | GA | 1.13 | - | | `HugePages` | `false` | Alpha | 1.8 | 1.9 |

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 feature gate is not listed in Proposed Solution: Add to the feature gate list Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.21 Additional Information: Prompted by /language en /kind bug /sig network
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
we'd like this feature documented, even if it has already graduated