jiebi/CodeConvo huggingface dataset:
Change:
```bash echo 'source <(kubectl completion bash)' >>~/.bash_profile ``` - Add the completion script to the `/usr/local/etc/bash_completion.d` directory:

Discussion:
There are no details or instructions on how to validate the binary downloaded from this page via some form of checksum, sha256 or otherwise. For automation purposes, eg. ansible playbook, being able to validate any binary downloads is a requirement of project stakeholders.
The site doesn't allow browsing, but the file is there as kubectl.sha256 afterall. Might be worth mentioning this in the document?
/retitle Document how to validate kubectl binary against checksum / signature /language en /kind feature /triage accepted The page in question is
To fix this: update to use download links from for example also explain to readers that checksum files are available that they can use to compare binaries obtained from elsewhere for example The and shortcodes are useful for automatically filling in the current Kubernetes version. /help /sig cli
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 : To fix this: update to use download links from explain to readers that checksum files are available that they can use to compare binaries obtained from elsewhere /sig cli 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 may be able to help with this /assign
Change:
Um eine bestimmte Version herunterzuladen, ersetzen Sie den Befehlsteil `$(curl -LS https://dl.k8s.io/release/stable.txt)` mit der jeweiligen Version. <del> Um beispielsweise die Version {{< param "fullversion" >}} auf macOS herunterzuladen, verwenden Sie den folgenden Befehl: </del> <ins> Um beispielsweise die Version {{< skew currentPatchVersion >}} auf macOS herunterzuladen, verwenden Sie den folgenden Befehl: </ins> ``` <del> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/darwin/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/darwin/amd64/kubectl </ins> ``` 2. Machen Sie die kubectl-Binärdatei ausführbar.

Discussion:
[de] Replace deprecated shortcode Problem: Based on , I have created this issue/task to help update the [de] language documentation. Proposed Solution: Page to Update: In the branch, I found: Results for "fullversion" in "k8s-website" /home/rdlugyhe/kubernetes/k8s-website/content/de/docs/tasks/tools/install-kubectl- 42: Um zum Beispiel Version {{< param "fullversion" }} auf Linux herunterzuladen: 45: curl -LO {{< param "fullversion" }}/bin/linux/amd64/kubectl /home/rdlugyhe/kubernetes/k8s-website/content/de/docs/tasks/tools/install-kubectl- 47: Um zum Beispiel Version {{< param "fullversion" }} auf Intel macOS herunterzuladen: 50: curl -LO "{{< param "fullversion" }}/bin/darwin/amd64/kubectl" 56: curl -LO "{{< param "fullversion" }}/bin/darwin/arm64/kubectl" /home/rdlugyhe/kubernetes/k8s-website/content/de/docs/tasks/tools/install- 200: Um beispielsweise die Version {{< param "fullversion" }} auf macOS herunterzuladen, verwenden Sie 203: curl -LO {{< param "fullversion" }}/bin/darwin/amd64/kubectl 228: Um beispielsweise die Version {{< param "fullversion" }} auf Linux herunterzuladen, verwenden Sie 231: curl -LO {{< param "fullversion" }}/bin/linux/amd64/kubectl 247: Laden Sie das aktuellste Release {{< param "fullversion" }} von diesem linkg
Change:
<script src="{{ "js/script.js" | relURL }}"></script> {{ with .Params.js }}{{ range (split . ",") }}<script src="{{ (trim . " ") | relURL }}"></script><!-- custom js added --> <del> {{ end }}{{ else }}<!-- no custom js detected -->{{ end }} </del>  No newline at end of file <ins> {{ end }}{{ else }}<!-- no custom js detected -->{{ end }} </ins>

