jiebi/CodeConvo huggingface dataset:
Change:
The legacy Linux package repositories (`apt.kubernetes.io` and `yum.kubernetes.io`)<br/> have been frozen starting from September 13, 2023.<br/> Please read our [announcement](/blog/2023/08/31/legacy-package-repository-deprecation/) for more details. <ins> - name: Kubecon 2023 NA startTime: 2023-10-20T00:00:00  #Added in https://github.com/kubernetes/website/pull/43565 endTime: 2023-11-09T18:00:00 style: >- background: linear-gradient(90deg, rgba(55,38,93,1) 0%, rgba(85,53,125,1) 65%, rgba(33,70,139,1) 100%); color: #fffff; title: | <img src ="/images/announcements/kccnc-na-2023-white.svg" style="float: right; height: 80px;" /> <a href= "https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/">KubeCon + CloudNativeCon NA 2023</a> <em> Chicago, Illinois + Virtual</em>. message: | 4 days of incredible opportunities to collaborate, learn + share with the entire community!<br /> November 6 - November 9, 2023. </ins>

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:
## Downloads for v1.21.0 <ins> ### Source Code </ins> filename | sha512 hash -------- | ----------- [kubernetes.tar.gz](https://dl.k8s.io/v1.21.0/kubernetes.tar.gz) | `19bb76a3fa5ce4b9f043b2a3a77c32365ab1fcb902d8dd6678427fb8be8f49f64a5a03dc46aaef9c7dadee05501cf83412eda46f0edacbb8fc1ed0bf5fb79142`

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 exist bugs in . [Part number 1] [Part number 2] Proposed Solution: [Part number 1] [Part number 2] 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
[As-is] [To-be]
Hello . Note: The release notes are auto-generated. What do you think about logging an issue with the release team (release notes)?
Hi Following your advice, I posted an on . Thank you!
release notes team here. yes this was autogenerated but we had to make manual fix to k/k (ref: ) a few days after the official release went out. i think it's the right move to fix it here as well
Change:
設定が異なるノードをサポートするには、[スケジューリング](#scheduling)を参照してください。 {{< /note >}} <del> RuntimeClassの設定は、RuntimeClassによって参照される`ハンドラー`名を持ちます。そのハンドラーは正式なDNS-1123に準拠する形式のラベルでなくてはなりません(英数字 + `-`の文字で構成されます)。 </del> <ins> RuntimeClassの設定は、RuntimeClassによって参照される`ハンドラー`名を持ちます。そのハンドラーは有効な[DNSラベル名](/ja/docs/concepts/overview/working-with-objects/names/#dns-label-names)でなくてはなりません。 </ins> ### 2. 対応するRuntimeClassリソースを作成する

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:
`*`, `=`, and `!` in your strings. If you don't, your shell will interpret these characters. <ins> {{< note >}} The `stringData` field for a Secret does not work well with server-side apply. {{< /note >}} </ins> ### Use source files 1. Store the credentials in files:

Discussion:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Update the docs for server-side apply to mention that for a does not work well with - Update the docs for Secrets to mention that for a does not work well with Why is this needed etc Comments /language en /kind feature /triage accepted /priority backlog
See for more detail:
/assign I would raise a PR for fixing this issue.
This is only partially resolved by ...
Hi, , What do you mean "partially resolved"? I checked the list and only found 2 references, which have been fixed by Or anything else I missed?
I don't think we have address all cases. Am I missing anything?
Thanks . I am afraid that you are right. I will open another PR for fixing the other 2 links with hints.
Change:
<ins> --- title: Docker id: docker date: 2018-04-12 full_link: https://docs.docker.com/engine/ short_description: > Dockerは、コンテナとして知られる、オペレーティングシステムレベルでの仮想化を提供するソフトウェア技術です。 aka: tags: - fundamental --- Docker(正確にはDocker Engine)は、{{< glossary_tooltip text="コンテナ" term_id="container" >}}としても知られる、オペレーティングシステムレベルでの仮想化を提供するソフトウェア技術です。 <!--more--> Dockerは、cgroupsやカーネル名前空間などのLinuxカーネルのリソースの隔離機能、OverlayFSなどの統合能力のあるファイルシステム、独立したコンテナを単一のLinuxインスタンス内で実行可能にするその他の機能などを利用して、マシンレベルでの仮想マシン(VM)の起動にかかるオーバーヘッドを回避します。 </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
Change:
<del> <!-- </del> <ins> --- </ins> layout: blog <del> title: "Kubernetes on MIPS" </del> <ins> title: "基于 MIPS 架构的 Kubernetes 方案" </ins> date: 2020-01-15 slug: Kubernetes-on-MIPS <del> --> </del> --- <ins> <!-- </ins> layout: blog <del> title: "基于 MIPS 架构的 Kubernetes 方案" </del> <ins> title: "Kubernetes on MIPS" </ins> date: 2020-01-15 slug: Kubernetes-on-MIPS <del> --- </del> <ins> --> </ins> <!-- **Authors:** TimYin Shi, Dominic Yin, Wang Zhan, Jessica Jiang, Will Cai, Jeffrey Gao, Simon Sun (Inspur)

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: Blog " MIPS Kubernetes " format error. Proposed Solution: Update blog format. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language zh
Change:
- Evicting all the pods from the node using graceful termination if the node continues to be unreachable. The default timeouts are 40s to start reporting ConditionUnknown and 5m after that to start evicting pods. The node controller checks the state of each node every `--node-monitor-period` seconds. #### Heartbeats

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: As-is: is rendered like this: ! Proposed Solution: Add a separating blank line. To-be: Page to Update: /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:
app.kubernetes.io/version: "5.7.21" app.kubernetes.io/component: database app.kubernetes.io/part-of: wordpress <del> app.kubernetes.io/managed-by: helm </del> <ins> app.kubernetes.io/managed-by: Helm </ins> ``` ## Applications And Instances Of Applications

Discussion:
There is a suggested annotation of: But Helm actually : Which will insert a value of "Helm", with a first character in uppercase. According to , labels are case-sensitive, except for the prefix. (You can notice this discrepancy if you are using the plug-in, as your chart with a lower-case word will always be replaced with upper-case, so a three-way-merge diff shows this as changing every time. I also imagine you could find this if you tried to use the label as a selector) Therefore I recommend that the suggested annotation in this document be replaced with: Caveat: I have no idea if the case changed between helm v2 and v3, but v2 is defunct now, so should be safe to make this change.
This is just an example of what could go in, but I think it might be a good first issue. If you want to work on this, assign yourself to this issue. Update all instances of to , including in the table. You should be able to complete this in GitHub without needing to work on a local clone. For instructions, read .
/language en
Let me help with this. /assign
/triage accepted /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 : /triage accepted /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
Change:
<center> <h2>Get Kubernetes Certified</h2> </center> <del> <div class="col-nav"> <center> <h5> <b>Certified Kubernetes Application Developer (CKAD)</b> </h5> <p>The Certified Kubernetes Application Developer exam certifies that users can design, build, configure, and expose cloud native applications for Kubernetes.</p> <br> <a href="https://training.linuxfoundation.org/certification/certified-kubernetes-application-developer-ckad/" target="_blank" class="button">Go to Certification</a> </center> </div> <div class="col-nav"> <center> <h5> <b>Certified Kubernetes Administrator (CKA)</b> </h5> <p>The Certified Kubernetes Administrator (CKA) program provides assurance that CKAs have the skills, knowledge, and competency to perform the responsibilities of Kubernetes administrators.</p> <br> <a href="https://training.linuxfoundation.org/certification/certified-kubernetes-administrator-cka/" target="_blank" class="button">Go to Certification</a> </center> </del> <ins> <div class="col-container"> <div class="col-nav"> <center> <h5> <b>Certified Kubernetes Application Developer (CKAD)</b> </h5> <p>The Certified Kubernetes Application Developer exam certifies that users can design, build, configure, and expose cloud native applications for Kubernetes.</p> <br> <a href="https://training.linuxfoundation.org/certification/certified-kubernetes-application-developer-ckad/" target="_blank" class="button">Go to Certification</a> </center> </div> <div class="col-nav"> <center> <h5> <b>Certified Kubernetes Administrator (CKA)</b> </h5> <p>The Certified Kubernetes Administrator (CKA) program provides assurance that CKAs have the skills, knowledge, and competency to perform the responsibilities of Kubernetes administrators.</p> <br> <a href=https://training.linuxfoundation.org/certification/certified-kubernetes-administrator-cka/" target="_blank" class="button">Go to Certification</a> </center> </div> </ins> </div> </div> </section>

Discussion:
This is feedback by email from within the CNCF/Linux Foundation: add the CKA/CKAD logos from to the page.
I'll take care of this, so assign it to me :)
/assign
Change:
RELEASE="$(curl -sSL https://dl.k8s.io/release/stable.txt)" ARCH="amd64" cd $DOWNLOAD_DIR <del> sudo curl -L --remote-name-all https://storage.googleapis.com/kubernetes-release/release/${RELEASE}/bin/linux/${ARCH}/{kubeadm,kubelet,kubectl} </del> <ins> sudo curl -L --remote-name-all https://dl.k8s.io/release/${RELEASE}/bin/linux/${ARCH}/{kubeadm,kubelet,kubectl} </ins> sudo chmod +x {kubeadm,kubelet,kubectl} curl -sSL "https://raw.githubusercontent.com/kubernetes/release/${RELEASE_VERSION}/cmd/kubepkg/templates/latest/deb/kubelet/lib/systemd/system/kubelet.service" | sed "s:/usr/bin:${DOWNLOAD_DIR}:g" | sudo tee /etc/systemd/system/kubelet.service

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: 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:
hostname used by kube-apisever by checking the value of the `kubernetes.io/hostname` label: ```shell <del> kubectl -n kube-system get lease kube-apiserver-c4vwjftbvpc5os2vvzle4qg27a -o yaml </del> <ins> kubectl -n kube-system get lease apiserver-07a5ea9b9b072c4a5f3d1c3702 -o yaml </ins> ``` ```yaml apiVersion: coordination.k8s.io/v1 kind: Lease metadata: <del> creationTimestamp: "2022-11-30T15:37:15Z" </del> <ins> creationTimestamp: "2023-07-02T13:16:48Z" </ins> labels: <del> k8s.io/component: kube-apiserver kubernetes.io/hostname: kind-control-plane name: kube-apiserver-c4vwjftbvpc5os2vvzle4qg27a </del> <ins> apiserver.kubernetes.io/identity: kube-apiserver kubernetes.io/hostname: master-1 name: apiserver-07a5ea9b9b072c4a5f3d1c3702 </ins> namespace: kube-system <del> resourceVersion: "18171" uid: d6c68901-4ec5-4385-b1ef-2d783738da6c </del> <ins> resourceVersion: "334899" uid: 90870ab5-1ba9-4523-b215-e4d4e662acb1 </ins> spec: <del> holderIdentity: kube-apiserver-c4vwjftbvpc5os2vvzle4qg27a_9cbf54e5-1136-44bd-8f9a-1dcd15c346b4 </del> <ins> holderIdentity: apiserver-07a5ea9b9b072c4a5f3d1c3702_0c8914f7-0f35-440e-8676-7844977d3a05 </ins> leaseDurationSeconds: 3600 <del> renewTime: "2022-11-30T18:04:27.912073Z" </del> <ins> renewTime: "2023-07-04T21:58:48.065888Z" </ins> ``` Expired leases from kube-apiservers that no longer exist are garbage collected by new kube-apiservers after 1 hour.

Discussion:
The command showed nothing. But this command worked. It looks like the labels have been changed and now the example is different from the real state of version 1.27.3.
Page related to issue: /language en
/retitle Incorrect label in kubectl command for inspecting Leases for kube-apiserver
Judging from the k8s upstream code, this label has indeed been changed and the documentation needs to be updated. /cc for confirm
/sig apps
/assign
/sig api-machinery
/triage accepted
/assign
Change:
- A user who can create a Pod that uses a secret can also see the value of that secret. Even if the API server policy does not allow that user to read the Secret, the user could run a Pod which exposes the secret. <del> - Currently, anyone with root permission on any node can read _any_ secret from the API server, by impersonating the kubelet. It is a planned feature to only send secrets to nodes that actually require them, to restrict the impact of a root exploit on a single node. </del> ## {{% heading "whatsnext" %}}

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: section () contains an outdated claim ( in 2016 in commit ) that compromise of a node/kubelet gives an attacker access to all secrets in the cluster. Specifically: My understanding is that modern clusters by default are configured to provide node/kubelet access only to secrets for Pods scheduled on that node/kubelet. . Tested on Amazon EKS 1.15. Proposed Solution: Edit to either entirely remove the above quote, or, if the security improvement is not enabled by default, provide information about how to enable it. Page to Update:
/kind bug /priority important-longterm Working on this also addresses from the style guide.
/language en
Thanks for reporting this
The outdated statement appears to be there in as well. I suspect it might be there in more languages.
That's OK - the localization teams have their own processes for picking up changes that are fixed in the upstream English localization.
/assign
I notice also that says: (my emphasis)
/sig auth
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
Anyone who'd like to, please feel free to open a pull request with an update.
/kind documentation
/sig security
/triage accepted
Change:
persist data. Volume management components are shipped as Kubernetes volume <del> [plugin](/docs/concepts/storage/volumes/#types-of-volumes). </del> <ins> [plugin](/docs/concepts/storage/volumes/#volume-types). </ins> The following broad classes of Kubernetes volume plugins are supported on Windows: * [`FlexVolume plugins`](/docs/concepts/storage/volumes/#flexvolume)

Discussion:
This is a Bug Report Problem: The link for under the in is wrong. It is redirected to the instead of that it should redirect to the Proposed Solution: Kubernetes volume plugin should redirect to the instead to the Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/sig docs /sig storage
I would like to work on it /assign /language en
/triage accepted
This issue is resolved here
Change:
{{< note >}} Pod内のすべてのコンテナが同時にTERMシグナルを受信するわけではなく、シャットダウンの順序が問題になる場合はそれぞれに`preStop`フックを使用して同期することを検討する。 {{< /note >}} <del> 1. kubeletが正常な終了を開始すると同時に、コントロールプレーンは、終了中のPodをEndpoints(および有効な場合はEndpointSlice)オブジェクトから削除します。これらのオブジェクトは、{{< glossary_tooltip text="selector" term_id="selector" >}}が設定された{{< glossary_tooltip term_id="service" text="Service" >}}を表します。{{< glossary_tooltip text="ReplicaSets" term_id="replica-set" >}}とその他のワークロードリソースは、終了中のPodを有効なサービス中のReplicaSetとして扱いません。ゆっくりと終了するPodは、(サービスプロキシーのような)ロードバランサーが終了猶予期間が_始まる_とエンドポイントからそれらのPodを削除するので、トラフィックを継続して処理できません。 </del> <ins> 1. kubeletが正常な終了を開始すると同時に、コントロールプレーンは、終了中のPodをEndpointSlice(およびEndpoints)オブジェクトから削除します。これらのオブジェクトは、{{< glossary_tooltip text="selector" term_id="selector" >}}が設定された{{< glossary_tooltip term_id="service" text="Service" >}}を表します。{{< glossary_tooltip text="ReplicaSets" term_id="replica-set" >}}とその他のワークロードリソースは、終了中のPodを有効なサービス中のReplicaSetとして扱いません。ゆっくりと終了するPodは、(サービスプロキシーのような)ロードバランサーが終了猶予期間が*始まる*とエンドポイントからそれらのPodを削除するので、トラフィックを継続して処理できません。 </ins> 1. 猶予期間が終了すると、kubeletは強制削除を開始する。コンテナランタイムは、Pod内でまだ実行中のプロセスに`SIGKILL`を送信する。kubeletは、コンテナランタイムが非表示の`pause`コンテナを使用している場合、そのコンテナをクリーンアップします。 1. kubeletは猶予期間を0(即時削除)に設定することでAPI server上のPodの削除を終了する。 1. API serverはPodのAPIオブジェクトを削除し、クライアントからは見えなくなります。

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:
- Learn about [page content types](/docs/contribute/style/page-content-types/) and [Hugo shortcodes](/docs/contribute/style/hugo-shortcodes/). --> <del> ## 第一次贡献 </del> <ins> ## 第一次贡献 {#your-first-contribution} </ins> - 通读[贡献概述](/zh/docs/contribute/new-content/overview/)，了解参与贡献的不同方式。 - 查看[`kubernetes/website` 问题列表](https://github.com/kubernetes/website/issues/) ，检索最适合作为切入点的问题。 - 在现有文档上， <del> [使用 GitHub 提交变更 (PR)](/zh/docs/contribute/new-content/open-a-pr/#changes-using-github)， </del> <ins> [使用 GitHub 提交 PR ](/zh/docs/contribute/new-content/open-a-pr/#changes-using-github)， </ins> 掌握在 GitHub 上登记 Issue 的方法。 <del> - Kubernetes 社区其他成员会[评审拉取请求 (PR)](/zh/docs/contribute/review/reviewing-prs/)， </del> <ins> - Kubernetes 社区其他成员会[评审 PR ](/zh/docs/contribute/review/reviewing-prs/)， </ins> 以确保文档精准和语言流畅。 - 阅读 kubernetes 的[内容指南](/zh/docs/contribute/style/content-guide/)和 <del> [风格指南](/docs/contribute/style/style-guide/) ，以发表有见地的评论。 </del> <ins> [风格指南](/zh/docs/contribute/style/style-guide/)，以发表有见地的评论。 </ins> - 了解[页面内容类型](/zh/docs/contribute/style/page-content-types/)和 [Hugo 短代码](/zh/docs/contribute/style/hugo-shortcodes/)。

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: Chinese page is different with English version page. Proposed Solution: Update Chinese page Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language zh /assign
thanks reviews and approvement from xichengliudui, tengqm and idealhack
Change:
## {{% heading "whatsnext" %}} <del> [크론 표현 포맷](https://pkg.go.dev/github.com/robfig/cron?tab=doc#hdr-CRON_Expression_Format)은 </del> <ins> [크론 표현 포맷](https://ko.wikipedia.org/wiki/Cron)은 </ins> 크론잡 `schedule` 필드의 포맷을 문서화 한다. 크론 잡 생성과 작업에 대한 지침과 크론잡 매니페스트의

Discussion:
Problem: The 5 fields of the cronJob schedule format are not described on the page - there is only a link to some external documetation (). This documentation however is for a 6 field format which include an extra seconds field at the start. Also the use of in the examples isn't required because `` already means every minute. Proposed Solution: Linking to a page which describes the 5 field version of the cron format e.g. the Wikipedia page: Page to Update:
/kind bug /priority important-longterm /language en