jiebi/CodeConvo huggingface dataset:
Change:
curl -L https://github.com/kubernetes-sigs/sig-windows-tools/releases/latest/download/flannel-overlay.yml | sed 's/Ethernet/Ethernet0 2/g' | kubectl apply -f - ``` {{< /note >}} ### Windowsワーカーノードの参加

Discussion:
Problem: Based on , I have created this issue/task to help update the [ja] language documentation. Proposed Solution: Page to Update: In the branch, I found: Results for "fullversion" in "k8s-website/content/ja" /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/concepts/containers/container- 46: IPDNS /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/concepts/services-networking/connect-applications- 146: /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/concepts/services- 283: )Service /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/setup/learning- 220: {{< param "fullversion" }}: 223: minikube start --kubernetes-version {{< param "fullversion" }} /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/tasks/tools/install- 34: Linux{{< param "fullversion" }}: 37: curl -LO {{< param "fullversion" }}/bin/linux/amd64/kubectl 116: macOS{{< param "fullversion" }}: 119: curl -LO {{< param "fullversion" }}/bin/darwin/amd64/kubectl 181: {{< 181: "fullversion" }}){{< param "fullversion" }} 186: curl -LO {{< param "fullversion" }} /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/tasks/administer-cluster/kubeadm/adding-windows- 107: Kubernetes{{< param "fullversion" }} 111: releases/latest/download/kube- kubectl apply -f - 150: .PrepareNode.

ps1 -KubernetesVersion {{% param "fullversion" %}} /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/tasks/administer-cluster/kubeadm/upgrading-windows- 35: # {{% param "fullversion" %}} 36: -Lo C:k {{% param "fullversion" %}} 70: -Lo C:k {{% param "fullversion" %}} 86: {{< param "fullversion" }}: 89: releases/latest/download/kube- kubectl apply -f - /sig docs /sig localization /language ja cc:
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: All the other documents need to change into or appropriatly. Since several languages are involved, I'd like to share this issue to check all localizations complete the task. Proposed Solution: Page to Update: /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/concepts/services-networking/connect-applications- /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/concepts/services- /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/setup/learning- /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/tasks/tools/install- /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/tasks/administer-cluster/kubeadm/adding-windows- /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/tasks/administer-cluster/kubeadm/upgrading-windows- /sig localization /language ja cc: 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
cc:
/triage accepted /area localization /priority backlog
Change:
```sh root@HOST0 $ kubeadm init phase etcd local --config=/tmp/${HOST0}/kubeadmcfg.yaml <del> root@HOST1 $ kubeadm init phase etcd local --config=/tmp/${HOST1}/kubeadmcfg.yaml root@HOST2 $ kubeadm init phase etcd local --config=/tmp/${HOST2}/kubeadmcfg.yaml </del> <ins> root@HOST1 $ kubeadm init phase etcd local --config=$HOME/kubeadmcfg.yaml root@HOST2 $ kubeadm init phase etcd local --config=$HOME/kubeadmcfg.yaml </ins> ``` 1. Optional: Check the cluster health

