jiebi/CodeConvo huggingface dataset:
Change:
{{< note >}} Um eine spezifische Version herunterzuladen, ersetze `$(curl -L -s https://dl.k8s.io/release/stable.txt)` mit der spezifischen Version <del> Um zum Beispiel Version {{< param "fullversion" >}} auf Intel macOS herunterzuladen: </del> <ins> Um zum Beispiel Version {{< skew currentPatchVersion >}} auf Intel macOS herunterzuladen: </ins> ```bash <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> ``` Für macOS auf Apple Silicon (z.B. M1/M2): ```bash <del> curl -LO "https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/darwin/arm64/kubectl" </del> <ins> curl -LO "https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/darwin/arm64/kubectl" </ins> ``` {{< /note >}}

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:
kubectl version --client --output=yaml ``` <del> 1. After installing the plugin, clean up the installation files: </del> <ins> 1. After installing and validating kubectl, delete the checksum file: </ins> ```bash <del> rm kubectl kubectl.sha256 </del> <ins> rm kubectl.sha256 </ins> ``` ### Install with Homebrew on macOS

Discussion:
In Step 6 of , The command says to delete kubectl along with kubectl.sha256 file, but kubectl is already moved in step 4. The command needs to be rm kubectl.sha256 instead of rm kubectl kubectl.sha256
/language en
/retitle Incorrect cleanup instruction in macOS kubectl installation guide /kind bug
Indeed there appears to be discrepancy in the cleanup instruction as the removal command in Step 6 erroneously attempts to delete the already-moved kubectl binary as part of Step 4. We should address this inconsistency. /triage accepted /priority backlog
I can help with this. Worked on this files before too. /assign
i submited PR pelase review when got time. Thanks!
Change:
- `cosign` ([install guide](https://docs.sigstore.dev/cosign/installation/)) - `curl` (often provided by your operating system) <del> - `jq` ([download jq](https://stedolan.github.io/jq/download/)) </del> <ins> - `jq` ([download jq](https://jqlang.github.io/jq/download/)) </ins> ## Verifying binary signatures

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:
--- title: Kubernetes 对象管理 <del> redirect_from: - "/docs/concepts/tools/kubectl/object-management-overview/" - "/docs/concepts/tools/kubectl/object-management-overview.html" - "/docs/user-guide/working-with-resources/" - "/docs/user-guide/working-with-resources.html" </del> --- {% capture overview %}

Discussion:
This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: This link: redirects to this page: The link is found here: Proposed Solution: Fix the redirect for /docs/user-guide/working-with-resources Page to Update: Redirect for
Yeah, it's confusing. Why it's P3? How hard to fix it? How I can help?
I know what the problem is and will submit a PR shortly. None of the pages in the /cn directory should have the directive at the top of the page. For example, currently, /cn/docs/tutorials/object-management-kubectl/object- has this set at the top of the page:
Wow! Thank you!!
Ok, nothing should be redirected to the /cn pages anymore. Cheers
Change:
### Cron schedule syntax ``` <del> # ┌───────────── minute (0 - 59) # │ ┌───────────── hour (0 - 23) # │ │ ┌───────────── day of the month (1 - 31) # │ │ │ ┌───────────── month (1 - 12) # │ │ │ │ ┌───────────── day of the week (0 - 6) (Sunday to Saturday; # │ │ │ │ │                                   7 is also Sunday on some systems) # │ │ │ │ │ # │ │ │ │ │ # * * * * * </del> <ins> #      ┌────────────────── timezone (optional) #      |      ┌───────────── minute (0 - 59) #      |      │ ┌───────────── hour (0 - 23) #      |      │ │ ┌───────────── day of the month (1 - 31) #      |      │ │ │ ┌───────────── month (1 - 12) #      |      │ │ │ │ ┌───────────── day of the week (0 - 6) (Sunday to Saturday; #      |      │ │ │ │ │                                   7 is also Sunday on some systems) #      |      │ │ │ │ │ #      |      │ │ │ │ │ # CRON_TZ=UTC * * * * * </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: PR highlights that the documentation for CronJob is out of date since the v1.22 release. We're now using the revised controller by default (with no option to revert) and also a different syntax for the schedule. Proposed Solution: Identify stale or incorrect data on the pages about CronJobs Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v.122 Additional Information: /kind bug /sig apps Relevant to
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:
<ins> apiVersion: v1 kind: Service metadata: name: my-service spec: ipFamily: IPv6 selector: app: MyApp ports: - protocol: TCP port: 80 targetPort: 9376 </ins>  No newline at end of file

