Question: # i18n strings for the English (main) site. # NOTE: Please keep the entries in alphabetical order when editing <ins> # Avoid using conjunction_1. # Must match the context in layouts/shortcodes/release-data.html # Appears on https://kubernetes.io/releases/ # For example the "and" in "Complete 1.25 Schedule and Changelog" [conjunction_1] other = "and" </ins> [caution] other = "Caution:"

When the following shortcode appears in a localized document... localized document displays English words such as: "Complete 1.24 and " Instances of the shortcode display English words in various localizations, such as: Is there a way to localize the languages these shortcodes display?
For instance, see
I have asked this question in the Hugo forum, here:
/assign
This is not a Hugo bug. is the file to localize.
partially fixes this issue. Each localization branch would need to merge PR and add corresponding entries to their files, such as: - -
Thanks, yes. I wasn't sure whom to ask, and generally try not to bother you with every question I have. The Hugo forum pointed us in the right direction, and quickly put together a PR solution.
Each localization branch would need to merge PR and add corresponding entries to their data/i18n/<lang/ files Once you PR merges, we should plan to add this topic to a localization meeting and post a message in the localization slack channel. We can also send an email, re post messages in slack for additional visibility. We should make sure the message includes all the steps needed o implement this and any urgency/priority around this change for the localization teams By a partial fix in your PR, do you mean that Localization teams will need to take additional steps to apply the changes to their localization, or are there additional file changes that need to be made?
Yes, exactly. Once this PR merges, I would do all the things you've suggested above or arrange with someone to do them. I'll create separate issues for each of the localization teams to update their branches as needed. This is not a breaking change, so there is no urgency.
I've tested to make sure this isn't a breaking change. If the file is missing the required entries, the page falls back and uses the entries from
/area localization
/triage accepted


Question: ### Migrating to the `systemd` driver in kubeadm managed clusters <del> Follow this [Migration guide](docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver) </del> <ins> Follow this [Migration guide](/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver) </ins> if you wish to migrate to the `systemd` cgroup driver in existing kubeadm managed clusters. ## Container runtimes

includes the deadlink:
/kind bug /triage accepted /language en
/sig cluster-lifecycle node i've LGTM on the pending PR.
/retitle container-runtime: migration guide points to a 404
this PR did not fix the problem: because it lacks a leading i will send a new one.
new fix is here:


Question: 该准入控制器为 Pod 设置默认的容忍度，在 5 分钟内容忍 `notready:NoExecute` 和 `unreachable:NoExecute` 污点。（如果 Pod 尚未容忍 `node.kubernetes.io/not-ready：NoExecute` 和 `node.alpha.kubernetes.io/unreachable：NoExecute` 污点的话） <del> ### DenyExecOnPrivileged {#denyexeconprivileged} {{< feature-state for_k8s_version="v1.13" state="deprecated" >}} </del> <ins> ### DenyExecOnPrivileged {#denyexeconprivileged} {{< feature-state for_k8s_version="v1.13" state="deprecated" >}} </ins> <!-- This admission controller will intercept all requests to exec a command in a pod if that pod has a privileged container.

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: Page /zh/docs/reference/access-authn-authz/admission-controllers/ display abnormally, these anchor points should start on a new line. Proposed Solution: fix the anchor point format. abnormal format: normal format: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign /language zh


Question:
Kubernetes Basics

This tutorial provides a walkthrough of the basics of the Kubernetes cluster orchestration system. Each module contains some background information on major Kubernetes features and concepts, and includes an interactive online tutorial. These interactive tutorials let you manage a simple cluster and its containerized applications for yourself.

Using the interactive tutorials, you can learn to:

This tutorial provides a walkthrough of the basics of the Kubernetes cluster orchestration system. Each module contains some background information on major Kubernetes features and concepts, and a tutorial for you to follow along.

Using the tutorials, you can learn to:

Deploy a containerized application on a cluster.

Scale the deployment.

In page , the first part describes that an online interative tutorial is included. But in fact, this tutorial was shutdown a few months ago. I think that may confuse some readers. !
/language en
Some replacement of words can fix this paragraph, but why katacoda/killercoda playgrounds are not used in these tutorial pages to make it interactive? /sig docs /kind feature
/assign
Seems like it's katacoda related.
Hi you don't need to translate anything. Just create a PR for english. (Optionally you can translate this if your know some other languages too. If you try to do so, raise a single PR per language.)
/assign
/kind bug /language en /remove-kind feature /triage accepted /priority important-longterm To discuss potential replacements for Katacoda (which has shut down), visit If anyone would like to support the Kubernetes project to set up or make use of a free replacement for Katacoda, you can: send financial to the Linux Foundation (very indirect support)
/assign


Question: visibility: visible; overflow: hidden; width: 1200px; <del> } </del> <ins> } </ins>  No newline at end of file

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


Question: * One or more machines running Ubuntu 16.04+, Debian 9, CentOS 7, RHEL 7, Fedora 25/26 (best-effort) or HypriotOS v1.0.1+ * 1GB or more of RAM per machine (any less will leave little room for your apps) * Full network connectivity between all machines in the cluster (public or private network is fine) <del> * Unique MAC address and product_uuid for every node </del> <ins> * Unique hostname, MAC address, and product_uuid for every node </ins> * Certain ports are open on your machines. See the section below for more details * Swap disabled. You must disable swap in order for the kubelet to work properly. * Set `/proc/sys/net/bridge/bridge-nf-call-iptables` to `1` by running `sysctl net.bridge.bridge-nf-call-iptables=1`

<!-- 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: kubectl get nodes seems to show the master is NotReady when a node is with the same hostname Proposed Solution: Make a unique hostname a requirement for every node just like MAC address and product_uuid. Possible the code should reflect that too. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--v1.8.1 <!--Additional Information:--
Thanks for the report If you think the code should be doing something different, please open a bug report for that code - either at , or in this case perhaps at I'll keep this report open to reflect the need in the documentation.


Question: An example NetworkPolicy might look like this: <del> ```yaml apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: test-network-policy namespace: default spec: podSelector: matchLabels: role: db policyTypes: - Ingress - Egress ingress: - from: - ipBlock: cidr: 172.17.0.0/16 except: - 172.17.1.0/24 - namespaceSelector: matchLabels: project: myproject - podSelector: matchLabels: role: frontend ports: - protocol: TCP port: 6379 egress: - to: - ipBlock: cidr: 10.0.0.0/24 ports: - protocol: TCP port: 5978 ``` </del> <ins> {{< codenew file="service/networking/networkpolicy.yaml" >}} </ins> {{< note >}} POSTing this to the API server for your cluster will have no effect unless your chosen networking solution supports network policy.

While working through the Killer Shell scenario for NetworkPolicies to prep for my CKA, I used the example but it failed validation. When I looked at their solution it had one tiny difference, they had a - in front of "ports:" and you guys didn't. Based on the reference docs it appears ports does expect an array which would mean that you are missing the hyphen. docs: solution from
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
The indentation of list items may be the source of confusion. Once you indent all list items under a given key, the parent element of the 'ports' attribute becomes more evident. The example on the website is correct. I'm not sure about the solution from If you put as the first key of a list item object, if will carry the bar for that list item, if is not the the first key, you will indent it rather than adding another before it. Anyway, I'm fixing the example in hope things become clearer for readers.


