Question: - title: Nodejs + Mongo path: https://github.com/kubernetes/kubernetes/tree/release-1.2/examples/nodesjs-mongodb - title: Petstore <del> path: https://github.com/kubernetes/kubernetes/tree/release-1.2/examples/k8spetstore/ </del> <ins> path: https://github.com/kubernetes/kubernetes/tree/release-1.2/examples/k8petstore/ </ins>

I wish /docs/samples/ didn't have a broken Petstore link
For the record, the broken link in question is located here: The actual link should be to . At least, that's what it is in the project. Not sure which one we should change ( makes more sense to me).


Question: <ins> --- layout: blog title: Docsy 带来更好的 Docs UX date: 2020-06-15 slug: better-docs-ux-with-docsy url: /zh-cn/blog/2020/06/better-docs-ux-with-docsy --- <!-- layout: blog title: A Better Docs UX With Docsy date: 2020-06-15 slug: better-docs-ux-with-docsy url: /blog/2020/06/better-docs-ux-with-docsy --> <!-- **Author:** Zach Corleissen, Cloud Native Computing Foundation --> **作者：** Zach Corleissen，Cloud Native Computing Foundation <!-- *Editor's note: Zach is one of the chairs for the Kubernetes documentation special interest group (SIG Docs).* --> **编者注：Zach 是 Kubernetes 文档特别兴趣小组（SIG Docs）的主席之一。** <!-- I'm pleased to announce that the [Kubernetes website](https://kubernetes.io) now features the [Docsy Hugo theme](https://docsy.dev). --> 我很高兴地宣布 [Kubernetes 网站](https://kubernetes.io)现在采用了 [Docsy Hugo 主题](https://docsy.dev)。 <!-- The Docsy theme improves the site's organization and navigability, and opens a path to improved API references. After over 4 years with few meaningful UX improvements, Docsy implements some best practices for technical content. The theme makes the Kubernetes site easier to read and makes individual pages easier to navigate. It gives the site a much-needed facelift. --> Docsy 主题改进了网站的组织结构和导航性能，并开辟了改进 API 参考的途径。 在 4 年多的时间里，尽管对用户体验方面的改进不多，但 Docsy 针对技术内容实现了一些最佳实践。 该主题使 Kubernetes 网站更易于阅读，并使各个页面更易于导航。 它大大改进了网站所需的外在形象。 <!-- For example: adding a right-hand rail for navigating topics on the page. No more scrolling up to navigate! --> 例如：添加用于在页面上导航主题的右侧栏。无需再向上滚动导航！ <!-- The theme opens a path for future improvements to the website. The Docsy functionality I'm most excited about is the theme's [`swaggerui` shortcode](https://www.docsy.dev/docs/adding-content/shortcodes/#swaggerui), which provides native support for generating API references from an OpenAPI spec. The CNCF is partnering with [Google Season of Docs](https://developers.google.com/season-of-docs) (GSoD) for staffing to make better API references a reality in Q4 this year. We're hopeful to be chosen, and we're looking forward to Google's list of announced projects on August 16th. Better API references have been a personal goal since I first started working with SIG Docs in 2017. It's exciting to see the goal within reach. --> 该主题为网站的未来改进开辟了道路。 我最兴奋的 Docsy 功能是主题的 [`swaggerui` shortcode](https://www.docsy.dev/docs/adding-content/shortcodes/#swaggerui)， 它为从 OpenAPI 规范生成 API 引用提供了本地支持。 CNCF 正在与 [Google Season of Docs](https://developers.google.com/season-of-docs)（GSoD）合作，希望在今年第四季度实现更好的 API 参考。 我们很有希望被选中，我们期待着谷歌在 8 月 16 日公布的项目清单。 自从我 2017 年第一次开始使用 SIG Docs 以来，更好的 API 参考一直是我的个人目标。 看到这个目标触手可及，真是令人兴奋。 <!-- One of SIG Docs' tech leads, [Karen Bradshaw](https://github.com/kbhawkey) did a lot of heavy lifting to fix a wide range of site compatibility issues, including a fix to the last of our [legacy pieces](https://github.com/kubernetes/website/pull/21359) when we [migrated from Jekyll to Hugo](2018-05-05-hugo-migration/) in 2018. Our other tech leads, [Tim Bannister](https://github.com/sftim) and [Taylor Dolezal](https://github.com/onlydole) provided extensive reviews. --> 作为 SIG Docs 的技术负责人之一，[Karen Bradshaw](https://github.com/kbhawkey) 做了很多繁重的工作来解决广泛的网站兼容性问题， 包括在 2018 年我们从 [Jekyll 迁移到 Hugo](2018-05-05-hugo-migration/) 时修复的最后一个[遗留问题](https://github.com/kubernetes/website/pull/21359)。 我们的其他技术负责人，[Tim Bannister](https://github.com/sftim) 和 [Taylor Dolezal](https://github.com/onlydole) 提出过很多意见。 <!-- Thanks also to [Björn-Erik Pedersen](https://bep.is/), who provided invaluable advice about how to navigate a Hugo upgrade beyond [version 0.60.0](https://gohugo.io/news/0.60.0-relnotes/). --> 还要感谢 [Björn-Erik Pedersen](https://bep.is/)，他提供了关于如何在 [0.60.0 版本](https://gohugo.io/news/0.60.0-relnotes/)之后进行 Hugo 升级的宝贵建议。 <!-- The CNCF contracted with [Gearbox](https://gearboxbuilt.com/) in Victoria, BC to apply the theme to the site. Thanks to Aidan, Troy, and the rest of the team for all their work! --> CNCF 与不列颠哥伦比亚省维多利亚市的 [Gearbox](https://gearboxbuilt.com/) 签约，将主题应用于该网站。 感谢 Aidan、Troy 和团队其他成员的所有工作！ </ins>

Problem: do not have chinese docs: Proposed Solution: add chinese docs in website Comments /language zh /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


Question: 1. Create the Pod: <del> kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/pod-redis.yaml </del> <ins> kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/pod-redis.yaml </ins> 1. Verify that the Pod's Container is running, and then watch for changes to the Pod: <del> kubectl get --watch pod redis </del> <ins> kubectl get --watch pod redis </ins> The output looks like this: <del> NAME      READY     STATUS    RESTARTS   AGE redis     1/1       Running   0          13s </del> <ins> NAME      READY     STATUS    RESTARTS   AGE redis     1/1       Running   0          13s </ins> 1. In another terminal, get a shell to the running Container: <del> kubectl exec -it redis -- /bin/bash </del> <ins> kubectl exec -it redis -- /bin/bash </ins> 1. In your shell, go to `/data/redis`, and create a file: <del> root@redis:/data/redis# echo Hello > test-file </del> <ins> root@redis:/data/redis# echo Hello > test-file </ins> 1. In your shell, list the running processes: <del> root@redis:/data/redis# ps aux </del> <ins> root@redis:/data/redis# ps aux </ins> The output is similar to this: <del> USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND redis        1  0.1  0.1  33308  3828 ?        Ssl  00:46   0:00 redis-server *:6379 root        12  0.0  0.0  20228  3020 ?        Ss   00:47   0:00 /bin/bash root        15  0.0  0.0  17500  2072 ?        R+   00:48   0:00 ps aux </del> <ins> USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND redis        1  0.1  0.1  33308  3828 ?        Ssl  00:46   0:00 redis-server *:6379 root        12  0.0  0.0  20228  3020 ?        Ss   00:47   0:00 /bin/bash root        15  0.0  0.0  17500  2072 ?        R+   00:48   0:00 ps aux </ins> 1. In your shell, kill the redis process: <del> root@redis:/data/redis# kill <pid> </del> <ins> root@redis:/data/redis# kill <pid> </ins> where `<pid>` is the redis process ID (PID). 1. In your original terminal, watch for changes to the redis Pod. Eventually, you will see something like this: <del> NAME      READY     STATUS     RESTARTS   AGE redis     1/1       Running    0          13s redis     0/1       Completed  0         6m redis     1/1       Running    1         6m </del> <ins> NAME      READY     STATUS     RESTARTS   AGE redis     1/1       Running    0          13s redis     0/1       Completed  0         6m redis     1/1       Running    1         6m </ins> At this point, the Container has terminated and restarted. This is because the redis Pod has a

<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: This page has extra spaces before the commands: I am not sure it's a more systemic problem, but this causes commands to not to show up on the bash history (undesirable). Proposed Solution: Page to Update: /assign
A cursory look through the rest of the docs under Configure Pods and Containers showed that one out of four docs also had this issue. I'll make this change as I update the callouts.


Question: {{< tabs name="k8s_install" >}} {{% tab name="Debian-based distributions" %}} <del> ```bash sudo apt-get update && sudo apt-get install -y apt-transport-https curl curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add - cat <<EOF | sudo tee /etc/apt/sources.list.d/kubernetes.list deb https://apt.kubernetes.io/ kubernetes-xenial main EOF sudo apt-get update sudo apt-get install -y kubelet kubeadm kubectl sudo apt-mark hold kubelet kubeadm kubectl ``` </del> <ins> 1. Update the `apt` package index and install packages needed to use the Kubernetes `apt` repository: ```shell sudo apt-get update sudo apt-get install -y apt-transport-https ca-certificates curl ``` 2. Download the Google Cloud public signing key: ```shell sudo curl -fsSLo /usr/share/keyrings/kubernetes-archive-keyring.gpg https://packages.cloud.google.com/apt/doc/apt-key.gpg ``` 3. Add the Kubernetes `apt` repository: ```shell echo "deb [signed-by=/usr/share/keyrings/kubernetes-archive-keyring.gpg] https://apt.kubernetes.io/ kubernetes-xenial main" | sudo tee /etc/apt/sources.list.d/kubernetes.list ``` 4. Update `apt` package index, install kubelet, kubeadm and kubectl, and pin their version: ```shell sudo apt-get update sudo apt-get install -y kubelet kubeadm kubectl sudo apt-mark hold kubelet kubeadm kubectl ``` </ins> {{% /tab %}} {{% tab name="Red Hat-based distributions" %}} ```bash

The current installation instructions for installing the third party Kubernetes Apt repository on Debian/Ubuntu, goes against best security practice. Currently the signing keys are to . The keychain should be downloaded to (file name to match the name used in ) using or (not as this is deprecated and will be last available in Debian 11 and Ubuntu 22.04) and referred to in as such Page to Update: References:
i read the linked pages and this change seems valid. thank you for bringing this up. would you help us by sending a PR for that? /sig cluster-lifecycle
/priority important-longterm /kind cleanup
/triage accepted
Please see
/sig cli


Question: If the number of backend endpoints falls below 1000, the control plane removes this annotation. <ins> ### endpoints.kubernetes.io/last-change-trigger-time Type: Annotation Example: `endpoints.kubernetes.io/last-change-trigger-time: 2023-07-20T04:45:21Z` Used on: Endpoints This annotation set to an [Endpoints](/docs/concepts/services-networking/service/#endpoints) object that represents the timestamp (stored as RFC 3339 date-time string, e.g. '2018-10-22T19:32:52.1Z'). This is timestamp of the last change in some Pod or Service object, that triggered the endpoints object change. </ins> ### control-plane.alpha.kubernetes.io/leader (deprecated) {#control-plane-alpha-kubernetes-io-leader} Type: Annotation

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: Kubernetes sometimes sets an annotation, , on an Endpoints. However, this annotation is not documented in Proposed Solution: Document this annotation. If it's deprecated, note that (and set a custom fragment identifier). Page to Update: Additional Information: /sig network /language en
/assign
/triage accepted
Help on this issue is welcome.


Question: これらのリソースを管理するコントローラーに固有のオプションを設定することにより、リソースのガベージコレクションを調整できます。次のページは、ガベージコレクションを設定する方法を示しています。 <del> * [Kubernetesオブジェクトのカスケード削除の設定](/docs/tasks/administer-cluster/use-cascading-deletion/) </del> <ins> * [Kubernetesオブジェクトのカスケード削除の設定](/ja/docs/tasks/administer-cluster/use-cascading-deletion/) </ins> * [完了したジョブのクリーンアップの設定](/ja/docs/concepts/workloads/controllers/ttlafterfinished/) <!-- * [Configuring unused container and image garbage collection](/docs/tasks/administer-cluster/reconfigure-kubelet/) -->

This is a Feature Request What would you like to be Translate tasks/administer-cluster/use-cascading-deletion/ into Japanese. Why is this needed This page has not been translated. Comments /language ja /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


Question: value: "The Most Honorable" - name: NAME value: "Kubernetes" <ins> - name: MESSAGE value: "$(GREETING) $(HONORIFIC) $(NAME)" </ins> command: ["echo"] <del> args: ["$(GREETING) $(HONORIFIC) $(NAME)"] </del> <ins> args: ["$(MESSAGE)"] </ins> ``` Upon creation, the command `echo Warm greetings to The Most Honorable Kubernetes` is run on the container.

The "Using environment variables inside of your config" feature is great and has been very useful. Thanks! I have two minor suggestions: would also be useful to document which fields of a container spec this interpolation applies (or if it applies to almost all fields, what the exceptions are.) , the example is slightly confusing / misleading. The key feature that is documented here is the ability to statically use env vars defined in the config in other config fields. While the example is calling with a single string, it may look at a glance like a shell command which would do the interpolation itself (note notation and not or ). Perhaps a clearer example would be using env vars inside of other env vars: This shows more clearly that environment variable is configured statically from previously set environment variables - before the Pod is created, no shell interpolation involved.
/triage accepted /language en
/assign
As per my understanding, you are expecting here to add where this environment variable applies inside the configuration file like below. To set environment variables, include the env or envFrom field in the configuration file under .spec.containers[*]. Please confirm if i wrongly understood.
PR Raised here .