Discussion:
This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign
Change:
A partir de Kubernetes 1.8, el servidor de métricas se despliega por defecto como un objeto de tipo [Deployment](https://github.com/docs/concepts/workloads/controllers/deployment/) en clústeres creados con el script `kube-up.sh`. Si usas otro mecanismo de configuración de Kubernetes, puedes desplegarlo <del> usando los [yamls de despliegue](https://github.com/kubernetes-incubator/metrics-server/tree/master/deploy) </del> <ins> usando los [yamls de despliegue](https://github.com/kubernetes-sigs/metrics-server/releases) </ins> proporcionados. Está soportado a partir de Kubernetes 1.7 (más detalles al final). El servidor reune métricas de la Summary API, que es expuesta por el [Kubelet](/docs/admin/kubelet/) en cada nodo.

Discussion:
deployment does not exist
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:
## 使用例 <del> 一度RuntimeClassがクラスターに対して設定されると、それを使用するのは非常に簡単です。PodSpecの`runtimeClassName`を指定してください。 </del> <ins> RuntimeClassがクラスターに対して設定されると、PodSpecで`runtimeClassName`を指定して使用できます。 </ins> 例えば ```yaml

Discussion:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/containers/runtime- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/containers/runtime- is outdated. Comments /language ja /assign
/triage accepted
Change:
### 추가 컨트롤 플레인 노드 업그레이드 <del> 1.  첫 번째 컨트롤 플레인 노드와 동일하지만 다음을 사용한다. </del> <ins> 첫 번째 컨트롤 플레인 노드와 동일하지만 다음을 사용한다. </ins> <del> ``` sudo kubeadm upgrade node ``` </del> <ins> ``` sudo kubeadm upgrade node ``` </ins> <del> 아래 명령 대신 위의 명령을 사용한다. </del> <ins> 아래 명령 대신 위의 명령을 사용한다. </ins> <del> ``` sudo kubeadm upgrade apply ``` </del> <ins> ``` sudo kubeadm upgrade apply ``` </ins> <del> 또한 `sudo kubeadm upgrade plan` 은 필요하지 않다. </del> <ins> 또한 `sudo kubeadm upgrade plan` 은 필요하지 않다. </ins> ### kubelet과 kubectl 업그레이드 <del> 1.  모든 컨트롤 플레인 노드에서 kubelet 및 kubectl을 업그레이드한다. </del> <ins> 모든 컨트롤 플레인 노드에서 kubelet 및 kubectl을 업그레이드한다. </ins> <del> {{< tabs name="k8s_install_kubelet" >}} {{% tab name="Ubuntu, Debian 또는 HypriotOS" %}} </del> <ins> {{< tabs name="k8s_install_kubelet" >}} {{% tab name="Ubuntu, Debian 또는 HypriotOS" %}} </ins> # 1.18.x-00의 x를 최신 패치 버전으로 바꾼다 apt-mark unhold kubelet kubectl &&  apt-get update && apt-get install -y kubelet=1.18.x-00 kubectl=1.18.x-00 &&  apt-mark hold kubelet kubectl <ins> - </ins> # apt-get 버전 1.1부터 다음 방법을 사용할 수도 있다 apt-get update &&  apt-get install -y --allow-change-held-packages kubelet=1.18.x-00 kubectl=1.18.x-00 <del> {{% /tab %}} {{% tab name="CentOS, RHEL 또는 Fedora" %}} </del> <ins> {{% /tab %}} {{% tab name="CentOS, RHEL 또는 Fedora" %}} </ins> # 1.18.x-0에서 x를 최신 패치 버전으로 바꾼다 yum install -y kubelet-1.18.x-0 kubectl-1.18.x-0 --disableexcludes=kubernetes <del> {{% /tab %}} {{< /tabs >}} </del> <ins> {{% /tab %}} {{< /tabs >}} </ins> <del> 1.  kubelet을 다시 시작한다. </del> <ins> kubelet을 다시 시작한다. </ins> <del> ```shell sudo systemctl restart kubelet ``` </del> <ins> ```shell sudo systemctl restart kubelet ``` </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: Broken layout on "kubeadm " ! Proposed Solution: Check and apply upstream changes. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ko
/assign
/unassign This issue already has been assigned to .
Change:
Notice how the number of desired replicas is 3 according to `.spec.replicas` field. <del> 3. To see the Deployment rollout status, run `kubectl rollout status deployment.v1.apps/nginx-deployment`. </del> <ins> 3. To see the Deployment rollout status, run `kubectl rollout status deployment/nginx-deployment`. </ins> The output is similar to: ```

Discussion:
I am following the minikube tutorial () and find two different ways to getting the roll-out status of an deployment: vs. I am using locally: What is the difference between these two? Might be a good idea to add a node to step number 3 which explains this.
I think that an appropriate improvement that's in line with your comment is to change to run instead. That sounds reasonable to do. /language en /kind cleanup /triage accepted /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 : I think that an appropriate improvement that's in line with your comment is to change to run instead. /language en /kind cleanup /triage accepted /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
/retitle Multiple way to refer to Deployment resource confusing in Deployment concept page
/assign
Change:
persistent volume (virtual disk) is being created. The virtual disk is distributed across the Virtual SAN datastore to meet the requirements. <del> You can see [Storage Policy Based Management for dynamic provisioning of volumes](https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/policy-based-mgmt.html) </del> <ins> You can see [Storage Policy Based Management for dynamic provisioning of volumes](https://github.com/vmware-archive/vsphere-storage-for-kubernetes/blob/fa4c8b8ad46a85b6555d715dd9d27ff69839df53/documentation/policy-based-mgmt.md) </ins> for more details on how to use storage policies for persistent volumes management.

Discussion:
Problem: The text on is not working, it should point to these Check the page for the problem. Page to Update: Proposed Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text Storage Policy Based Management for dynamic provisioning of volumes to and not to this . /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 not working, it should point to these Check the page for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text Storage Policy Based Management for dynamic provisioning of volumes to and not to this . /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
/triage accepted
Change:
padding-bottom: 5rem; } <del> section.call-to-action .main-section > div.call-to-action > div { order: 1; </del> <ins> body.cid-training section.call-to-action .main-section > div.call-to-action > div { </ins> padding: 20px; } <del> section.call-to-action .main-section .cta-text { text-align: center; flex: 1 1 auto; max-width: 50vw; </del> <ins> body.cid-training section.call-to-action .main-section .cta-text { width: 100%; flex-basis: 100%; </ins> } <del> /* if max() and min() are available, use them */ section.call-to-action .main-section .cta-text { </del> <ins> body.cid-training section.call-to-action .main-section .cta-text > * { margin-left: auto; margin-right: auto; text-align: center; /* if max() and min() are available, use them */ </ins> min-width: min(20em, 50vw); max-width: min(1000px, 50vw); } <del> section.call-to-action .main-section .cta-image.cta-image-before { order: 0 } section.call-to-action .main-section .cta-image.cta-image-after { order: 2 </del> <ins> body.cid-training section.call-to-action .main-section .cta-image { max-width: max(20vw,150px); flex-basis: auto; </ins> } <del> section.call-to-action .main-section .cta-image > img { </del> <ins> body.cid-training section.call-to-action .main-section .cta-image > img { </ins> display: block; width: 150px; margin: auto; } <del> .col { </del> <ins> body.cid-training #logo-cks { order: 2; /* central */ } body.cid-training .col { </ins> display: flex; flex-direction: row; float: left; margin: 1% 0 1% 1.6%; } <del> .col:first-child { margin-left: 0; } </del> <ins> body.cid-training .col:first-child { margin-left: 0; } </ins> <del> .col-container { </del> <ins> body.cid-training .col-container { </ins> display: flex; /* Make the container element behave like a table */ flex-direction: row; width: 100%; /* Set full-width to expand the whole page */ padding-bottom: 30px; } <del> .col-nav { </del> <ins> body.cid-training .col-nav { </ins> display: flex; flex-grow: 1; width: 18%;

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 to mention the new Kubernetes Security Specialist Certification Why is this needed There is a Kubernetes Security Specialist Certification, coming in November 2020. Comments /kind feature /language en
/priority important-soon
let's collaborate to put everything in place to make this into a Good First Issue.
Design-wise, it's much easier to place 2 certification logos than 3. do you have any thoughts on how to adjust things design-wise to incorporate the 3rd certification?
/sig security
/triage accepted
/cc
Change:
--- title: "ツールのインストール" <del> description: Kubernetesのツールをローカルのコンピュータ上にセットアップします。 </del> <ins> description: Kubernetesのツールをローカルのコンピューター上にセットアップします。 </ins> weight: 10 no_list: true ---

Discussion:
This is a Feature Request What would you like to be fix the notation variations of the term "computer" valid: invalid: | Why is this needed In Japanese documents, There are notation variations. The Japanese localization of k/website has rules, so we want to follow them. Comments FYI: Japanese Localization document: command /language ja /area localization /help /good-first-issue
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
PTAL before woking
PR
/remove-help
Change:
<ins> --- title: huge pageを管理する content_type: task description: クラスター内のスケジュール可能なリソースとしてhuge pageの設定と管理を行います。 --- <!-- overview --> {{< feature-state state="stable" >}} Kubernetesでは、事前割り当てされたhuge pageをPod内のアプリケーションに割り当てたり利用したりすることをサポートしています。このページでは、ユーザーがhuge pageを利用できるようにする方法について説明します。 ## {{% heading "prerequisites" %}} 1. Kubernetesのノードがhuge pageのキャパシティを報告するためには、ノード上でhuge pageを事前割り当てしておく必要があります。1つのノードでは複数のサイズのhuge pageが事前割り当てできます。 ノードは、すべてのhuge pageリソースを、スケジュール可能なリソースとして自動的に探索・報告してくれます。 <!-- steps --> ## API huge pageはコンテナレベルのリソース要求で`hugepages-<size>`という名前のリソースを指定することで利用できます。ここで、`<size>`は、特定のノード上でサポートされている整数値を使った最も小さなバイナリ表記です。たとえば、ノードが2048KiBと1048576KiBのページサイズをサポートしている場合、ノードはスケジュール可能なリソースとして、`hugepages-2Mi`と`hugepages-1Gi`の2つのリソースを公開します。CPUやメモリとは違い、huge pageはオーバーコミットをサポートしません。huge pageリソースをリクエストするときには、メモリやCPUリソースを同時にリクエストしなければならないことに注意してください。 1つのPodのspec内に書くことで、Podから複数のサイズのhuge pageを利用することもできます。その場合、すべてのボリュームマウントで`medium: HugePages-<hugepagesize>`という表記を使う必要があります。 ```yaml apiVersion: v1 kind: Pod metadata: name: huge-pages-example spec: containers: - name: example image: fedora:latest command: - sleep - inf volumeMounts: - mountPath: /hugepages-2Mi name: hugepage-2mi - mountPath: /hugepages-1Gi name: hugepage-1gi resources: limits: hugepages-2Mi: 100Mi hugepages-1Gi: 2Gi memory: 100Mi requests: memory: 100Mi volumes: - name: hugepage-2mi emptyDir: medium: HugePages-2Mi - name: hugepage-1gi emptyDir: medium: HugePages-1Gi ``` Podで1種類のサイズのhuge pageをリクエストするときだけは、`medium: HugePages`という表記を使うこともできます。 ```yaml apiVersion: v1 kind: Pod metadata: name: huge-pages-example spec: containers: - name: example image: fedora:latest command: - sleep - inf volumeMounts: - mountPath: /hugepages name: hugepage resources: limits: hugepages-2Mi: 100Mi memory: 100Mi requests: memory: 100Mi volumes: - name: hugepage emptyDir: medium: HugePages ``` - huge pageのrequestsはlimitsと等しくなければなりません。limitsを指定した場合にはこれがデフォルトですが、requestsを指定しなかった場合にはデフォルトではありません。 - huge pageはコンテナのスコープで隔離されるため、各コンテナにはそれぞれのcgroupサンドボックスの中でcontainer specでリクエストされた通りのlimitが設定されます。 - huge pageベースのEmptyDirボリュームは、Podがリクエストしたよりも大きなサイズのページメモリーを使用できません。 - `shmget()`に`SHM_HUGETLB`を指定して取得したhuge pageを使用するアプリケーションは、`/proc/sys/vm/hugetlb_shm_group`に一致する補助グループ(supplemental group)を使用して実行する必要があります。 - namespace内のhuge pageの使用量は、ResourceQuotaに対して`cpu`や`memory`のような他の計算リソースと同じように`hugepages-<size>`というトークンを使用することで制御できます。 - 複数のサイズのhuge pageのサポートはフィーチャーゲートによる設定が必要です。{{< glossary_tooltip text="kubelet" term_id="kubelet" >}}と{{< glossary_tooltip text="kube-apiserver" term_id="kube-apiserver" >}}上で、`HugePageStorageMediumSize`[フィーチャーゲート](/ja/docs/reference/command-line-tools-reference/feature-gates/)を使用すると有効にできます(`--feature-gates=HugePageStorageMediumSize=true`)。 </ins>

Discussion:
This is a Feature Request What would you like to be Translate 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