Question: ## Security Vulnerability Response <del> Each report is acknowledged and analyzed by Product Security Committee members within 3 working days. This will set off the [Security Release Process](https://git.k8s.io/security/security-release-process.md#disclosures). </del> <ins> Each report is acknowledged and analyzed by Security Response Committee members within 3 working days. This will set off the [Security Release Process](https://git.k8s.io/security/security-release-process.md#disclosures). </ins> <del> Any vulnerability information shared with Product Security Committee stays within Kubernetes project and will not be disseminated to other projects unless it is necessary to get the issue fixed. </del> <ins> Any vulnerability information shared with Security Response Committee stays within Kubernetes project and will not be disseminated to other projects unless it is necessary to get the issue fixed. </ins> As the security issue moves from triage, to identified fix, to release planning we will keep the reporter updated. ## Public Disclosure Timing <del> A public disclosure date is negotiated by the Kubernetes Product Security Committee and the bug submitter. We prefer to fully disclose the bug as soon as possible once a user mitigation is available. It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for vendor coordination. The timeframe for disclosure is from immediate (especially if it's already publicly known) to a few weeks. For a vulnerability with a straightforward mitigation, we expect report date to disclosure date to be on the order of 7 days. The Kubernetes Product Security Committee holds the final say when setting a disclosure date. </del> <ins> A public disclosure date is negotiated by the Kubernetes Security Response Committee and the bug submitter. We prefer to fully disclose the bug as soon as possible once a user mitigation is available. It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for vendor coordination. The timeframe for disclosure is from immediate (especially if it's already publicly known) to a few weeks. For a vulnerability with a straightforward mitigation, we expect report date to disclosure date to be on the order of 7 days. The Kubernetes Security Response Committee holds the final say when setting a disclosure date. </ins>

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 change We should find the term “product security committee” anywhere within the English-language docs, and replace that term with “security response committee”. We don't need to revise any blog articles. If we feel there are some blog articles where an exception is justified, I'd revise those in a separate PR per article as the review process is different. Why is this needed renamed the product security committee to “Security Response Committee” Comments /language en /sig docs /sig security /help /triage accepted Relevant to
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 : This is a Feature Request <!-- See for guidance on writing an actionable issue description. --We should find the term “product security committee” anywhere within the English-language docs, and replace that term with “security response committee”. We don't need to revise any blog articles. If we feel there are some blog articles where an exception is justified, I'd revise those in a separate PR per article as the review process is different. renamed the product security committee to “Security Response Committee” /language en /sig docs /sig security /help /triage accepted Relevant to 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
/priority backlog
thanks , PR's are incoming org wide for the change.
Hi, I would like to take this up /assign


Question: <ins> --- title: Serviceトポロジーを有効にする content_type: task --- <!-- overview --> このページでは、Kubernetes上でServiceトポロジーを有効にする方法の概要について説明します。 ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} <!-- steps --> ## はじめに *Serviceトポロジー*は、クラスターのノードのトポロジーに基づいてトラフィックをルーティングできるようにする機能です。たとえば、あるServiceのトラフィックに対して、できるだけ同じノードや同じアベイラビリティゾーン上にあるエンドポイントを優先してルーティングするように指定できます。 ## 前提 トポロジーを考慮したServiceのルーティングを有効にするには、以下の前提を満たしている必要があります。 * Kubernetesバージョン1.17以降である * {{< glossary_tooltip text="Kube-proxy" term_id="kube-proxy" >}}がiptableモードまたはIPVSモードで稼働している * [Endpoint Slice](/docs/concepts/services-networking/endpoint-slices/)を有効にしている ## Serviceトポロジーを有効にする {{< feature-state for_k8s_version="v1.17" state="alpha" >}} Serviceトポロジーを有効にするには、すべてのKubernetesコンポーネントで`ServiceTopology`と`EndpointSlice`フィーチャーゲートを有効にする必要があります。 ``` --feature-gates="ServiceTopology=true,EndpointSlice=true" ``` ## {{% heading "whatsnext" %}} * [Serviceトポロジー](/ja/docs/concepts/services-networking/service-topology)のコンセプトについて読む * [Endpoint Slice](/docs/concepts/services-networking/endpoint-slices)について読む * [サービスとアプリケーションの接続](/ja/docs/concepts/services-networking/connect-applications-service/)を読む </ins>

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


Question: <del> Subproject commit 0f9c38b8daae932518bee269de2768395d2a2dc2 </del> <ins> Subproject commit f6a1870918520c83872fc07943a67a1d9d2a998c </ins>

Look into evaluating how we can make building the site take less memory / cpu. As has grown, it went from a small hugo build to what it is today (a large, memory and file hungry build). This is all good though, it means we are adding content and localizations. Look into ways to reduce build time. A few options come to mind: Can we remove a large chunk of unused content? Can we build only a small subset of docs (easily and portable to the various localizations)? Are there any optimizations in hugo itself? There should be a way to reduce the amount of resources required to build . Considering there isn't a clear solution, I won't mark as good-first-issue. /sig docs /triage accepted
Idea: run the build localization-by-localization. I don't know if Hugo supports this but if it might let us run 14 shorter builds (potentially in parallel) rather than 1 long one. Idea: look for image resize options at build time. If reasonable to do so, replace the source image with what it gets resized to.
This might be an area where we could look for resources from CNCF to help with it - especially if the fix is applicable across multiple CNCF projects.


Question: <ins> --- title: रेप्लिकासेट (ReplicaSet) id: replica-set date: 2018-04-12 full_link: /docs/concepts/workloads/controllers/replicaset/ short_description: > रेप्लिकासेट यह सुनिश्चित करता है कि किसी एक अवसर पर निर्दिष्ट संख्या में पॉड प्रतिकृतियां चल रही हैं। aka: tags: - fundamental - core-object - workload --- एक रेप्लिकासेट (का उद्देश्य) किसी भी समय चल रहे रेप्लिका पॉड्स का एक समूह बनाए रखना है। <!--more--> वर्कलोड ऑब्जेक्ट्स, जैसे {{< glossary_tooltip text="डिप्लॉयमेंट" term_id="deployment" >}}, रेप्लिकासेट्स के विनिर्देश के आधार पर आपके क्लस्टर पर कॉन्फ़िगर की गई संख्या में {{< glossary_tooltip term_id="pod" text="पॉड्स" >}} चल रहे है ये सुनिश्चित करते हैं। </ins>

If this is your first contribution, visit for information on how to get started. Review a few to see which content you have to change and which you leave unchanged. Make sure your base, target branch is and create a working branch called . Create a file called content/hi/docs/reference/glossary/replica- Copy the content of to the file you created Localize the content. Push your change and create a pull request. Completing this feature issue fixes part of /language hi /triage accepted
/assign Thank you


Question:
Build your cloud native career

Kubernetes is at the core of the cloud native movement. Training and certifications from the Linux Foundation and our training partners lets you invest in your career, learn Kubernetes, and make your cloud native projects successful.

Build your cloud native career

Kubernetes is at the core of the cloud native movement. Training and certifications from the Linux Foundation and our training partners lets you invest in your career, learn Kubernetes, and make your cloud native projects successful.

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


Question: {{< kat-button >}} {{< note >}} <del> Se você instalou o Minikube localmente, execute: `minikube start`. </del> <ins> Se você instalou o Minikube localmente, execute: `minikube start`. Antes de executar `minikube dashboard`, abra um novo terminal, execute `minikube dashboard` nele, e retorne para o terminal anterior. </ins> {{< /note >}} 2. Abra o painel do Kubernetes em um navegador:

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. --Update the page Olá, Minikube (Brazilian Portuguese) to reflect the latest content in English. The Portuguese version of this page is a little bit outdated when compared to the English version. Page address: Content path in the repository: Why is this needed To keep the content in Brazilian Portuguese in sync with the English version. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/help /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 : This is a Feature Request <!-- See for guidance on writing an actionable issue description. --<!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Update the page Olá, Minikube (Brazilian Portuguese) to reflect the latest content in English. The Portuguese version of this page is a little bit outdated when compared to the English version. To keep the content in Brazilian Portuguese in sync with the English version. <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/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
/language pt-br Kindly provide the link to the page as well.

