jiebi/CodeConvo huggingface dataset:
Change:
- [create Secret from config file](/docs/tasks/configmap-secret/managing-secret-using-config-file/) - [create Secret using kustomize](/docs/tasks/configmap-secret/managing-secret-using-kustomize/) <del> ### Editing a Secret </del> <ins> ## Editing a Secret </ins> An existing Secret may be edited with the following command:

Discussion:
This is a Feature Request What would you like to be More detailed documentation about Secret, in addition to the current lengthy Secret concept. Why is this needed We have many secrets about Secret which should be documented. For example, the securet type can be one of: - - - - Some secret types needs special annotation or data keys. For example, for service account tokens, the following two annotations are required: - AND, the following key is required in the data property: Comments In addition to the new contents to be , we should consider moving some of the task-alike content out of the concept introduction at
/priority important-longterm
Can you please point me where can I read more about , Also which could help in add & improving the following? Thanks
This information is in the upstream source code. There is no convenient way for dumping them as swagger/openapi specs which are used for generating the API reference documentation. I would even suspect there could be one in future given the complexity of the semantics and nesting of struct definitions in Go lang. You have to read the source code to understand the many constraints for resources like this. For the resource type, the validation logic is here:
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
+1 Especially, is the token inside a secret periodically roated? Expiration of seems to be set to 5 years. Is it going to be renewed automatically, or do you have to renew manually (and how)? What's the impact to already running workloads that hit the expiration?
+1 Additionally: Document that secrets whose keys are removed from secrets files remain in the deployed secrets as empty strings, meaning the secrets resource must be deleted to remove that key and rebuilt on next deploy.
Immutable Secrets are also relevant ( has some 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
Given the mentioned gap from the issue description and the various comments received, I'd like to propose a freeze of lifecycle for this issue. /lifecycle frozen
Put this on my TODO list. /assign
Change:
``` [kubernetes] name=Kubernetes <del> baseurl=https://pkgs.k8s.io/core:/stable:/v{{< param "version" >}}/rpm/ </del> <ins> baseurl=https://pkgs.k8s.io/core:/stable:/{{< param "version" >}}/rpm/ </ins> enabled=1 gpgcheck=1 <del> gpgkey=https://pkgs.k8s.io/core:/stable:/v{{< param "version" >}}/rpm/repodata/repomd.xml.key </del> <ins> gpgkey=https://pkgs.k8s.io/core:/stable:/{{< param "version" >}}/rpm/repodata/repomd.xml.key </ins> exclude=kubelet kubeadm kubectl cri-tools kubernetes-cni ```

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 section , under tab, there is an extra "v" in the and URLs corresponding to the latest kubernetes version.  Proposed Solution: Correct to . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
I can contribute the fix - easy one.
/triage accepted Thanks
Change:
mymap-child    0      13m8s mymap-parent   0      13m8s <del> kubectl delete --cascade=false configmap/mymap-parent </del> <ins> kubectl delete --cascade=orphan configmap/mymap-parent </ins> configmap "mymap-parent" deleted kubectl get configmap

Discussion:
According to the can get a parameter with a value of "background", "orphan", or "foreground". proposes to use .
Hello Related PRs/issues: So, the page should be updated. /kind bug /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 : Hello is now deprecated in favor of warning: is deprecated (boolean value) and can be replaced with Cascade=false is deprecated in kubectl 1.21, according to Bug /language en /help </details
/triage accepted
/good-first-issue
This request has been marked as suitable for new contributors. 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 : /good-first-issue </details
/assign
/assign
To : has already assigned himself/herself, and posted a PR ().
Change:
and bare metal workloads. * [Flannel](https://github.com/flannel-io/flannel#deploying-flannel-manually) is an overlay network provider that can be used with Kubernetes. <ins> * [Gateway API](/docs/concepts/services-networking/gateway/) is an open source project managed by the [SIG Network](https://github.com/kubernetes/community/tree/master/sig-network) community and provides an expressive, extensible, and role-oriented API for modeling service networking. </ins> * [Knitter](https://github.com/ZTE/Knitter/) is a plugin to support multiple network interfaces in a Kubernetes pod. * [Multus](https://github.com/k8snetworkplumbingwg/multus-cni) is a Multi plugin for

Discussion:
This is a Feature Request What would you like to be High level documentation for Gateway API with links out to https://gateway- This should include the following: new "Gateway API" page between Service and Ingress in This should provide a high level overview of Gateway API, with a focus on content that is unlikely to become stale. This can likely take some content from both https://gateway- and https://gateway- and would help increase the discoverability of Gateway API. the "Ingress" page to note that the API is effectively frozen and all new features are being to Gateway API (with a corresponding link to the page by 1). the section on the "Service" page that references Ingress and Gateway API to give more prominence to Gateway API. Why is this needed With the upcoming graduation of Gateway API to GA (x-ref ), it's past time to cover it in Kubernetes docs. Comments I'd previously talked with about this at a high level, but definitely let me know if you've got any suggestions for how we can scope/adjust this differently. /sig network /assign
checkout the gateway API in the section and look out for the bugs
/triage accepted /priority important-longterm
How about adding a short link eg that redirects (302) to https://gateway- ?
I'd put Service, Ingress, then Gateway - and leave it in that order until most new clusters include Gateway as an add-on.
Also see
Change:
1. Laden Sie die neueste Version herunter: ``` <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/darwin/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/$(curl -LS https://dl.k8s.io/release/stable.txt)/bin/darwin/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 macOS herunterzuladen, verwenden Sie den folgenden Befehl: ``` <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/{{< param "fullversion" >}}/bin/darwin/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/darwin/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:
`Failed`    | Pod内のすべてのコンテナが終了し、少なくとも1つのコンテナが異常終了しました。つまり、コンテナはゼロ以外のステータスで終了したか、システムによって終了されました。 `Unknown`   | 何らかの理由によりPodの状態を取得できませんでした。このフェーズは通常はPodのホストとの通信エラーにより発生します。 <ins> {{< note >}} Podの削除中に、kubectlコマンドには`Terminating`が出力されることがあります。この`Terminating`ステータスは、Podのフェーズではありません。Podには、正常に終了するための期間を与えられており、デフォルトは30秒です。`--force`フラグを使用して、[Podを強制的に削除する](/ja/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination-forced)ことができます。 {{< /note >}} </ins> Nodeが停止するか、クラスタの残りの部分から切断された場合、Kubernetesは失われたNode上のすべてのPodの`Phase`をFailedに設定するためのポリシーを適用します。 ## コンテナのステータス {#container-states}

Discussion:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/workloads/pods/pod- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/workloads/pods/pod- is outdated. For example, there is no description of PodHasNetwork(alpha feature). Comments /language ja /assign
/triage accepted
Change:
<div class="layout" id="top"> <del> <main class="content katacoda-content"> <div class="katacoda"> <div class="katacoda__alert"> Esta tela é muito estreita para interagir com o Terminal, use um desktop / tablet. </div> <div class="katacoda__box" id="inline-terminal-1"  data-katacoda-id="kubernetes-bootcamp/1" 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="/pt/docs/tutorials/kubernetes-basics/deploy-app/deploy-intro/" role="button">Continue para o Módulo 2<span class="btn__next">›</span></a> </div> </div> </del> <ins> <main class="content"> <div> <h2 class="katacoda-gone"> Conteúdo indisponível </h2> <p> O tutorial interativo de como criar um 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> </div>

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:
<ins> --- title: フィーチャーゲート(Feature gate) id: feature-gate date: 2023-01-12 full_link: /ja/docs/reference/command-line-tools-reference/feature-gates/ short_description: > 特定のKubernetes機能を有効にするかどうかを制御する方法。 aka: tags: - fundamental - operation --- フィーチャーゲートはクラスター内でどのKubernetes機能を有効にするかを制御するために使用できるキー(不透明な文字列値)のセットです。 <!--more--> 各Kubernetesコンポーネントで`--feature-gates`コマンドラインフラグを使用して、これらの機能をオンまたはオフにすることができます。 各Kubernetesコンポーネントでは、そのコンポーネントに関連する一連のフィーチャーゲートを有効または無効にすることができます。 Kubernetesのドキュメントには、現在のすべての[フィーチャーゲート](/ja/docs/reference/command-line-tools-reference/feature-gates/)とその制御対象がリストされています。 </ins>

Discussion:
Note that this issue is for Japanese Speaker This is a Feature Request What would you like to be Translate into Japanese Why is this needed There is no Japanese translation for this page Comments File to translate: Original: Japanese Localization document: /area localization /language ja /good-first-issue
This request has been marked as suitable for new contributors. 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 : Note that this issue is for Japanese Speaker Original: /language ja /good-first-issue 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
/assign
san, can you please review the PR
Change:
message: | 4 days of incredible opportunities to collaborate, learn + share with the entire community!<br /> April 18 - April 21, 2023. - name: Redirecting k8s.gcr.io - After startTime: 2023-03-27T00:00:00 # This should run after the redirect begins endTime: 2023-05-31T00:00:00

Discussion:
This is a Feature Request What would you like to be Set a banner to announce KubeCon 2023 NA Why is this needed We usually turn on a banner for the upcoming KubeCon, and we're about ~3 weeks out. Logos are available from: (make sure to copy the logo into this repo) should help with text Also see the config for a previous year's NA KubeCon. Comments This change will need steering committee approval. I would set the banner to start on the Oct 20, 2023 and to end on the November 9, 2023 at 1800 CEST. /priority important-soon
/triage accepted
Banner is smaller than the usual size
Change:
## `coredns` (or `kube-dns`) is stuck in the `Pending` state This is **expected** and part of the design. kubeadm is network provider-agnostic, so the admin <del> should [install the pod network solution](/docs/concepts/cluster-administration/addons/) </del> <ins> should [install the pod network add-on](/docs/concepts/cluster-administration/addons/) </ins> of choice. You have to install a Pod Network before CoreDNS may be deployed fully. Hence the `Pending` state before the network is set up. ## `HostPort` services do not work The `HostPort` and `HostIP` functionality is available depending on your Pod Network <del> provider. Please contact the author of the Pod Network solution to find out whether </del> <ins> provider. Please contact the author of the Pod Network add-on to find out whether </ins> `HostPort` and `HostIP` functionality are available. Calico, Canal, and Flannel CNI providers are verified to support HostPort.

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 words should be unified in and . For the sake of clarity, the same words should be used for things that have the same meaning. Proposed Solution: We should use either the terms "network solution" or "network add-on". Page to Update: Troubleshooting kubeadm: Installing Addons: <!--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
modifying the kubeadm troubleshooting page to use "addon" instead of "solution" seems fine to me. PRs welcome! /help /sig cluster-lifecycle /kind cleanup /priority backlog
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : modifying the kubeadm troubleshooting page to use "addon" instead of "solution" seems fine to me. PRs welcome! /sig cluster-lifecycle /kind cleanup /priority backlog </details
/assign
/assign
Change:
The kubelet acts as a client when connecting to the container runtime via gRPC. The runtime and image service endpoints have to be available in the container runtime, which can be configured separately within the kubelet by using the <del> `--image-service-endpoint` and `--container-runtime-endpoint` [command line flags](/docs/reference/command-line-tools-reference/kubelet) </del> <ins> `--image-service-endpoint` [command line flags](/docs/reference/command-line-tools-reference/kubelet). </ins> For Kubernetes v{{< skew currentVersion >}}, the kubelet prefers to use CRI `v1`. If a container runtime does not support `v1` of the CRI, then the kubelet tries to

Discussion:
Documentation for external etcd cluster for kubernetes 1.27 is not up to date That the documentation doesn't take into consideration the fact that was removed in version 1.27 of kubelet: Restart=always Just try to install kubernetes with an external etcd cluster (which right now doesn't work anyway also for other reasons related to this ) with version 1.27.2 and you'll get: No response <details27.2 </details<detailsself-hosted </details<details</details<detailskubeadm </details<detailscontainerd </details<detailscalico </details
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands: - Please see the for a listing of the SIGs, working groups, and committees available. <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
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. 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
/transfer website /assign
removed the comment in v1.27. is not re-generated. I opened to fix it.
/retitle flag still in the documentation for external etcd in version 1.27 despite removal /language en /triage accepted
Change:
- ianychoi - seokho-son - ysyukr <del> sig-docs-maintainers: # Website maintainers </del> <ins> sig-docs-leads: # Website chairs and tech leads </ins> - jimangel - kbarnard10 <del> - pwittrock - steveperry-53 </del> <ins> - kbhawkey - onlydole - sftim </ins> - zacharysarah <del> - zparnold </del> sig-docs-zh-owners: # Admins for Chinese content - chenopis - chenrui333

Discussion:
The  group in OWNERSALIASES is a historical artifact with no permissions associated with it. Remove the team from OWNERS_ALIASES. I'm also proposing to update the description of from "Website admins" to "Website chairs and tech leads" and add and to the group. For more information, see We need to update the to replace with I propose continuing to limit repo admin access to current chairs. /assign
Change:
Để tải về phiên bản cụ thể, hãy thay thế phần `$(curl -LS https://dl.k8s.io/release/stable.txt)` trong câu lệnh với một phiên bản cụ thể. <del> Ví dụ như, để tải về phiên bản {{< param "fullversion" >}} trên Linux, hãy nhập như sau: </del> <ins> Ví dụ như, để tải về phiên bản {{< skew currentPatchVersion >}} trên Linux, hãy nhập như sau: </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. Tạo kubectl binary thực thi.

Discussion:
Problem: Based on , I have created this issue/task to help update the [vi] language documentation. Proposed Solution: Page to Update: In the branch, I found: Results for "fullversion" in "k8s-website/content/vi" /home/rdlugyhe/kubernetes/k8s-website/content/vi/docs/tasks/tools/install- 36: Ví dụ như, để tải về phiên bản {{< param "fullversion" }} trên Linux, hãy nhập như sau: 39: curl -LO {{< param "fullversion" }}/bin/linux/amd64/kubectl 111: Ví dụ, để tải về phiên bản {{< param "fullversion" }} trên macOS, gõ: 114: curl -LO {{< param "fullversion" }}/bin/darwin/amd64/kubectl 176: 1. Tải về phiên bản mới nhất {{< param "fullversion" }} từ đường dẫn nàyg