Discussion:
I don't have any issue .but i have suggestion . when i follow the official guide i noticed a document incorrect path issue. In the steps 7 they mention in /tmp folder all the etcd instance. but steps 6 showing in the only $HOST0 having tmp other etcd instance having document root. Document should update the correct path !
/language en /sig cluster-lifecycle I don't think I've understood the report you've filed In the existing page, which specific part of that text contains the details that you think we should change?
Hi In the step 7 path should be correct as below root {HOST0} root root
if you look at step 4: all files are under ~so it seems step 6 is the one that is wrong.~ EDIT: never mind the copied files end up in HOME with scp.
/assign
/kind bug /triage accepted
fix here:
Change:
and they were applied successfully. For more details, read about [LimitRanges](/docs/concepts/policy/limit-range). <ins> ### addonmanager.kubernetes.io/mode Example: `addonmanager.kubernetes.io/mode: "Reconcile"` Used on: All objects To specify how an add-on should be managed, you can use the `addonmanager.kubernetes.io/mode` label. This label can have one of three values: `Reconcile`, `EnsureExists`, or `Ignore`. - `Reconcile`: Addon resources will be periodically reconciled with the expected state. If there are any differences, the add-on manager will recreate, reconfigure or delete the resources as needed. This is the default mode if no label is specified. - `EnsureExists`: Addon resources will be checked for existence only but will not be modified after creation. The add-on manager will create or re-create the resources when there is no instance of the resource with that name. - `Ignore`: Addon resources will be ignored. This mode is useful for add-ons that are not compatible with the add-on manager or that are managed by another controller. For more details, see [Addon-manager](https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/addon-manager/README.md) </ins> ### beta.kubernetes.io/arch (deprecated) This label has been deprecated. Please use `kubernetes.io/arch` instead.

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 and document the label Why is this needed mentions a label but this is not yet mentioned in Comments The whole tree within is deprecated. I'm not sure if the label is as well. /language en /kind feature
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
We should do this /lifecycle frozen /triage accepted
This issue has not been updated in over 1 year, and should be re-triaged. You can: Confirm that this issue is still relevant with (org members only) Close this issue with For more details on the triage process, see /remove-triage accepted
/triage accepted /priority backlog
/assign
Change:
|`custom-class-c`         | 1000                   | |`regular/unset`          | 0                      | <del> Within the [kubelet configuration](/docs/reference/config-api/kubelet-config.v1beta1/#kubelet-config-k8s-io-v1beta1-KubeletConfiguration) </del> <ins> Within the [kubelet configuration](/docs/reference/config-api/kubelet-config.v1beta1/) </ins> the settings for `shutdownGracePeriodByPodPriority` could look like: |Pod priority class value|Shutdown period|

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Url selector #kubelet-config-k8s-io-v1beta1-KubeletConfiguration doesn't make a difference between: and Proposed Solution: Removing the selector from the URLs Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/language en
/assign
/retitle Problems with (generated) reference for kubelet configuration
Change:
<del> #hero { </del> <ins> body.cid-training body.cid-training #hero { </ins> text-align: left; padding-bottom: 20px; } <del> .section { </del> <ins> body.cid-training body.cid-training .section { </ins> clear: both; padding: 0px; margin-bottom: 2em; width: 100%; } <del> section.call-to-action { </del> <ins> body.cid-training section.call-to-action { </ins> color: #ffffff; background-color: #3371e3; } <del> section.call-to-action .main-section { </del> <ins> body.cid-training section.call-to-action .main-section { </ins> max-width: initial; } <del> section.call-to-action .main-section > div.call-to-action { </del> <ins> body.cid-training section.call-to-action .main-section > div.call-to-action { </ins> display: flex; flex-direction: row; flex-wrap: wrap; <del> flex-basis: auto; </del> justify-content: center; align-items: center; margin: initial;

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:
CLIにはPVに紐付いているPVCの名前が表示されます。 <del> ## 永続ボリューム要求 </del> <ins> ## 永続ボリューム要求 {#persistentvolumeclaims} </ins> 各PVCにはspecとステータスが含まれます。これは、仕様とクレームのステータスです。

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. --Why is this needed This document is not translated in Japanese. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --Copy a file from en contents to concepts/policy/resource- and translate it into Japanese.
/assign /language-ja
/language ja
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
/assign
/unassign
/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:
used. If you set the <del> [`storageclass.kubernetes.io/is-default-class`](/docs/reference/labels-annotations-taints/#ingressclass-kubernetes-io-is-default-class) </del> <ins> [`storageclass.kubernetes.io/is-default-class`](/docs/reference/labels-annotations-taints/#storageclass-kubernetes-io-is-default-class) </ins> annotation to true on more than one StorageClass in your cluster, and you then create a PersistentVolumeClaim with no `storageClassName` set, Kubernetes uses the most recently created default StorageClass.

Discussion:
This is bug report There is wrong link referring to the page in Default StorageClass Problem in Default StorageClass , there is which is redirecting to the wrong source Solution update with valid link Page to update
/sig docs /language en /assign
/triage accepted
fixed this issue in PTAL!!
/kind bug
Change:
exceeding its requests, it won't be evicted. Another Pod with higher priority that exceeds its requests may be evicted. ## {{% heading "whatsnext" %}} * Read about using ResourceQuotas in connection with PriorityClasses: [limit Priority Class consumption by default](/docs/concepts/policy/resource-quotas/#limit-priority-class-consumption-by-default)

Discussion:
Page: The second paragraph needs clarity. The QoS class isn't actually used to calculate the pod eviction order, but can be used to estimate the order. The kubelet uses Priority to order pods for out-of-resource eviction. You can use the QoS class to estimate the order in which pods are most likely to get evicted. The kubelet ranks pods for eviction based on the following factors: Whether or not the pod resource usage exceeds the defined requests The pod Priority The amount of the pod's resource consumption relative to the defined requests For more information, see [Evicting end-user pods]. Note: this will likely link to instead of the existing Out of Resource Handling topic. /sig docs /language en /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
/sig node
/triage accepted eh, worth a shot
The label cannot be applied. Only GitHub organization members can add the label. <detailsIn response to : /triage accepted 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:
### curlを使用してWindowsへkubectlのバイナリをインストールする <del> 1. [こちらのリンク](https://storage.googleapis.com/kubernetes-release/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe)から、最新リリースである{{< param "fullversion" >}}をダウンロードしてください。 </del> <ins> 1. [こちらのリンク](https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe)から、最新リリースである{{< param "fullversion" >}}をダウンロードしてください。 </ins> または、`curl`をインストールされていれば、次のコマンドも使用できます: ```bash <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe </del> <ins> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe </ins> ``` <del> 最新の安定版を入手する際は(たとえばスクリプトで使用する場合)、[https://storage.googleapis.com/kubernetes-release/release/stable.txt](https://storage.googleapis.com/kubernetes-release/release/stable.txt)を参照してください。 </del> <ins> 最新の安定版を入手する際は(たとえばスクリプトで使用する場合)、[https://dl.k8s.io/release/stable.txt](https://dl.k8s.io/release/stable.txt)を参照してください。 </ins> 2. バイナリをPATHに追加します 3. `kubectl`のバージョンがダウンロードしたものと同じであることを確認してください:

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:
Pour télécharger une version spécifique, remplacez `$(curl -s https://dl.k8s.io/release/stable.txt)` avec la version spécifique. <del> Par exemple, pour télécharger la version {{< param "fullversion" >}} sur Linux, tapez : </del> <ins> Par exemple, pour télécharger la version {{< skew currentPatchVersion >}} sur Linux, tapez : </ins> ``` <del> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/linux/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/linux/amd64/kubectl </ins> ``` 2. Rendez le binaire kubectl exécutable.

Discussion:
This is a Bug Report Problem: The param is deprecated. Proposed Solution: Replace the shortcode (French pages), for example with when possible and append when needed. Part of /language fr /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:
`SchedulingDisabled`はKubernetesのAPIにおけるConditionではありません;その代わり、cordonされたノードはUnschedulableとしてマークされます。 {{< /note >}} <del> ノードのConditionはJSONオブジェクトで表現されます。例えば、正常なノードの場合は以下のような構造体が表示されます。 </del> <ins> Nodeの状態は、Nodeリソースの`.status`の一部として表現されます。例えば、正常なノードの場合は以下のようなjson構造が表示されます。 </ins> ```json "conditions": [

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. --About Graceful node shutdown Swap memory management Why is this needed Graceful node shutdown is FEATURE STATE: Kubernetes v1.21 [beta] and Swap memory management is FEATURE STATE: Kubernetes v1.22 [alpha] The Japanese documents do not reflect the latest updates of them. In addition to that, I made some corrections. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/language ja
/assign
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]:
The Kubernetes project currently lacks enough active 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 Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:
/remove-lifecycle rotten because the related PR is under reviewing /triage accepted
Change:
<div class="layout" id="top"> <main class="content katacoda-content"> <del> <div class="katacoda"> <div class="katacoda__alert"> Para interagir com o terminal, favor utilizar a versão desktop/tablet </div> <div class="katacoda__box" id="inline-terminal-1"  data-katacoda-id="kubernetes-bootcamp/5" data-katacoda-color="326de6" data-katacoda-secondary="273d6d" data-katacoda-hideintro="false" data-katacoda-prompt="Kubernetes Bootcamp Terminal" style="height: 600px;"> </div> </div> <div class="row"> <div class="col-md-12"> <a class="btn btn-lg btn-success" href="/docs/tutorials/kubernetes-basics/update/update-intro/" role="button">Continue para o Módulo 6<span class="btn__next">›</span></a> </div> </div> </del> <ins> <div> <h2 class="katacoda-gone"> Conteúdo indisponível </h2> <p> O tutorial interativo de como escalonar um aplicativo que está rodando no seu cluster não está disponível. Para mais informações, veja o <a href="https://kubernetes.io/pt-br/blog/2023/02/14/kubernetes-katacoda-tutorials-stop-from-2023-03-31/"> anúncio de encerramento do Katacoda</a>. </p> </div> </ins> </main> <del> <a class="scrolltop" href="#top"></a> </del> </div> </body>

Discussion:
The terminal to use the interactive tutorials is using Katacoda, however, it was purchased by O'Reilly and is outside the domain that the terminal is using to run.
Hi You can ask support queries in channels.
Page related to issue: /language pt
/retitle [pt-br] Remove the obsolete online interactive tutorial from the page
For anyone willing to assist on this, please refer to PR for information regarding the implementation of similar changes carried out on the main website (i.e. English pages).
/good-first-isssue
/triage accepted /assign
/retitle [pt-br] Obsolete online interactive tutorial in the Using Minikube to Create a Cluster page /kind bug
Change:
- start with an alphanumeric character - end with an alphanumeric character <ins> ### RFC 1035 Label Names Some resource types require their names to follow the DNS label standard as defined in [RFC 1035](https://tools.ietf.org/html/rfc1035). This means the name must: - contain at most 63 characters - contain only lowercase alphanumeric characters or '-' - start with an alphabetic character - end with an alphanumeric character </ins> ### Path Segment Names Some resource types require their names to be able to be safely encoded as a

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: Pod / Service names can not start with an alphanumeric character in kubernetes, but should be possible according to RFC1123 Proposed Solution: Change documentation in sections and to: or change kubernetes name check to use the specification in RFC1123. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: 19.11 <!--Additional Information:--
Kubernetes does not strictly follow the RFC.
this might be true, but the documentation says otherwise. eg.
According to the validation logic, starting with alphanumeric characters should be okay. Can you paste the error message you have got?
I tried locally, and getting this error !
Just double checked the validation logic for core v1 Service. Its name must be a RFC1035 label rather than a RFC1123 label. This is something we need to fix in the docs. Related code:
/triage accepted /kind bug /assign