The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /language pt-br 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
/language pt
Hi there, Just the page address and the content path to the issue description.
/assign
I didn't understand this point.
If you are familiar with the localization language used here, I don't think you should have a doubt about understanding it. However, if you don't, we recommend folks only pick up those issues of the language they're comfortable with and use it often.
/assign


Question: <ins> --- layout: blog title: "Kubernetes 1.25：应用滚动上线所用的两个特性进入稳定阶段" date: 2022-09-15 slug: "app-rollout-features-reach-stable" --- <!-- layout: blog title: "Kubernetes 1.25: Two Features for Apps Rollouts Graduate to Stable" date: 2022-09-15 slug: "app-rollout-features-reach-stable" --> <!-- **Authors:** Ravi Gudimetla (Apple), Filip Křepinský (Red Hat), Maciej Szulik (Red Hat) --> **作者：** Ravi Gudimetla (Apple)、Filip Křepinský (Red Hat)、Maciej Szulik (Red Hat) <!-- This blog describes the two features namely `minReadySeconds` for StatefulSets and `maxSurge` for DaemonSets that SIG Apps is happy to graduate to stable in Kubernetes 1.25. Specifying `minReadySeconds` slows down a rollout of a StatefulSet, when using a `RollingUpdate` value in `.spec.updateStrategy` field, by waiting for each pod for a desired time. This time can be used for initializing the pod (e.g. warming up the cache) or as a delay before acknowledging the pod. --> 这篇博客描述了两个特性，即用于 StatefulSet 的 `minReadySeconds` 以及用于 DaemonSet 的 `maxSurge`， SIG Apps 很高兴宣布这两个特性在 Kubernetes 1.25 进入稳定阶段。 当 `.spec.updateStrategy` 字段设置为 `RollingUpdate` 时， 你可以设置 `minReadySeconds`， 通过让每个 Pod 等待一段预期时间来减缓 StatefulSet 的滚动上线。 <!-- `maxSurge` allows a DaemonSet workload to run multiple instances of the same pod on a node during a rollout when using a `RollingUpdate` value in `.spec.updateStrategy` field. This helps to minimize the downtime of the DaemonSet for consumers. These features were already available in a Deployment and other workloads. This graduation helps to align this functionality across the workloads. --> 当 `.spec.updateStrategy` 字段设置为 `RollingUpdate` 时， `maxSurge` 允许 DaemonSet 工作负载在滚动上线期间在一个节点上运行同一 Pod 的多个实例。 这对于消费者而言有助于将 DaemonSet 的停机时间降到最低。 这两个特性也可用于 Deployment 和其他工作负载。此功能的提级有助于将这一功能在所有工作负载上对齐。 <!-- ## What problems do these features solve? ### minReadySeconds for StatefulSets {#solved-problem-statefulset-minreadyseconds} --> ## 这两个特性能解决什么问题？   {#what-problems-do-these-features-solve} ### 针对 StatefulSet 的 minReadySeconds   {#solved-problem-statefulset-minreadyseconds} <!-- `minReadySeconds` ensures that the StatefulSet workload is `Ready` for the given number of seconds before reporting the pod as `Available`. The notion of being `Ready` and `Available` is quite important for workloads. For example, some workloads, like Prometheus with multiple instances of Alertmanager, should be considered `Available` only when the Alertmanager's state transfer is complete. `minReadySeconds` also helps when using loadbalancers with cloud providers. Since the pod should be `Ready` for the given number of seconds, it provides buffer time to prevent killing pods in rotation before new pods show up. --> `minReadySeconds` 确保 StatefulSet 工作负载在给定的秒数内处于 `Ready`， 然后才会将该 Pod 报告为 `Available`。 处于 `Ready` 和 `Available` 状况的这种说法对工作负载相当重要。 例如 Prometheus 这些工作负载有多个 Alertmanager 实例， 只有 Alertmanager 的状态转换完成后才应该被视为 `Available`。 `minReadySeconds` 还有助于云驱动确定何时使用负载均衡器。 因为 Pod 应在给定的秒数内处于 `Ready`，所以这就提供了一段缓冲时间， 防止新 Pod 还没起来之前就在轮转过程中杀死了旧 Pod。 <!-- ### maxSurge for DaemonSets {#how-use-daemonset-maxsurge} Kubernetes system-level components like CNI, CSI are typically run as DaemonSets. These components can have impact on the availability of the workloads if those DaemonSets go down momentarily during the upgrades. The feature allows DaemonSet pods to temporarily increase their number, thereby ensuring zero-downtime for the DaemonSets. Please note that the usage of `hostPort` in conjunction with `maxSurge` in DaemonSets is not allowed as DaemonSet pods are tied to a single node and two active pods cannot share the same port on the same node. --> ### 针对 DaemonSet 的 maxSurge     {#how-use-daemonset-maxsurge} CNI、CSI 这类 Kubernetes 系统级别的组件通常以 DaemonSet 方式运行。如果这些 DaemonSet 在升级期间瞬间挂掉， 对应的组件可能会影响工作负载的可用性。此特性允许 DaemonSet Pod 临时增加数量，以此确保 DaemonSet 的停机时间为零。 请注意在 DaemonSet 中不允许同时使用 `hostPort` 和 `maxSurge`， 因为 DaemonSet Pod 被捆绑到了一个节点，所以两个活跃的 Pod 无法共享同一节点上的相同端口。 <!-- ## How does it work? ### minReadySeconds for StatefulSets {#how-does-statefulset-minreadyseconds-work} The StatefulSet controller watches for the StatefulSet pods and counts how long a particular pod has been in the `Running` state, if this value is greater than or equal to the time specified in `.spec.minReadySeconds` field of the StatefulSet, the StatefulSet controller updates the `AvailableReplicas` field in the StatefulSet's status. --> ## 工作原理    {#how-does-it-work} ### 针对 StatefulSet 的 minReadySeconds  {#how-does-statefulset-minreadyseconds-work} StatefulSet 控制器监视 StatefulSet Pod 并统计特定的 Pod 已处于 `Running` 状态多长时间了， 如果这个值大于或等于 StatefulSet 的 `.spec.minReadySeconds` 字段中指定的时间， StatefulSet 控制器将更新 StatefulSet 的状态中的 `AvailableReplicas` 字段。 <!-- ### maxSurge for DaemonSets {#how-does-daemonset-maxsurge-work} The DaemonSet controller creates the additional pods (above the desired number resulting from DaemonSet spec) based on the value given in `.spec.strategy.rollingUpdate.maxSurge`. The additional pods would run on the same node where the old DaemonSet pod is running till the old pod gets killed. --> ### 针对 DaemonSet 的 maxSurge  {#how-does-daemonset-maxsurge-work} DaemonSet 控制器根据 `.spec.strategy.rollingUpdate.maxSurge` 中给出的值创建额外 Pod （超出 DaemonSet 规约所设定的预期数量）。 这些 Pod 将运行在旧 DaemonSet Pod 运行所在的同一节点上，直到这个旧 Pod 被杀死为止。 <!-- - The default value is 0. - The value cannot be `0` when `MaxUnavailable` is 0. - The value can be specified either as an absolute number of pods, or a percentage (rounded up) of desired pods. --> - 默认值为 0。 - 当 `MaxUnavailable` 为 0 时此值不能为 `0`。 - 此值可以指定为一个绝对的 Pod 个数或预期 Pod 总数的百分比（向上取整）。 <!-- ## How do I use it? ### minReadySeconds for StatefulSets {#how-use-statefulset-minreadyseconds} Specify a value for `minReadySeconds` for any StatefulSet and check if pods are available or not by inspecting `AvailableReplicas` field using: --> ## 我如何使用它？   {#how-do-i-use-it} ### 针对 StatefulSet 的 minReadySeconds   {#how-use-statefulset-minreadyseconds} 执行以下命令为任意 StatefulSet 指定一个 `minReadySeconds` 值， 通过检验 `AvailableReplicas` 字段查看这些 Pod 是否可用： ``` kubectl get statefulset/<StatefulSet 名称> -o yaml ``` <!-- Please note that the default value of `minReadySeconds` is 0. ### maxSurge for DaemonSets {#how-use-daemonset-maxsurge} Specify a value for `.spec.updateStrategy.rollingUpdate.maxSurge` and set `.spec.updateStrategy.rollingUpdate.maxUnavailable` to `0`. Then observe a faster rollout and higher number of pods running at the same time in the next rollout. --> 请注意 `minReadySeconds` 的默认值为 0。 ### 针对 DaemonSet 的 maxSurge  {#how-use-daemonset-maxsurge} 为 `.spec.updateStrategy.rollingUpdate.maxSurge` 指定一个值并将 `.spec.updateStrategy.rollingUpdate.maxUnavailable` 设置为 `0`。 然后观察下一次滚动上线是不是更快，同时运行的 Pod 数量是不是更多。 ``` kubectl rollout restart daemonset <name_of_the_daemonset> kubectl get pods -w ``` <!-- ## How can I learn more? ### minReadySeconds for StatefulSets {#learn-more-statefulset-minreadyseconds} - Documentation: https://k8s.io/docs/concepts/workloads/controllers/statefulset/#minimum-ready-seconds - KEP: https://github.com/kubernetes/enhancements/issues/2599 - API Changes: https://github.com/kubernetes/kubernetes/pull/100842 --> ## 我如何才能了解更多？   {#how-can-i-learn-more} ### 针对 StatefulSet 的 minReadySeconds   {#learn-more-statefulset-minreadyseconds} - 文档： https://k8s.io/zh-cn/docs/concepts/workloads/controllers/statefulset/#minimum-ready-seconds - KEP： https://github.com/kubernetes/enhancements/issues/2599 - API 变更： https://github.com/kubernetes/kubernetes/pull/100842 <!-- ### maxSurge for DaemonSets {#learn-more-daemonset-maxsurge} - Documentation: https://k8s.io/docs/tasks/manage-daemon/update-daemon-set/ - KEP: https://github.com/kubernetes/enhancements/issues/1591 - API Changes: https://github.com/kubernetes/kubernetes/pull/96375 --> ### 针对 DaemonSet 的 maxSurge   {#learn-more-daemonset-maxsurge} - 文档： https://k8s.io/zh-cn/docs/tasks/manage-daemon/update-daemon-set/ - KEP： https://github.com/kubernetes/enhancements/issues/1591 - API 变更： https://github.com/kubernetes/kubernetes/pull/96375 <!-- ## How do I get involved? Please reach out to us on [#sig-apps](https://kubernetes.slack.com/archives/C18NZM5K9) channel on Slack, or through the SIG Apps mailing list [kubernetes-sig-apps@googlegroups.com](https://groups.google.com/g/kubernetes-sig-apps). --> ## 我如何参与？   {#how-do-i-get-involved} 请通过 Slack [#sig-apps](https://kubernetes.slack.com/archives/C18NZM5K9) 频道或通过 SIG Apps 邮件列表 [kubernetes-sig-apps@googlegroups.com](https://groups.google.com/g/kubernetes-sig-apps) 联系我们。 </ins>