Discussion:
Kubernetes website does not respond to language change
This is because .... we are not using the cached jquery script. We are downloading from which is sometimes blocked from China.
Change:
the code and any runtime it requires, application and system libraries, and default values for any essential settings. <del> By design, a container is immutable: you cannot change the code of a container that is already running. If you have a containerized application and want to make changes, you need to build a new image that includes the change, then recreate the container to start from the updated image. </del> <ins> Containers are intended to be stateless and [immutable](https://glossary.cncf.io/immutable-infrastructure/): you should not change the code of a container that is already running. If you have a containerized application and want to make changes, the correct process is to build a new image that includes the change, then recreate the container to start from the updated image. </ins> ## Container runtimes

Discussion:
Problem: I find this information confusing: Containers are designed to be staless and immutable, but it is the responsibility of the users to maintain these properties. The wording "by design" suggests that the container is immutable however it is used. It is incorrect that you cannot change the code of a container that is already running. I have seen the anti-pattern of running in the containers entrypoint. This makes the container not reproducible, because of the download of a different version of the software every time the container starts, and it proves that the container "by design" is not immutable. More on this container operations thoughts can be found here: Proposed Solution: I will propose a PR with the following: Containers are designed to be stateless and immutable: you should not change the code of a container that is already running. If you have a containerized application and want to make changes, the correct process is to build a new image that includes the change, then recreate the container to start from the updated image. Page to Update:
/remove-kind bug I agree: app containers are intended to be immutable, but the container is able to mutate itself and external actors can do that too.
/language en /triage accepted /priority backlog
Change:
answering questions and suggesting appropriate work for them to do This team at times works in close conjunction with the <del> [Product Security Committee][psc] and therefore should abide by the guidelines </del> <ins> [Security Response Committee][src] and therefore should abide by the guidelines </ins> set forth in the [Security Release Process][security-release-process]. GitHub Access Controls: [@kubernetes/release-managers](https://github.com/orgs/kubernetes/teams/release-managers)

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 change We should find the term “product security committee” anywhere within the English-language docs, and replace that term with “security response committee”. We don't need to revise any blog articles. If we feel there are some blog articles where an exception is justified, I'd revise those in a separate PR per article as the review process is different. Why is this needed renamed the product security committee to “Security Response Committee” Comments /language en /sig docs /sig security /help /triage accepted Relevant to
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 Feature Request <!-- See for guidance on writing an actionable issue description. --We should find the term “product security committee” anywhere within the English-language docs, and replace that term with “security response committee”. We don't need to revise any blog articles. If we feel there are some blog articles where an exception is justified, I'd revise those in a separate PR per article as the review process is different. renamed the product security committee to “Security Response Committee” /language en /sig docs /sig security /help /triage accepted Relevant to 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
/priority backlog
thanks , PR's are incoming org wide for the change.
Hi, I would like to take this up /assign
Change:
This section outlines the necessary steps to use containerd as CRI runtime. <del> Use the following commands to install Containerd on your system: Follow the instructions for [getting started with containerd](https://github.com/containerd/containerd/blob/main/docs/getting-started.md). Return to this step once you've created a valid configuration file, `config.toml`. </del> <ins> To install containerd on your system, follow the instructions on [getting started with containerd](https://github.com/containerd/containerd/blob/main/docs/getting-started.md).Return to this step once you've created a valid `config.toml` configuration file. </ins> {{< tabs name="Finding your config.toml file" >}} {{% tab name="Linux" %}}

Discussion:
This page is missing the commands to install containerd. At the anchor , there is the following text: "Use the following commands to install Containerd on your system:" Yet there is nothing below this instructing how to perform the install. I believe it should have something along the lines of: But the actual instructions for installing containerd appear to be missing. Below this we find the following text indicating that a restart of the newly installed containerd service should be performed, but the instructions to perform the actual install are missing. "If you apply this change, make sure to restart containerd:" `sudo systemctl restart containerd'
Page: /language en
/assign
Hi , There's already a line mentioned to go through this link () and then come back to this step.
We should remove the text "Use the following commands to install Containerd on your system:” as these are obsolete. Instead, we expect the containerd documentation to cover that detail.
We could also revise the text to make it clear that following those third-party docs is a required step towards having a working containerd.
/assign
/triage accepted
Perfect , I'll commit the changes as required !
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale
Change:
for each individual projection. ## serviceAccountToken projected volumes {#serviceaccounttoken} <del> When the `TokenRequestProjection` feature is enabled, you can inject the token for the current [service account](/docs/reference/access-authn-authz/authentication/#service-account-tokens) </del> <ins> You can inject the token for the current [service account](/docs/reference/access-authn-authz/authentication/#service-account-tokens) </ins> into a Pod at a specified path. For example: {{< codenew file="pods/storage/projected-service-account-token.yaml" >}}

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: says: However, has graduated and is always enabled. Proposed Solution: Delete the text before “you can” from that sentence. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en
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:
## Running Node Conformance Test To run the node conformance test, perform the following steps: <del> 1. Point your Kubelet to localhost `--api-servers="http://localhost:8080"`, because the test framework starts a local master to test Kubelet. There are some other Kubelet flags you may care: </del> <ins> 1. Work out the value of the `--kubeconfig` option for the kubelet; for example: `--kubeconfig=/var/lib/kubelet/config.yaml`. Because the test framework starts a local control plane to test the kubelet, use `http://localhost:8080` as the URL of the API server. There are some other kubelet command line parameters you may want to use: </ins> * `--pod-cidr`: If you are using `kubenet`, you should specify an arbitrary CIDR to Kubelet, for example `--pod-cidr=10.180.0.0/24`. * `--cloud-provider`: If you are using `--cloud-provider=gce`, you should

Discussion:
This is a Bug Report Inability to set kubelet Problem: As per Expected result Kubelet should point to the correct api-servers. Actual result kubelet cannot start because is not a valid option, since it was changed to Proposed Solution: Modify the documentation to create a kubeconfig file that points to the api servers . Page to Update: Kubernetes Version: v1.18.5
/language en /kind bug /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-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale
Change:
<ins> --- title: Windowsノードのアップグレード min-kubernetes-server-version: 1.17 content_type: task weight: 40 --- <!-- overview --> {{< feature-state for_k8s_version="v1.18" state="beta" >}} このページでは、[kubeadmで作られた](/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes)Windowsノードをアップグレードする方法について説明します。 ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} * [残りのkubeadmクラスターをアップグレードするプロセス](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade)を理解します。 Windowsノードをアップグレードする前にコントロールプレーンノードをアップグレードしたいと思うかもしれません。 <!-- steps --> ## ワーカーノードをアップグレード ### kubeadmをアップグレード 1.  Windowsノードから、kubeadmをアップグレードします。: ```powershell # {{< param "fullversion" >}}を目的のバージョンに置き換えます curl.exe -Lo C:kkubeadm.exe https://dl.k8s.io/{{< param "fullversion" >}}/bin/windows/amd64/kubeadm.exe ``` ### ノードをドレインする 1.  Kubernetes APIにアクセスできるマシンから、 ノードをスケジュール不可としてマークして、ワークロードを削除することでノードのメンテナンスを準備します: ```shell # <node-to-drain>をドレインするノードの名前に置き換えます kubectl drain <node-to-drain> --ignore-daemonsets ``` このような出力結果が表示されるはずです: ``` node/ip-172-31-85-18 cordoned node/ip-172-31-85-18 drained ``` ### kubeletの構成をアップグレード 1. Windowsノードから、次のコマンドを呼び出して新しいkubelet構成を同期します: ```powershell kubeadm upgrade node ``` ### kubeletをアップグレード 1.  Windowsノードから、kubeletをアップグレードして再起動します: ```powershell stop-service kubelet curl.exe -Lo C:kkubelet.exe https://dl.k8s.io/{{< param "fullversion" >}}/bin/windows/amd64/kubelet.exe restart-service kubelet ``` ### ノードをオンライン状態に 1.  Kubernetes APIにアクセスできるマシンから、 スケジュール可能としてマークして、ノードをオンラインに戻します: ```shell # <node-to-drain>をノードの名前に置き換えます kubectl uncordon <node-to-drain> ``` ### kube-proxyをアップグレード 1. Kubernetes APIにアクセスできるマシンから、次を実行します、 もう一度{{< param "fullversion" >}}を目的のバージョンに置き換えます: ```shell curl -L https://github.com/kubernetes-sigs/sig-windows-tools/releases/latest/download/kube-proxy.yml | sed 's/VERSION/{{< param "fullversion" >}}/g' | kubectl apply -f - ``` </ins>

Discussion:
This is a Feature Request What would you like to be Translate docs/tasks/administer-cluster/kubeadm/upgrading-windows-nodes/ into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign
/close
Closing this issue. <detailsIn response to : /close 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:
{{< note >}} To be able to create Indexed Jobs, make sure to enable the `IndexedJob` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) <del> on the [API server](docs/reference/command-line-tools-reference/kube-apiserver/) </del> <ins> on the [API server](/docs/reference/command-line-tools-reference/kube-apiserver/) </ins> and the [controller manager](/docs/reference/command-line-tools-reference/kube-controller-manager/). {{< /note >}}

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:
{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} <del> Each node in your cluster must have at least 1 CPU. </del> <ins> Your cluster must have at least 1 CPU available for use to run the task examples. </ins> {{% /capture %}}

Discussion:
A couple of pages: state that Based on what I know about nodes, this seems like something you could take for granted. Consider ~dropping~ revising that text.
/kind cleanup /priority backlog
Just realized this is talking about Kubernetes' count of CPUs, rather than what (say) the Linux kernel would see. That might not be obvious to every reader&mdash;I missed it, for example.
/language en
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
/remove-lifecycle stale
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
/remove-lifecycle stale
/help
Happy to help with explanations for anyone who is picking this up.
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
/remove-lifecycle stale
/assign /remove-help
I was reviewing the docs and I think the statement is referring to the minimal requirements to execute the proposed tasks (and I think this is wrong, because some exercises goes up to 2 cores). Not sure if my understanding is the same as yours.
The “1 CPU” means 1.0 of Kubernetes CPU units. That's different from saying “there needs to be at least one physical CPU core available”. Readers new to Kubernetes might not grasp that Kubernetes has its own idea of CPU number and assume that a Node that runs the kubelet OK must have at least one installed core available to make code execution possible. For example: a node with 0.5 CPU doesn't meet the 1.0 CPU requirement.

If some exercises require more than 1.0 CPU then those pages should explain that. I think addressing that might be a different issue though.
Honestly, I still don't get it. I thought the Kubernetes CPU reflects what the operating system reports (ex.: ). I wasn't considering possible to have a Kubelet running on a node and reporting only 0.5 CPU (how do we do that? flags? cgroup via systemd?). Since the docs are not using term physical, I still think the original author was referring to minimum required resource for the task examples.
To be honest, I might have this wrong too. I do know that the existing text is not clear.
An example of an instance type with < 1.0 CPU:
Even those shared core instances will reports 1 vCPU, but I got your point. I'll try something here!
Change:
- wget - "-O" - "/work-dir/index.html" <del> - http://kubernetes.io </del> <ins> - http://info.cern.ch </ins> volumeMounts: - name: workdir mountPath: "/work-dir"

Discussion:
command: wget "-O" "/work-" : command: wget "-O" "/work-"
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
why?
sync from en