This is a Feature Request Will localize this blog to zh text: /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: This projected volume consists of three sources: <del> 1. A ServiceAccountToken acquired from kube-apiserver via TokenRequest API. It will expire after 1 hour by default or when the pod is deleted. It is bound to the pod and has kube-apiserver as the audience. 1. A ConfigMap containing a CA bundle used for verifying connections to the kube-apiserver. This feature depends on the `RootCAConfigMap` feature gate, which publishes a "kube-root-ca.crt" ConfigMap to every namespace. `RootCAConfigMap` feature gate is graduated to GA in 1.21 and default to true. (This flag will be removed from --feature-gate arg in 1.22) 1. A DownwardAPI that references the namespace of the pod. </del> <ins> 1. A `serviceAccountToken` acquired from kube-apiserver via TokenRequest API. It will expire after 1 hour by default or when the pod is deleted. It is bound to the pod and it has its audience set to match the audience of the `kube-apiserver`. 1. A `configMap` containing a CA bundle used for verifying connections to the kube-apiserver. 1. A `downwardAPI` that references the namespace of the pod. </ins> See more details about [projected volumes](/docs/tasks/configure-pod-container/configure-projected-volume-storage/).

says about : Since 1.22 is released, the text shall not say what is planned to happen in the 1.22 versions, as if those were in the future.
/triage accepted /kind bug /assign
/language en


Question: ### Menginstal program kubectl dengan curl pada Windows <del> 1. Unduh versi terbarunya {{< param "fullversion" >}} dari [tautan ini](https://storage.googleapis.com/kubernetes-release/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe). </del> <ins> 1. Unduh versi terbarunya {{< param "fullversion" >}} dari [tautan ini](https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe). </ins> Atau jika sudah ada `curl` pada mesin kamu, jalankan perintah ini: ``` <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> Untuk mendapatkan versi stabil terakhir (misalnya untuk _scripting_), lihat di [https://storage.googleapis.com/kubernetes-release/release/stable.txt](https://storage.googleapis.com/kubernetes-release/release/stable.txt). </del> <ins> Untuk mendapatkan versi stabil terakhir (misalnya untuk _scripting_), lihat di [https://dl.k8s.io/release/stable.txt](https://dl.k8s.io/release/stable.txt). </ins> 2. Tambahkan program yang sudah diunduh tersebut ke PATH kamu. 3. Pastikan instalasinya sudah berhasil dengan melakukan pengecekan versi:

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.


Question:
--address string     Default: 0.0.0.0

  	The IP address for the Kubelet to serve on (set to 0.0.0.0 or :: for listening in gll interfaces and IP families)  (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.)	   	The IP address for the Kubelet to serve on (set to 0.0.0.0 or :: for listening in all interfaces and IP families)  (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.)

says: typo gll → all
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


Question: systemctl daemon-reload systemctl restart docker ``` <del> {{< /tab >}} {{< tab name="CentOS/RHEL 7.4+" >}} </del> <ins> {{% /tab %}} {{% tab name="CentOS/RHEL 7.4+" %}} </ins> ```shell # (도커 CE 설치)

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 for tabs on "Container runtimes" page as below. ! Proposed Solution: TBD Page to Update: /language ko <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/retitle Broken layout for tabs on "Container runtimes" page in Korean
This problem is due to incorrect tab code. We should fix this like the below: (Line 71, 125, 126, 180) to
/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 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
Hey folks, I'm happy to help you with this /assign


Question: 1. In a terminal window, clone your fork and update the [Docsy Hugo theme](https://github.com/google/docsy#readme): ```shell <del> git clone git@github.com/<github_username>/website </del> <ins> git clone git@github.com:<github_username>/website </ins> cd website git submodule update --init --recursive --depth 1 ```

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: It failed when running the command in the doc It works after replacing the first with in Proposed Solution: Replace the first with in 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
I will open a PR to fix it.
/retitle Incorrect git clone URL in "Opening a pull request" page /language en


Question: kubectl logs myapp-pod -c init-mydb      # Inspect the second init container ``` <del> At this point, those init containers will be waiting to discover Services named </del> <ins> At this point, those init containers will be waiting to discover {{< glossary_tooltip text="Services" term_id="service" >}} named </ins> `mydb` and `myservice`. Here's a configuration you can use to make those Services appear:

This is a Bug Report Problem: section of page does not cover all required reference points which are mentioned throughout page. Proposed Solution: Add references of below topics under what's next section of page. learn about service, volume. kubelet, kubectl overview. Garbage Collection that Kubernetes uses to clean up cluster resources. Types of probes. Liveness, Readiness and Startup Probes. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/sig docs /language en /assign
/remove-kind bug /triage accepted I'm not sure how much we need to tell people about Services and Volumes; maybe we should instead signpost readers to learn more about Pods in general - perhaps links to specific fragments of relevant Pod pages? Same for garbage collection really.
Thanks for reply. In that case i will add one link in general to know more about pods and service under What's next section. For garbage collection its already available under what's next section. So i will not add reference link inside page.
Oops! it was my mistake, there is no reference link provided for under what's next section. will add this too.
Hi , Below, i prepared the preview changes what i am planning to do as per my understanding based your comment above. I would like to confirm is these changes you were expecting to do for this issue. ! Please suggest.
Hi Could you please confirm on above comment.
Hi Could you please take a look on Hi Please confirm if these changes sounds good to you. So that i can go ahead and work on it, Thanks.
When adding links, please use links that have words like “volumes”; readers don't need to see the URL. If you send in a pull request we can offer feedback on it directly. Ideally we can accept it as is!
Thanks for your response, i will soon open a PR for it.
Fixed it here .


Question: - `KubeletTracing`: Add support for distributed tracing in the kubelet. When enabled, kubelet CRI interface and authenticated http servers are instrumented to generate OpenTelemetry trace spans. <del> See [Traces for Kubernetes System Components](/docs/concepts/cluster-administration/traces-for-kubernetes-system-components) for more details. </del> <ins> See [Traces for Kubernetes System Components](/docs/concepts/cluster-administration/system-traces) for more details. </ins> - `LegacyServiceAccountTokenNoAutoGeneration`: Stop auto-generation of Secret-based [service account tokens](/docs/reference/access-authn-authz/authentication/#service-account-tokens). - `LocalStorageCapacityIsolation`: Enable the consumption of

This is a Bug Report In the file: find two hits: with broken links to 404. /language en
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
Below is the correct link for Traces for Kubernetes System Components:
/assign


Question: FOO_SERVICE_PORT=<порт, на котором запущен сервис> ``` <del> Сервисы получают выделенные IP-адреса и доступны для контейнера через DNS, если включен [аддон DNS](https://releases.k8s.io/{{< param "fullversion" >}}/cluster/addons/dns/). </del> <ins> Сервисы получают выделенные IP-адреса и доступны для контейнера через DNS, если включен [аддон DNS](https://releases.k8s.io/v{{< skew currentPatchVersion >}}/cluster/addons/dns/). </ins> ## {{% heading "whatsnext" %}}

Problem: Based on , I have created this issue/task to help update the [ru] language documentation. Proposed Solution: Page to Update: In the branch, I found: Results for "fullversion" in "k8s-website/content/ru" /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/tasks/tools/install- 33: Например, для установки версии {{< param "fullversion" }} на Linux введите: 36: {{< param "fullversion" }}/bin/linux/amd64/kubectl 110: Например, для установки версии {{< param "fullversion" }} на macOS введите: 113: {{< param "fullversion" }}/bin/darwin/amd64/kubectl 175: 1. Загрузите последний релиз {{< param "fullversion" }} по этой ссылке. 180: {{< param "fullversion" }} In the branch, I found: Results for "fullversion" in "k8s-website/content/ru" /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/concepts/containers/container- 44: DNS, если включен . /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/setup/learning- 222: чтобы запустить Minikube из-под версии {{< param "fullversion" }}, вам нужно выполнить следующую команду: 225: minikube start --kubernetes-version {{< param "fullversion" }} /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/tasks/tools/install- 36: Например, команда загрузки версии {{< param "fullversion" }} для Linux будет выглядеть следующим образом 39: curl -LO {{< param "fullversion" }}/bin/linux/amd64/kubectl 116: Например, команда загрузки версии {{< param "fullversion" }} для macOS будет выглядеть следующим образом 119: curl -LO {{< param "fullversion" }}/bin/darwin/amd64/kubectl 183: 1.

Загрузите последнюю версию {{< param "fullversion" }} по этой ссылкеe


Question: title: Kubernetesのコンポーネント content_type: concept description: > <del> Kubernetesクラスターはコントロールプレーンやノードと呼ばれるマシン群といったコンポーネントからなります。 weight: 20 </del> <ins> Kubernetesクラスターはコントロールプレーンのコンポーネントとノードと呼ばれるマシン群で構成されています。 weight: 30 </ins> card: name: concepts weight: 20

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. --Updated Japanese translation for the file. Why is this needed There are several updates in and therefore this page is outdated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/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: Patch your Deployment: ```shell <del> kubectl patch deployment retainkeys-demo --type merge --patch-file patch-file-no-retainkeys.yaml </del> <ins> kubectl patch deployment retainkeys-demo --type strategic --patch-file patch-file-no-retainkeys.yaml </ins> ``` In the output, you can see that it is not possible to set `type` as `Recreate` when a value is defined for `spec.strategy.rollingUpdate`:

example commands are missing Resulting in: I will prepare a patch for this.
/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 : /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


Question: ([Running Automated Tasks with a CronJob](/docs/tasks/job/automated-tasks-with-cron-jobs/) takes you through this example in more detail). <ins> ### Cron schedule syntax ``` # ┌───────────── 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) # │ │ │ │ │ # │ │ │ │ │ # * * * * * ``` | Entry 										| Description																									| Equivalent to | | ------------- 						| ------------- 																							|-------------  | | @yearly (or @annually)		| Run once a year at midnight of 1 January										| 0 0 1 1 * 		| | @monthly 									| Run once a month at midnight of the first day of the month	| 0 0 1 * * 		| | @weekly 									| Run once a week at midnight on Sunday morning								| 0 0 * * 0 		| | @daily (or @midnight)			| Run once a day at midnight																	| 0 0 * * * 		| | @hourly 									| Run once an hour at the beginning of the hour								| 0 * * * * 		| For example, the line below states that the task must be started every Friday at midnight, as well as on the 13th of each month at midnight: `0 0 13 * 5` To generate CronJob schedule expressions, you can also use web tools like [crontab.guru](https://crontab.guru/). </ins> ## CronJob limitations {#cron-job-limitations} A cron job creates a job object _about_ once per execution time of its schedule. We say "about" because there

<!-- Please only use this template for submitting enhancement requests --What would you like to be : Add CronJob full syntax at and also in the Ex, the line below states that the job must be scheduled every friday as well as the 13th of each month at midnight : 0 0 13 5 Entry Equivalent to -- -- (or 0 0 1 1 0 0 1 0 0 0 (or 0 0 0 N/A Required Remarks -- -- Minutes Hours Day of month ? L W only in some implementations Month Day of week ? L # only in some implementations Year This field is not supported in standard/default implementations Comma ( , ) Commas are used to separate items of a list. For example, using "MON,WED,FRI" in the 5th field (day of week) means Mondays, Wednesdays and Fridays. Dash( - ) Dash defines ranges. For example, 2000-2010 indicates every year between 2000 and 2010, inclusive. Percent ( % ) Percent-signs (%) in the command, unless escaped with backslash (), are changed into newline characters, and all data after the first % are sent to the command as standard input.[13] Non-standard characters The following are non-standard characters and exist only in some cron implementations, such as the Quartz Java scheduler. L 'L' stands for "last". When used in the day-of-week field, it allows specifying constructs such as "the last Friday" ("5L") of a given month. In the day-of-month field, it specifies the last day of the month. Slash (/) In vixie-cron, slashes can be combined with ranges to specify step values.[3] For example, /5 in the minutes field indicates every 5 minutes Hash (#) '#' is allowed for the day-of-week field, and must be followed by a number between one and five. It allows specifying constructs such as "the second Friday" of a given month.[14] For example, entering "5" in the day-of-week field corresponds to the third Friday of every month. Why is this needed: it would be unfair for anyone clearing the CKAD & CKA exams, to fails some questions just because people do not remeber the syntax.

/sig docs
/sig docs
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
Thanks! This is really informative and definitely help to beginners. I would like to add some general examples and use the same format as Can I work on this?
thanks for your reply, yes please feel free to work on it !
/assign shekhar-rajak
/remove-lifecycle rotten
Does k8s actually support those extended features (# offset etc)? Can't find it in the docs anywhere.
Looks like K8s uses for CronJobs And it doesn't support the extended cron syntax.
/transfer website BTW, there is no (permitted) cheatsheet for the Kubernetes certifications. The term “cheat sheet” means a handy lookup and not a guide to answering a specific exam.
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: You can project keys to specific paths and specific permissions on a per-file basis. The [Secrets](/docs/concepts/configuration/secret#using-secrets-as-files-from-a-pod) user guide explains the syntax. <del> ## Real World Example: Configuring Redis using a ConfigMap You can follow the steps below to configure a Redis cache using data stored in a ConfigMap. 1. Create a ConfigMap from the `docs/user-guide/configmap/redis/redis-config` file ```shell kubectl create configmap example-redis-config --from-file=docs/user-guide/configmap/redis/redis-config kubectl get configmap example-redis-config -o yaml ``` ```yaml apiVersion: v1 data: redis-config: | maxmemory 2mb maxmemory-policy allkeys-lru kind: ConfigMap metadata: creationTimestamp: 2016-03-30T18:14:41Z name: example-redis-config namespace: default resourceVersion: "24686" selfLink: /api/v1/namespaces/default/configmaps/example-redis-config uid: 460a2b6e-f6a3-11e5-8ae5-42010af00002 ``` 1. Create a pod specification that uses the config data stored in the ConfigMap: ```yaml apiVersion: v1 kind: Pod metadata: name: redis spec: containers: - name: redis image: kubernetes/redis:v1 env: - name: MASTER value: "true" ports: - containerPort: 6379 resources: limits: cpu: "0.1" volumeMounts: - mountPath: /redis-master-data name: data - mountPath: /redis-master name: config volumes: - name: data emptyDir: {} - name: config configMap: name: example-redis-config items: - key: redis-config path: redis.conf ``` 1. Create the pod. ```shell kubectl create -f docs/user-guide/configmap/redis/redis-pod.yaml ``` In the example, the config volume is mounted at `/redis-master`. It uses `path` to add the `redis-config` key to a file named `redis.conf`. The file path for the redis config, therefore, is `/redis-master/redis.conf`. This is where the image will look for the config file for the redis master. 1. Use `kubectl exec` to enter the pod and run the `redis-cli` tool to verify that the configuration was correctly applied: ```shell kubectl exec -it redis redis-cli 127.0.0.1:6379> CONFIG GET maxmemory 1) "maxmemory" 2) "2097152" 127.0.0.1:6379> CONFIG GET maxmemory-policy 1) "maxmemory-policy" 2) "allkeys-lru" ``` </del> {% endcapture %} {% capture discussion %}

<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... [x ] Feature Request Problem: As discussed in , the 'Real World Example' section of should probably be a separate tutorial. Proposed Solution: Create a new tutorial from the existing content (probably needs additional information). Remove the section from the task doc and replace with a 'What's Next' pointer to new tutorial doc. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
done


Question: literal values. For example, the following instructions create a Kustomization file for the username `admin` and the password `1f2d1e2e67df`. <ins> {{< note >}} The `stringData` field for a Secret does not work well with server-side apply. {{< /note >}} </ins> ### Create the Kustomization file {{< tabs name="Secret data" >}}

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.


Question: Container Vulnerability Scanning and OS Dependency Security | As part of an image build step, you should scan your containers for known vulnerabilities. Image Signing and Enforcement | Sign container images to maintain a system of trust for the content of your containers. Disallow privileged users | When constructing containers, consult your documentation for how to create users inside of the containers that have the least level of operating system privilege necessary in order to carry out the goal of the container. <ins> Use container runtime with stronger isolation | Select [container runtime classes](/docs/concepts/containers/runtime-class/) that provider stronger isolation </ins> --> ## 容器

! Chinese page link can not open
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 zh
/assign
/kind bug


Question: - Using PowerShell to automate the verification using the `-eq` operator to get a `True` or `False` result: ```powershell <del> $($(CertUtil -hashfile .kubectl.exe SHA256)[1] -replace " ", "") -eq $(type .kubectl.exe.sha256) </del> <ins> $(Get-FileHash -Algorithm SHA256 .kubectl.exe).Hash -eq $(Get-Content .kubectl.exe.sha256) </ins> ``` 1. Append or prepend the `kubectl` binary folder to your `PATH` environment variable.

Why not use PowerShell Get-FileHash instead of certutil for getting/checking file hashes?
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
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
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]:
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: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:
Closing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. 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 closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] 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
/remove-lifecycle stale
/reopen
You can't reopen an issue/PR unless you authored it or you are a collaborator. <detailsIn response to : /reopen 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
-- makes sense. I've raised a PR here -


Question: ## Running the website locally using Hugo <del> Make sure to install the Hugo extended version specified by the `HUGO_VERSION` environment variable in the [`netlify.toml`](netlify.toml#L10) file. </del> <ins> Make sure to install the Hugo extended version specified by the `HUGO_VERSION` environment variable in the [`netlify.toml`](netlify.toml#L11) file. </ins> To build and test the site locally, run:

Under the the is pointing toward the wrong line in the file.
/assign
/retitle Incorrect line reference in within
/triage accepted


Question: app.kubernetes.io/name: mysql app.kubernetes.io/instance: mysql-abcxzy app.kubernetes.io/version: "5.7.21" <del> app.kubernetes.io/managed-by: helm </del> <ins> app.kubernetes.io/managed-by: Helm </ins> app.kubernetes.io/component: database app.kubernetes.io/part-of: wordpress ...

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


Question: an owner reference. Owner references help different parts of Kubernetes avoid interfering with objects they don’t control. <ins> {{< note >}} Cross-namespace owner references are disallowed by design. Namespaced dependents can specify cluster-scoped or namespaced owners. A namespaced owner **must** exist in the same namespace as the dependent. If it does not, the owner reference is treated as absent, and the dependent is subject to deletion once all owners are verified absent. Cluster-scoped dependents can only specify cluster-scoped owners. In v1.20+, if a cluster-scoped dependent specifies a namespaced kind as an owner, it is treated as having an unresolvable owner reference, and is not able to be garbage collected. In v1.20+, if the garbage collector detects an invalid cross-namespace `ownerReference`, or a cluster-scoped dependent with an `ownerReference` referencing a namespaced kind, a warning Event with a reason of `OwnerRefInvalidNamespace` and an `involvedObject` of the invalid dependent is reported. You can check for that kind of Event by running `kubectl get events -A --field-selector=reason=OwnerRefInvalidNamespace`. {{< /note >}} </ins> ## Cascading deletion {#cascading-deletion} Kubernetes checks for and deletes objects that no longer have owner

The following information was dropped in and is critical to include in the garbage collection ownerReferences topic:
/triage accepted /sig api-machinery
/priority important-soon


Question: ## Background <del> Docker has a concept of [volumes](https://docs.docker.com/storage/), though it is somewhat looser and less managed. A Docker volume is a directory on disk or in another container. Docker provides volume drivers, but the functionality is somewhat limited. </del> Kubernetes supports many types of volumes. A {{< glossary_tooltip term_id="pod" text="Pod" >}} can use any number of volume types simultaneously. [Ephemeral volume](/docs/concepts/storage/ephemeral-volumes/) types have a lifetime of a pod,

This is a Bug Report Problem: The "background" sections describes volumes as if they all were ephemeral: It also starts with a comparison against Docker, which may or may not still make sense. Proposed Solution: Rewrite and link to the persistent- and (once is merged) to ephemeral- Page to Update:
/sig storage /priority backlog I definitely agree about the Docker stuff - there's no need to focus on a particular runtime, nor on Docker as a local development tool.
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 /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
/assign


Question: * [Apply Pod Security Standards at Cluster level](/docs/tutorials/security/cluster-level-pss/) * [Apply Pod Security Standards at Namespace level](/docs/tutorials/security/ns-level-pss/) <ins> * [AppArmor](/docs/tutorials/security/apparmor/) * [seccomp](/docs/tutorials/security/seccomp/) </ins> ## {{% heading "whatsnext" %}} If you would like to write a tutorial, see

This is a Feature Request What would you like to be Post-merge of , move the tutorials under into Merge clusters section into security section here: Why is this needed Issue description is a slight modification from original request in the comment Comments /hold for /cc /sig docs security
this might be a good first issue for new contributors in sig-security-docs /triage accepted
Hi, I would like to work on this issue. /assign
/kind cleanup
Hi , I a query: moving the tutorials from the cluster sub-directory into the security sub-directory, the cluster sub-directory will only have its file so do I need to do something regarding it ( file)? Thanks
Whenever you are free can you please help me with the above mentioned query. Thanks


Question: frontend-3823415956-k22zn       1/1       Running   0          54m frontend-3823415956-w9gbt       1/1       Running   0          54m frontend-3823415956-x2pld       1/1       Running   0          5s <del> mongo-1068406935-3lswp   1/1       Running   0          56m </del> <ins> mongo-1068406935-3lswp          1/1       Running   0          56m </ins> ``` 1. Run the following command to scale down the number of frontend Pods:

4 ordered lists have wrong indexes. For example, the number below should be 3. ! Page to update: /language en /kind cleanup
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


Question: </source> # Example: <del> # I0204 06:55:31.872680       5 servicecontroller.go:277] LB already exists and doesn't need update for service kube-system/kube-ui </del> <ins> # I0204 06:55:31.872680       5 servicecontroller.go:277] LB already exists and doesn't need update for service kube-system/kubernetes-dashboard </ins> <source> type tail format multiline

Connect with Proxies references kube ui. It should use the kube dashboard instead.
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. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale


Question:
Recently, the team launched a new single sign-on solution for use in an internal application. "Due to the resource based architecture of the Kubernetes platform, we were able to bring that application into an entirely new production environment in less than a day, most of that time used for testing after applying the already well-known resource definitions from staging to the new environment," says van den Bosch. "On a traditional VM this would have likely cost a day or two, and then probably a few weeks to iron out the kinks in our provisioning scripts as we apply updates."

Legacy applications are also being moved to Kubernetes. Not long ago, the team needed to set up a Java-based application for compiling and running a frontend. "On a traditional VM, it would have taken quite a bit of time to set it up and keep it up to date, not to mention maintenance for that setup down the line," says van den Bosch. Instead, it took less than half a day to Dockerize it and get it running on Kubernetes. "It was much easier, and we were able to save costs too because we didn't have to spin up new VMs specially for it."

Legacy applications are also being moved to Kubernetes. Not long ago, the team needed to set up a Java-based application for compiling and running a frontend. "On a traditional VM, it would have taken quite a bit of time to set it up and keep it up to date, not to mention maintenance for that setup down the line," says van den Bosch. Instead, it took less than half a day to containerize it and get it running on Kubernetes. "It was much easier, and we were able to save costs too because we didn't have to spin up new VMs specially for it."
  {{< case-studies/quote author="VICTOR VAN DEN BOSCH, SENIOR DEVOPS ENGINEER, PROWISE" >}} "We're really trying to deliver integrated solutions with our hardware and software and making it as easy as possible for users to use and collaborate from different places," says van den Bosch. And, says Haalstra, "We cannot do it without Kubernetes."

ref: Some of the case studies need a bit of rewording to remove unnecessary mention of docker. Note: the case studies are HTML + CSS rather than markdown - you need to be familiar with that in order to update these! I'd reword “Docker containers” to “containers” I'd reword “Dockerize” to “containerize” I'd reword “Docker file” to “Dockerfile” I'd change “just over two years ago” to “in 2015” I'd also change “Dockerized” to “containerized” /priority backlog /triage accepted
Hi there, I would like to work on this issue. /assign
I have an question does the PR need to made against the branch or the branch? Thanks
You need to make a PR against the branch.
/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 : /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
/assign
Hi I have opened a regarding this a few days ago. If you are free can you PTAL at the PR. Thanks.
Please close your PR as has already it earlier. Kindly look into those issues which are not already assigned to someone. Thank you.
/assign


Question: CEL is configured with the following options, libraries and language features, introduced at the specified Kubernetes versions: <del> | CEL option, library or language feature             | Included                                                                                | Availablity                | | --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | -------------------------- | | [Standard macros](stdmacros)                        | `has`, `all`, `exists`, `exists_one`, `map`, `filter`                                                           | All Kubernetes versions    | | [Standard functions](stdlib)                        | See [official list of standard definitions](stdlib)                                                             | All Kubernetes versions    | | [Homogeneous Aggregate Literals](opt1)              |                                                                                | All Kubernetes versions    | | [Default UTC Time Zone](opt2)                       |                                                                                | All Kubernetes versions    | | [Eagerly Validate Declarations](opt3)               |                                                                                | All Kubernetes versions    | | [extended strings library](stringsgodoc), Version 1 | `charAt`, `indexOf`, `lastIndexOf`, `lowerAscii`, `upperAscii`, `replace`, `split`, `join`, `substring`, `trim` | All Kubernetes versions    | | Kubernetes list library                             | See [Kubernetes list library](#kubernetes-list-library)                                                         | All Kubernetes versions    | | Kubernetes regex library                            | See [Kubernetes regex library](#kubernetes-regex-library)                                                       | All Kubernetes versions    | | Kubernetes URL library                              | See [Kubernetes URL library](#kubernetes-url-library)                                                           | All Kubernetes versions    | | Kubernetes authorizer library                       | See [Kubernetes authorizer library](#kubernetes-authorizer-library)                                             | All Kubernetes versions    | [stdmacros]: https://github.com/google/cel-spec/blob/v0.7.0/doc/langdef.md#macros [stdlib]: https://github.com/google/cel-spec/blob/master/doc/langdef.md#list-of-standard-definitions [stringsgodoc]: https://pkg.go.dev/github.com/google/cel-go/ext#Strings [opt1]: https://pkg.go.dev/github.com/google/cel-go@v0.17.4/cel#HomogeneousAggregateLiterals [opt2]: https://pkg.go.dev/github.com/google/cel-go@v0.17.4/cel#DefaultUTCTimeZone [opt3]: https://pkg.go.dev/github.com/google/cel-go@v0.17.4/cel#EagerlyValidateDeclarations [opt4]: https://pkg.go.dev/github.com/google/cel-go@v0.17.4/cel#OptionalTypes [opt5]: https://pkg.go.dev/github.com/google/cel-go@v0.17.4/cel#CrossTypeNumericComparisons </del> <ins> | CEL option, library or language feature                                                                                | Included                                                                                | Availablity               | |------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| | [Standard macros](https://github.com/google/cel-spec/blob/v0.7.0/doc/langdef.md#macros)                                | `has`, `all`, `exists`, `exists_one`, `map`, `filter`                                                                                | All Kubernetes versions   | | [Standard functions](https://github.com/google/cel-spec/blob/master/doc/langdef.md#list-of-standard-definitions)       | See [official list of standard definitions](https://github.com/google/cel-spec/blob/master/doc/langdef.md#list-of-standard-definitions)   | All Kubernetes versions   | | [Homogeneous Aggregate Literals](https://pkg.go.dev/github.com/google/cel-go@v0.17.4/cel#HomogeneousAggregateLiterals) |                                                                                | All Kubernetes versions   | | [Default UTC Time Zone](https://pkg.go.dev/github.com/google/cel-go@v0.17.4/cel#DefaultUTCTimeZone)                    |                                                                                | All Kubernetes versions   | | [Eagerly Validate Declarations](https://pkg.go.dev/github.com/google/cel-go@v0.17.4/cel#EagerlyValidateDeclarations)   |                                                                                | All Kubernetes versions   | | [extended strings library](https://pkg.go.dev/github.com/google/cel-go/ext#Strings), Version 1                         | `charAt`, `indexOf`, `lastIndexOf`, `lowerAscii`, `upperAscii`, `replace`, `split`, `join`, `substring`, `trim`                           | All Kubernetes versions   | | Kubernetes list library                                                                                | See [Kubernetes list library](#kubernetes-list-library)                                                                                | All Kubernetes versions   | | Kubernetes regex library                                                                                | See [Kubernetes regex library](#kubernetes-regex-library)                                                                                | All Kubernetes versions   | | Kubernetes URL library                                                                                | See [Kubernetes URL library](#kubernetes-url-library)                                                                                | All Kubernetes versions   | | Kubernetes authorizer library                                                                                | See [Kubernetes authorizer library](#kubernetes-authorizer-library)                                                                       | All Kubernetes versions   | | Kubernetes quantity library                                                                                | See [Kubernetes quantity library](#kubernetes-quantity-library)                                                                           | Kubernetes versions 1.29+ | | CEL optional types                                                                                | See [CEL optional types](https://pkg.go.dev/github.com/google/cel-go@v0.17.4/cel#OptionalTypes)                                           | Kubernetes versions 1.29+ | | CEL CrossTypeNumericComparisons                                                                                | See [CEL CrossTypeNumericComparisons](https://pkg.go.dev/github.com/google/cel-go@v0.17.4/cel#CrossTypeNumericComparisons)                | Kubernetes versions 1.29+ | </ins> CEL functions, features and language settings support Kubernetes control plane rollbacks. For example, _CEL Optional Values_ was introduced at Kubernetes 1.29

This is a Bug Report Problem: has an entry for "Standard functions - See official list of standard definitions". Both link to which just shows an error page ("Were you looking for..."). Proposed Solution: I'm not sure :sweat_smile: - I am new to CEL and don't know where the standard lib is defined. Page to Update: /cc
/triage accepted /assign Hi , thanks for raising this! I will open an pr to fix it shortly :)
/language en /priority backlog
This is due to the reference for the hyperlinks mentioned after the table, which are not working. see the code here: we have to update the links in the table. For example, the hyperlink for Standard functions is mentioned like but it should be
Thanks for pointing out. I have raised the PR to address this and please feel free to take a look. :)


Question: 시스템에 도커를 설치하기 위해서 아래의 커맨드들을 사용한다. {{< tabs name="tab-cri-docker-installation" >}} <del> {{< tab name="Ubuntu 16.04+" >}} </del> <ins> {{% tab name="Ubuntu 16.04+" %}} </ins> ```shell # (도커 CE 설치)

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 for tabs on "Container runtimes" page as below. ! Proposed Solution: TBD Page to Update: /language ko <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/retitle Broken layout for tabs on "Container runtimes" page in Korean
This problem is due to incorrect tab code. We should fix this like the below: (Line 71, 125, 126, 180) to
/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 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
Hey folks, I'm happy to help you with this /assign


Question: to use a different pod template and for the Job to have a new name. You cannot update the Job because these fields are not updatable. Therefore, you delete Job `old` but _leave its pods <del> running_, using `kubectl delete jobs/old --cascade=false`. </del> <ins> running_, using `kubectl delete jobs/old --cascade=orphan`. </ins> Before deleting it, you make a note of what selector it uses: ```shell

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 ().


Question: ### Project keys to specific paths and file permissions <del> You can project keys to specific paths and specific permissions on a per-file basis. The [Secrets](/docs/concepts/configuration/secret/#using-secrets-as-files-from-a-pod) guide explains the syntax. </del> <ins> You can project keys to specific paths. Refer to the corresponding section in the [Secrets](/docs/tasks/inject-data-application/distribute-credentials-secure/#project-secret-keys-to-specific-file-paths) guide for the syntax. You can set POSIX permissions for keys. Refer to the corresponding section in the [Secrets](/docs/tasks/inject-data-application/distribute-credentials-secure/#set-posix-permissions-for-secret-keys) guide for the syntax. </ins> ### Optional references

In , it mentions this guide explains the syntax. However the above Secret link doesn't mention anything on "specific paths" & file permission is defined . Appreciate feedback and update (correction) to documentation.
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
/kind bug
/remove-kind bug I think this is a request to mention POSIX permissions for the volume and its files, within the task page “Configure a Pod to Use a ConfigMap”. Is that right ? If that covers everything you want to see changed, please state that so we're sure. If you want another change as well, please be as clear as you can about what improvement you'd like. /language en
The reference needs to be updated/corrected to and on the page Configure a Pod to Use a ConfigMap and subsection !
/assign


Question: <!-- overview --> <!-- <del> A _Deployment_ provides declarative updates for [Pods](/docs/concepts/workloads/pods/pod/) and [ReplicaSets](/docs/concepts/workloads/controllers/replicaset/). </del> <ins> A _Deployment_ provides declarative updates for {{< glossary_tooltip text="Pods" term_id="pod" >}} and {{< glossary_tooltip term_id="replica-set" text="ReplicaSets" >}}. </ins> --> 一个 Deployment 为 {{< glossary_tooltip text="Pod" term_id="pod" >}} 和 {{< glossary_tooltip term_id="replica-set" text="ReplicaSet" >}}

There are some bugs: ,nginx%3Dnginx%3A1.9.1,-%2D%2Drecord%3Dtrue%0A3 "nginx=nginx:1.9.1" should be changed to "nginx=nginx:1.16.1" ,nginx%3Dnginx%3A1.91,-%2D%2Drecord%3Dtrue "nginx=nginx:1.91" should be changed to "nginx=nginx:1.161" "image updated to 1.9.1" should be changed to "image updated to 1.16.1" The content of this article has many "", it could be changed to "deployment". For example: ,,-%E8%BE%93%E5%87%BA%E7%B1%BB%E4%BC%BC%E4%BA%8E "kubectl rollout history " could be changed to "kubectl rollout history deployment/nginx-deployment"
/language zh
/triage accepted
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
looks like docs is already updated to nginx:1.16.1. Do you mind closing this issue?
There should still be a few places left unfinished.
Could you please edit the issue which needs to be still updated?
Bug1: ,nginx%3Dnginx%3A1.9.1,-%2D%2Drecord%3Dtrue%0A3 "nginx=nginx:1.9.1" should be changed to "nginx=nginx:1.16.1" Bug2: ,nginx%3Dnginx%3A1.91,-%2D%2Drecord%3Dtrue "nginx=nginx:1.91" should be changed to "nginx=nginx:1.161" Bug3: "image updated to 1.9.1" should be changed to "image updated to 1.16.1" Bug4: The content of this article has many "", it could be changed to "deployment".

For example: ,,-%E8%BE%93%E5%87%BA%E7%B1%BB%E4%BC%BC%E4%BA%8E "kubectl rollout history " could be changed to "kubectl rollout history deployment/nginx-deployment"
Thanks for clarifying. /assign
/retitle [zh] Localization bugs / work required for Deployment concept
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
/triage accepted