Question: <ins> --- title: 关于 cgroup v2 content_type: concept weight: 50 --- <!-- title: About cgroup v2 content_type: concept weight: 50 --> <!-- overview --> <!-- On Linux, {{< glossary_tooltip text="control groups" term_id="cgroup" >}} constrain resources that are allocated to processes. The {{< glossary_tooltip text="kubelet" term_id="kubelet" >}} and the underlying container runtime need to interface with cgroups to enforce [resource mangement for pods and containers](/docs/concepts/configuration/manage-resources-containers/) which includes cpu/memory requests and limits for containerized workloads. There are two versions of cgroups in Linux: cgroup v1 and cgroup v2. cgroup v2 is the new generation of the `cgroup` API. --> 在 Linux 上，{{< glossary_tooltip text="控制组" term_id="cgroup" >}}约束分配给进程的资源。 {{< glossary_tooltip text="kubelet" term_id="kubelet" >}} 和底层容器运行时都需要对接 cgroup 来强制执行[为 Pod 和容器管理资源](/zh-cn/docs/concepts/configuration/manage-resources-containers/)， 这包括为容器化工作负载配置 CPU/内存请求和限制。 Linux 中有两个 cgroup 版本：cgroup v1 和 cgroup v2。cgroup v2 是新一代的 `cgroup` API。 <!-- body --> <!-- ## What is cgroup v2? {#cgroup-v2} --> ## 什么是 cgroup v2？  {#cgroup-v2} {{< feature-state for_k8s_version="v1.25" state="stable" >}} <!-- cgroup v2 is the next version of the Linux `cgroup` API. cgroup v2 provides a unified control system with enhanced resource management capabilities. --> cgroup v2 是 Linux `cgroup` API 的下一个版本。cgroup v2 提供了一个具有增强资源管理能力的统一控制系统。 <!-- cgroup v2 offers several improvements over cgroup v1, such as the following: - Single unified hierarchy design in API - Safer sub-tree delegation to containers - Newer features like [Pressure Stall Information](https://www.kernel.org/doc/html/latest/accounting/psi.html) - Enhanced resource allocation management and isolation across multiple resources - Unified accounting for different types of memory allocations (network memory, kernel memory, etc) - Accounting for non-immediate resource changes such as page cache write backs --> cgroup v2 对 cgroup v1 进行了多项改进，例如： - API 中单个统一的层次结构设计 - 更安全的子树委派给容器 - 更新的功能特性， 例如[压力阻塞信息（Pressure Stall Information，PSI）](https://www.kernel.org/doc/html/latest/accounting/psi.html) - 跨多个资源的增强资源分配管理和隔离 - 统一核算不同类型的内存分配（网络内存、内核内存等） - 考虑非即时资源变化，例如页面缓存回写 <!-- Some Kubernetes features exclusively use cgroup v2 for enhanced resource management and isolation. For example, the [MemoryQoS](/blog/2021/11/26/qos-memory-resources/) feature improves memory QoS and relies on cgroup v2 primitives. --> 一些 Kubernetes 特性专门使用 cgroup v2 来增强资源管理和隔离。 例如，[MemoryQoS](/blog/2021/11/26/qos-memory-resources/) 特性改进了内存 QoS 并依赖于 cgroup v2 原语。 <!-- ## Using cgroup v2 {#using-cgroupv2} The recommended way to use cgroup v2 is to use a Linux distribution that enables and uses cgroup v2 by default. To check if your distribution uses cgroup v2, refer to [Identify cgroup version on Linux nodes](#check-cgroup-version). --> ## 使用 cgroup v2  {#using-cgroupv2} 使用 cgroup v2 的推荐方法是使用一个默认启用 cgroup v2 的 Linux 发行版。 要检查你的发行版是否使用 cgroup v2，请参阅[识别 Linux 节点上的 cgroup 版本](#check-cgroup-version)。 <!-- ### Requirements cgroup v2 has the following requirements: * OS distribution enables cgroup v2 * Linux Kernel version is 5.8 or later * Container runtime supports cgroup v2. For example: * [containerd](https://containerd.io/) v1.4 and later * [cri-o](https://cri-o.io/) v1.20 and later * The kubelet and the container runtime are configured to use the [systemd cgroup driver](/docs/setup/production-environment/container-runtimes#systemd-cgroup-driver) --> ### 要求  {#requirements} cgroup v2 具有以下要求： * 操作系统发行版启用 cgroup v2 * Linux 内核为 5.8 或更高版本 * 容器运行时支持 cgroup v2。例如： * [containerd](https://containerd.io/) v1.4 和更高版本 * [cri-o](https://cri-o.io/) v1.20 和更高版本 * kubelet 和容器运行时被配置为使用 [systemd cgroup 驱动](/zh-cn/docs/setup/production-environment/container-runtimes#systemd-cgroup-driver) <!-- ### Linux Distribution cgroup v2 support For a list of Linux distributions that use cgroup v2, refer to the [cgroup v2 documentation](https://github.com/opencontainers/runc/blob/main/docs/cgroup-v2.md) --> ### Linux 发行版 cgroup v2 支持  {#linux-distribution-cgroup-v2-support} 有关使用 cgroup v2 的 Linux 发行版的列表， 请参阅 [cgroup v2 文档](https://github.com/opencontainers/runc/blob/main/docs/cgroup-v2.md)。 <!-- the list should be kept in sync with https://github.com/opencontainers/runc/blob/main/docs/cgroup-v2.md --> <!-- * Container Optimized OS (since M97) * Ubuntu (since 21.10, 22.04+ recommended) * Debian GNU/Linux (since Debian 11 bullseye) * Fedora (since 31) * Arch Linux (since April 2021) * RHEL and RHEL-like distributions (since 9) --> * Container-Optimized OS（从 M97 开始） * Ubuntu（从 21.10 开始，推荐 22.04+） * Debian GNU/Linux（从 Debian 11 Bullseye 开始） * Fedora（从 31 开始） * Arch Linux（从 2021 年 4 月开始） * RHEL 和类似 RHEL 的发行版（从 9 开始） <!-- To check if your distribution is using cgroup v2, refer to your distribution's documentation or follow the instructions in [Identify the cgroup version on Linux nodes](#check-cgroup-version). You can also enable cgroup v2 manually on your Linux distribution by modifying the kernel cmdline boot arguments. If your distribution uses GRUB, `systemd.unified_cgroup_hierarchy=1` should be added in `GRUB_CMDLINE_LINUX` under `/etc/default/grub`, followed by `sudo update-grub`.  However, the recommended approach is to use a distribution that already enables cgroup v2 by default. --> 要检查你的发行版是否使用 cgroup v2， 请参阅你的发行版文档或遵循[识别 Linux 节点上的 cgroup 版本](#check-cgroup-version)中的指示说明。 你还可以通过修改内核 cmdline 引导参数在你的 Linux 发行版上手动启用 cgroup v2。 如果你的发行版使用 GRUB，则应在 `/etc/default/grub` 下的 `GRUB_CMDLINE_LINUX` 中添加 `systemd.unified_cgroup_hierarchy=1`， 然后执行 `sudo update-grub`。不过，推荐的方法仍是使用一个默认已启用 cgroup v2 的发行版。 <!-- ### Migrating to cgroup v2 {#migrating-cgroupv2} To migrate to cgroup v2, ensure that you meet the [requirements](#requirements), then upgrade to a kernel version that enables cgroup v2 by default. The kubelet automatically detects that the OS is running on cgroup v2 and performs accordingly with no additional configuration required. --> ### 迁移到 cgroup v2   {#migrating-cgroupv2} 要迁移到 cgroup v2，需确保满足[要求](#requirements)，然后升级到一个默认启用 cgroup v2 的内核版本。 kubelet 能够自动检测操作系统是否运行在 cgroup v2 上并相应调整其操作，无需额外配置。 <!-- There should not be any noticeable difference in the user experience when switching to cgroup v2, unless users are accessing the cgroup file system directly, either on the node or from within the containers. cgroup v2 uses a different API than cgroup v1, so if there are any applications that directly access the cgroup file system, they need to be updated to newer versions that support cgroup v2. For example: --> 切换到 cgroup v2 时，用户体验应没有任何明显差异，除非用户直接在节点上或从容器内访问 cgroup 文件系统。 cgroup v2 使用一个与 cgroup v1 不同的 API，因此如果有任何应用直接访问 cgroup 文件系统， 则需要将这些应用更新为支持 cgroup v2 的版本。例如： <!-- * Some third-party monitoring and security agents may depend on the cgroup filesystem. Update these agents to versions that support cgroup v2. * If you run [cAdvisor](https://github.com/google/cadvisor) as a stand-alone DaemonSet for monitoring pods and containers, update it to v0.43.0 or later. * If you use JDK, prefer to use JDK 11.0.16 and later or JDK 15 and later, which [fully support cgroup v2](https://bugs.openjdk.org/browse/JDK-8230305). --> * 一些第三方监控和安全代理可能依赖于 cgroup 文件系统。你要将这些代理更新到支持 cgroup v2 的版本。 * 如果以独立的 DaemonSet 的形式运行 [cAdvisor](https://github.com/google/cadvisor) 以监控 Pod 和容器， 需将其更新到 v0.43.0 或更高版本。 * 如果你使用 JDK，推荐使用 JDK 11.0.16 及更高版本或 JDK 15 及更高版本， 以便[完全支持 cgroup v2](https://bugs.openjdk.org/browse/JDK-8230305)。 <!-- ## Identify the cgroup version on Linux Nodes  {#check-cgroup-version} The cgroup version depends on on the Linux distribution being used and the default cgroup version configured on the OS. To check which cgroup version your distribution uses, run the `stat -fc %T /sys/fs/cgroup/` command on the node: --> ## 识别 Linux 节点上的 cgroup 版本 {#check-cgroup-version} cgroup 版本取决于正在使用的 Linux 发行版和操作系统上配置的默认 cgroup 版本。 要检查你的发行版使用的是哪个 cgroup 版本，请在该节点上运行 `stat -fc %T /sys/fs/cgroup/` 命令： ```shell stat -fc %T /sys/fs/cgroup/ ``` <!-- For cgroup v2, the output is `cgroup2fs`. For cgroup v1, the output is `tmpfs.` --> 对于 cgroup v2，输出为 `cgroup2fs`。 对于 cgroup v1，输出为 `tmpfs`。 ## {{% heading "whatsnext" %}} <!-- - Learn more about [cgroups](https://man7.org/linux/man-pages/man7/cgroups.7.html) - Learn more about [container runtime](/docs/concepts/architecture/cri) - Learn more about [cgroup drivers](/docs/setup/production-environment/container-runtimes#cgroup-drivers) --> - 进一步了解 [cgroups](https://man7.org/linux/man-pages/man7/cgroups.7.html) - 进一步了解[容器运行时](/zh-cn/docs/concepts/architecture/cri) - 进一步了解 [cgroup 驱动](/zh-cn/docs/setup/production-environment/container-runtimes#cgroup-drivers) </ins>

This is a Feature Request I would like to translate this document, in order to prevent conflicts, open this issue /language zh /assign
/language zh
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /language zh-cn 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 zh
May I take it over if you have some problem. /assign
yesI agreethanks
/triage accepted


Question: [input_placeholder_email_address] other = "ईमेल ऐड्रेस" <ins> [javascript_required] other = "इस विषय को देखने के लिए जावास्क्रिप्ट [सक्रिय](https://www.enable-javascript.com/) होना चाहिए।" </ins> [latest_release] other = "नवीनतम रिलीज़:"

Updated with new strings from Didn't remove any strings from , even if they're missing 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
/assign
/language hi
Completed.


Question: <del> --- title: 역할과 책임 content_type: concept weight: 10 --- <!-- overview --> 누구나 쿠버네티스에 기여할 수 있다. SIG Docs에 대한 기여가 커짐에 따라, 커뮤니티의 다양한 멤버십을 신청할 수 있다. 이러한 역할을 통해 커뮤니티 내에서 더 많은 책임을 질 수 있다. 각 역할마다 많은 시간과 노력이 필요하다. 역할은 다음과 같다. - 모든 사람: 쿠버네티스 문서에 정기적으로 기여하는 기여자 - 멤버: 이슈를 할당, 심사하고 풀 리퀘스트에 대한 구속력 없는 리뷰를 제공할 수 있다. - 리뷰어: 문서의 풀 리퀘스트에 대한 리뷰를 리딩할 수 있으며 변경 사항에 대한 품질을 보증할 수 있다. - 승인자: 문서에 대한 리뷰를 리딩하고 변경 사항을 병합할 수 있다 <!-- body --> ## 모든 사람 GitHub 계정을 가진 누구나 쿠버네티스에 기여할 수 있다. SIG Docs는 모든 새로운 기여자를 환영한다! 모든 사람은 다음의 작업을 할 수 있다. - [`kubernetes/website`](https://github.com/kubernetes/website)를 포함한 모든 [쿠버네티스](https://github.com/kubernetes/) 리포지터리에서 이슈를 올린다. - 풀 리퀘스트에 대해 구속력 없는 피드백을 제공한다. - 현지화에 기여한다. - [슬랙](http://slack.k8s.io/) 또는 [SIG docs 메일링 리스트](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)에 개선을 제안한다. [CLA에 서명](/ko/docs/contribute/new-content/overview/#sign-the-cla) 후에 누구나 다음을 할 수 있다. - 기존 콘텐츠를 개선하거나, 새 콘텐츠를 추가하거나, 블로그 게시물 또는 사례연구 작성을 위해 풀 리퀘스트를 연다. - 다이어그램, 그래픽 자산 그리고 포함할 수 있는 스크린캐스트와 비디오를 제작한다. 자세한 내용은 [새로운 콘텐츠 기여하기](/ko/docs/contribute/new-content/)를 참고한다. ## 멤버 멤버는 `kubernetes/website` 에 여러 개의 풀 리퀘스트를 제출한 사람이다. 멤버는 [쿠버네티스 GitHub 조직](https://github.com/kubernetes)의 회원이다. 멤버는 다음의 작업을 할 수 있다. - [모든 사람](#모든-사람)에 나열된 모든 것을 한다. - 풀 리퀘스트에 `/lgtm` 코멘트를 사용하여 LGTM(looks good to me) 레이블을 추가한다. {{< note >}} `/lgtm` 사용은 자동화를 트리거한다. 만약 구속력 없는 승인을 제공하려면, 단순히 "LGTM" 코멘트를 남기는 것도 좋다! {{< /note >}} - `/hold` 코멘트를 사용하여 풀 리퀘스트에 대한 병합을 차단한다. - `/assign` 코멘트를 사용하여 풀 리퀘스트에 리뷰어를 지정한다. - 풀 리퀘스트에 구속력 없는 리뷰를 제공한다. - 자동화를 사용하여 이슈를 심사하고 분류한다. - 새로운 기능에 대한 문서를 작성한다. ### 멤버 되기 최소 5개의 실질적인 풀 리퀘스트를 제출하고 다른 [요구 사항](https://github.com/kubernetes/community/blob/master/community-membership.md#member)을 충족시킨 후, 다음의 단계를 따른다. 1. 멤버십을 [후원](/docs/contribute/advanced#sponsor-a-new-contributor)해줄 두 명의 [리뷰어](#리뷰어) 또는 [승인자](#승인자)를 찾는다. [슬랙의 #sig-docs 채널](https://kubernetes.slack.com) 또는 [SIG Docs 메일링 리스트](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)에서 후원을 요청한다. {{< note >}} SIG Docs 멤버 개인에게 직접 email을 보내거나 슬랙 다이렉트 메시지를 보내지 않는다. 반드시 지원서를 제출하기 전에 후원을 요청해야 한다. {{< /note >}} 1. [`kubernetes/org`](https://github.com/kubernetes/org/) 리포지터리에 GitHub 이슈를 등록한다. **Organization Membership Request** 이슈 템플릿을 사용한다. 1. 후원자에게 GitHub 이슈를 알린다. 다음 중 하나를 수행할 수 있다. - 이슈에서 후원자의 GitHub 사용자 이름을 코멘트로 추가한다. (`@<GitHub-username>`) - 슬랙 또는 이메일을 사용해 이슈 링크를 후원자에게 보낸다. 후원자는 `+1` 투표로 여러분의 요청을 승인할 것이다. 후원자가 요청을 승인하면, 쿠버네티스 GitHub 관리자가 여러분을 멤버로 추가한다. 축하한다! 만약 멤버십이 수락되지 않으면 피드백을 받게 될 것이다. 피드백의 내용을 해결한 후, 다시 지원하자. 1. 여러분의 이메일 계정으로 수신된 쿠버네티스 GitHub 조직으로의 초대를 수락한다. {{< note >}} GitHub은 초대를 여러분 계정의 기본 이메일 주소로 보낸다. {{< /note >}} ## 리뷰어 리뷰어는 열린 풀 리퀘스트를 리뷰할 책임이 있다. 멤버 피드백과는 달리, 여러분은 리뷰어의 피드백을 반드시 해결해야 한다. 리뷰어는 [@kubernetes/sig-docs-{language}-reviews](https://github.com/orgs/kubernetes/teams?query=sig-docs) GitHub 팀의 멤버이다. 리뷰어는 다음의 작업을 수행할 수 있다. - [모든 사람](#모든-사람)과 [멤버](#멤버)에 나열된 모든 것을 수행한다. - 풀 리퀘스트 리뷰와 구속력 있는 피드백을 제공한다. {{< note >}} 구속력 없는 피드백을 제공하려면, 코멘트에 "선택 사항: "과 같은 문구를 접두어로 남긴다. {{< /note >}} - 코드에서 사용자 화면 문자열 편집 - 코드 코멘트 개선 여러분은 SIG DOcs 리뷰어이거나, 특정 주제 영역의 문서에 대한 리뷰어일 수 있다. ### 풀 리퀘스트에 대한 리뷰어 할당 자동화 시스템은 모든 풀 리퀘스트에 대해 리뷰어를 할당한다. `/assign [@_github_handle]` 코멘트를 남겨 특정 사람에게 리뷰를 요청할 수 있다. 지정된 리뷰어가 PR에 코멘트를 남기지 않는다면, 다른 리뷰어가 개입할 수 있다. 필요에 따라 기술 리뷰어를 지정할 수도 있다. ### `/lgtm` 사용하기 LGTM은 "Looks good to me"의 약자이며 풀 리퀘스트가 기술적으로 정확하고 병합할 준비가 되었음을 나타낸다. 모든 PR은 리뷰어의 `/lgtm` 코멘트가 필요하고 병합을 위해 승인자의 `/approve` 코멘트가 필요하다. 리뷰어의 `/lgtm` 코멘트는 구속력 있고 자동화 시스템이 `lgtm` 레이블을 추가하도록 트리거한다. ### 리뷰어 되기 [요건](https://github.com/kubernetes/community/blob/master/community-membership.md#reviewer)을 충족하면, SIG Docs 리뷰어가 될 수 있다. 다른 SIG의 리뷰어는 SIG Docs의 리뷰어 자격에 반드시 별도로 지원해야 한다. 지원하려면, 다음을 수행한다. 1. `kubernetes/website` 리포지터리 내 [OWNERS_ALIASES](https://github.com/kubernetes/website/blob/master/OWNERS) 파일의 섹션에 여러분의 GitHub 사용자 이름을 추가하는 풀 리퀘스트를 연다. {{< note >}} 자신을 추가할 위치가 확실하지 않으면, `sig-docs-ko-reviews` 에 추가한다. {{< /note >}} 1. PR을 하나 이상의 SIG-Docs 승인자(`sig-docs-{language}-owners` 에 나열된 사용자 이름)에게 지정한다. 승인되면, SIG Docs 리더가 적당한 GitHub 팀에 여러분을 추가한다. 일단 추가되면, [K8s-ci-robot](https://github.com/kubernetes/test-infra/tree/master/prow#bots-home)이 새로운 풀 리퀘스트에서 리뷰어로 여러분을 할당하고 제안한다. ## 승인자 승인자는 병합하기 위해 풀 리퀘스트를 리뷰하고 승인한다. 승인자는 [@kubernetes/sig-docs-{language}-owners](https://github.com/orgs/kubernetes/teams/?query=sig-docs) GitHub 팀의 멤버이다. 승인자는 다음의 작업을 할 수 있다. - [모든 사람](#모든-사람), [멤버](#멤버) 그리고 [리뷰어](#리뷰어) 하위의 모든 목록을 할 수 있다. - 코멘트에 `/approve` 를 사용해서 풀 리퀘스트를 승인하고, 병합해서 기여자의 컨텐츠를 게시한다. - 스타일 가이드 개선을 제안한다. - 문서 테스트 개선을 제안한다. - 쿠버네티스 웹사이트 또는 다른 도구 개선을 제안한다. PR에 이미 `/lgtm` 이 있거나, 승인자도 `/lgtm` 코멘트를 남긴다면, PR은 자동으로 병합된다. SIG Docs 승인자는 추가적인 기술 리뷰가 필요치 않는 변경에 대해서만 `/lgtm` 을 남겨야 한다. ### 풀 리퀘스트 승인 승인자와 SIG Docs 리더는 website 리포지터리로 풀 리퀘스트를 병합할 수 있는 유일한 사람들이다. 이것은 특정한 책임이 따른다. - 승인자는 PR들을 리포지터리에 병합하는 `/approve` 명령을 사용할 수 있다. {{< warning >}} 부주의한 머지로 인해 사이트를 파괴할 수 있으므로, 머지할 때에 그 의미를 확인해야 한다. {{< /warning >}} - 제안된 변경이 [컨트리뷰션 가이드 라인](/docs/contribute/style/content-guide/#contributing-content)에 적합한지 확인한다. 질문이 생기거나 확실하지 않다면 자유롭게 추가 리뷰를 요청한다. - PR을 `/approve` 하기 전에 Netlify 테스트 결과를 검토한다. <img src="/images/docs/contribute/netlify-pass.png" width="75%" alt="승인 전에 반드시 Netlify 테스트를 통과해야 한다" /> - 승인 전에 PR에 대한 Netlify 프리뷰 페이지를 방문하여, 제대로 보이는지 확인한다. - 주간 로테이션을 위해 [PR Wrangler 로테이션 스케줄](https://github.com/kubernetes/website/wiki/PR-Wranglers)에 참여한다. SIG Docs는 모든 승인자들이 이 로테이션에 참여할 것으로 기대한다. 자세한 내용은 [PR 랭글러(PR wrangler)](/ko/docs/contribute/participating/pr-wranglers/)를 참고한다. ## 승인자 되기 [요구 사항](https://github.com/kubernetes/community/blob/master/community-membership.md#approver)을 충족하면 SIG Docs 승인자가 될 수 있다. 다른 SIG의 승인자는 SIG Docs의 승인자 자격에 대해 별도로 신청해야 한다. 지원하려면 다음을 수행한다. 1. `kubernetes/website` 리포지터리 내 [OWNERS_ALIASES](https://github.com/kubernetes/website/blob/master/OWNERS) 파일의 섹션에 자신을 추가하는 풀 리퀘스트를 연다. {{< note >}} 자신을 추가할 위치가 확실하지 않으면, `sig-docs-ko-owners` 에 추가한다. {{< /note >}} 2. PR에 한 명 이상의 현재 SIG Docs 승인자를 지정한다. 승인되면, SIG Docs 리더가 적당한 GitHub 팀에 여러분을 추가한다. 일단 추가되면, [@k8s-ci-robot](https://github.com/kubernetes/test-infra/tree/master/prow#bots-home)이 새로운 풀 리퀘스트에서 승인자로 여러분을 할당하고 제안한다. ## {{% heading "whatsnext" %}} - 모든 승인자가 교대로 수행하는 역할인 [PR 랭글러](/ko/docs/contribute/participating/pr-wranglers)에 대해 읽어보기 </del>

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 is a typo in filename of roles-and- file. Proposed Solution: Rename roles-and- instead of roles-and- Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ko
/assign


Question: </tr> </tbody> </table>  No newline at end of file

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: According to and , so updated the generator and opened a PR which replaces most of string with , but and remain in these files: - Proposed Solution: Maybe we need to check/update the generator again, and then generate references again. Or, if the generator is fine, then we might update those files manually. Page to Update: ,,- ,,- ,meta/v1.Duration,-cacheDuration%20indicates%20the
for kubeadm, the change ~must~ can be done here: but we are in code freeze for 1.24, so let's wait until code freeze is lifted (19th of April) /sig cluster-lifecycle
/triage accepted
/sig node
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 /assign
/reopen The kubeadm reference is still on its way to be regenerated. The kubelet credential providers one is yet to be fixed.
Reopened this issue. <detailsIn response to : /reopen The kubeadm reference is still on its way to be regenerated. The kubelet credential providers one is yet to be fixed. 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
But I didn't find the link in this file . ,meta/v1.Duration,-cacheDuration%20indicates%20the page points to There are the only links that still exist in this directory : // For semantics around ctx use and closing/ending streaming RPCs, please refer to for example (Code generated by protoc-gen-gogo.

DO NOT EDIT.) If these links need to be updated, they need to be updated in or repository. This part of the update should be beyond the scope of Kubernetes.


Question: <ins> --- title: Define Dependent Environment Variables content_type: task weight: 20 --- <!-- overview --> This page shows how to define dependent environment variables for a container in a Kubernetes Pod. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} <!-- steps --> ## Define an environment dependent variable for a container When you create a Pod, you can set dependent environment variables for the containers that run in the Pod. To set dependent environment variables, you can use $(VAR_NAME) in the `value` of `env` in the configuration file. In this exercise, you create a Pod that runs one container. The configuration file for the Pod defines an dependent environment variable with common usage defined. Here is the configuration manifest for the Pod: {{< codenew file="pods/inject/dependent-envars.yaml" >}} 1. Create a Pod based on that manifest: ```shell kubectl apply -f https://k8s.io/examples/pods/inject/dependent-envars.yaml ``` ``` pod/dependent-envars-demo created ``` 2. List the running Pods: ```shell kubectl get pods dependent-envars-demo ``` ``` NAME                      READY     STATUS    RESTARTS   AGE dependent-envars-demo     1/1       Running   0          9s ``` 3. Check the logs for the container running in your Pod: ```shell kubectl logs pod/dependent-envars-demo ``` ``` UNCHANGED_REFERENCE=$(PROTOCOL)://172.17.0.1:80 SERVICE_ADDRESS=https://172.17.0.1:80 ESCAPED_REFERENCE=$(PROTOCOL)://172.17.0.1:80 ``` As shown above, you have defined the correct dependency reference of `SERVICE_ADDRESS`, bad dependency reference of `UNCHANGED_REFERENCE` and skip dependent references of `ESCAPED_REFERENCE`. When an environment variable is already defined when being referenced, the reference can be correctly resolved, such as in the `SERVICE_ADDRESS` case. When the environment variable is undefined or only includes some variables, the undefined environment variable is treated as a normal string, such as `UNCHANGED_REFERENCE`. Note that incorrectly parsed environment variables, in general, will not block the container from starting. The `$(VAR_NAME)` syntax can be escaped with a double `$`, ie: `$$(VAR_NAME)`. Escaped references are never expanded, regardless of whether the referenced variable is defined or not. This can be seen from the `ESCAPED_REFERENCE` case above. ## {{% heading "whatsnext" %}} * Learn more about [environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/). * See [EnvVarSource](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#envvarsource-v1-core). </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 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Why is this needed If the environment variables started by the pod are cyclically dependent and mutually referenced, the resulting environment variable values will not be what we expected. At present, there is no detailed description about this in the official document, it is recommended to reopen a page to describe it in detail Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/kind feature
/assign


Question: ## Node topology <del> {{< feature-state state="beta" for_k8s_version="v1.18" >}} </del> <ins> {{< feature-state state="stable" for_k8s_version="v1.27" >}} </ins> If you have enabled the `TopologyManager` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/), then

This is a Bug Report <!--Required Information--Problem: The of is mentioned under , which is wrong, As per mention in the the correct Feature state for is . Here is Upstream PR for it: Proposed Solution: Change the Feature State of from to . Page to Update:
/sig node /assign /triage accepted
Fixed it here:
/retitle Wrong feature state shown for TopologyManager
/language en


Question: 英語 | 日本語 --------- | --------- <del> cluster|クラスター orchestrate(動詞)|オーケストレーションする Persistent Volume|KubernetesリソースとしてのPersistentVolumeはママ表記、一般的な用語としての場合は、永続ボリューム Deployment/Deploy|KubernetesリソースとしてのDeploymentはママ表記、一般的な用語としてのdeployの場合は、デプロイ </del> Addon/Add-on|アドオン <del> Quota|クォータ For more information|さらなる情報(一時的) prefix | プレフィックス container | コンテナ directory | ディレクトリ </del> <ins> Aggregation Layer | アグリゲーションレイヤー architecture | アーキテクチャ </ins> binary | バイナリ <ins> cluster|クラスター community | コミュニティ container | コンテナ </ins> controller | コントローラー <del> operator | オペレーター Aggregation Layer | アグリゲーションレイヤー </del> <ins> Deployment/Deploy|KubernetesリソースとしてのDeploymentはママ表記、一般的な用語としてのdeployの場合は、デプロイ directory | ディレクトリ For more information|さらなる情報(一時的) GitHub | GitHub (ママ表記) </ins> Issue | Issue (ママ表記) <ins> operator | オペレーター orchestrate(動詞)|オーケストレーションする Persistent Volume|KubernetesリソースとしてのPersistentVolumeはママ表記、一般的な用語としての場合は、永続ボリューム prefix | プレフィックス </ins> Pull Request | Pull Request (ママ表記) <del> GitHub | GitHub (ママ表記) </del> <ins> Quota|クォータ </ins> registry | レジストリ <del> architecture | アーキテクチャ </del> secure | セキュア <del> stacked | 積層(例: stacked etcd clusterは積層etcdクラスター) </del> a set of ~ | ～の集合 <del> community | コミュニティ </del> <ins> stacked | 積層(例: stacked etcd clusterは積層etcdクラスター) </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 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --I'd like to sort "", common words alphabetically in Japanese localization guide. Why is this needed It'll be easier to find a word in the list. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign


Question:
apiVersion: kubeadm.k8s.io/v1beta4 kind: UpgradeConfiguration apply:   	...      ...  diff:   	...      ...  node:   	...      ...  plan:   	...      ...

The UpgradeConfiguration structure includes a few substructures that only apply to different subcommands of kubeadm upgrade. For example, the apply substructure will be used with the kubeadm upgrade apply subcommand and all other substructures will be ignored in such a case.

The indentation of the example configuration is messy. !
/kind bug /language en page:
Also Consider to remove the exist in the same page under . Note: This page is automatically generated, you are not allowed to directly change the documentation page.
/retitle Messy indentation on kubeadm config reference page
/priority backlog We'd prioritize other improvements over this one. /triage accepted
/assign This is because the Golang source code contains TAB characters instead of SPACEs as a convention, and those TABs are messing up the YAML snippet. I'll work on this.
PR sent for website. PR sent for the generator.


Question: title: ConfigMap id: configmap date: 2018-04-12 <del> full_link: /docs/tasks/configure-pod-container/configure-pod-configmap/ </del> <ins> full_link: /docs/concepts/configuration/configmap/ </ins> short_description: > <del> An API object used to store non-confidential data in key-value pairs. Can be consumed as environment variables, command-line arguments, or config files in a volume. </del> <ins> An API object used to store non-confidential data in key-value pairs. Can be consumed as environment variables, command-line arguments, or configuraton files in a volume. </ins> aka: tags: - core-object --- <del> An API object used to store non-confidential data in key-value pairs. Can be consumed as environment variables, command-line arguments, or config files in a {{< glossary_tooltip text="volume" term_id="volume" >}}. </del> <ins> An API object used to store non-confidential data in key-value pairs. {{< glossary_tooltip text="Pods" term_id="pod" >}} can consume ConfigMaps as environment variables, command-line arguments, or as configuration files in a {{< glossary_tooltip text="volume" term_id="volume" >}}. </ins> <!--more--> <del> Allows you to decouple environment-specific configuration from your {{< glossary_tooltip text="container images" term_id="container" >}}, so that your applications are easily portable. When storing confidential data use a [Secret](/docs/concepts/configuration/secret/). </del> <ins> A ConfigMap allows you to decouple environment-specific configuration from your {{< glossary_tooltip text="container images" term_id="image" >}}, so that your applications are easily portable. </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 write a new concept page: (or possibly ) If the does not work as the page overview, consider tweaking the glossary entry so that it does. Then use a Hugo shortcode. Why is this needed ConfigMap is a core object type for Kubernetes; as such, it needs documenting properly. Comments Consider using as an example for page structure. It's better to put Task-style documentation in task pages such as and then hyperlink to those from the Concept page. Also see: /docs/user-guide/configmap need more details on ConfigMap updates Actionable user-guide/configmap does not document self-updating It's unclear what happens when ConfigMap is changed Need doc on using ConfigMap updates Wanted: ConfigMap Rollout Options Doc
/language en /sig apps
/priority important-longterm
This is worth prioritizing /priority important-soon
/remove-priority important-longterm
/project Doc Sprints
/assign
/unassign
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
Still worth documenting /remove-lifecycle stale
/reopen let's collaborate on this!


Question: if [ -d "$1" ] ; then SYNCED=1 for f in `find $1 -name "*.md"` ; do <del> EN_VERSION=`echo $f | sed "s/content/..//content/en//g"` </del> <ins> EN_VERSION=`echo $f | sed "s/content/.{2,5}//content/en//g"` </ins> if [ ! -e $EN_VERSION ]; then echo -e "**removed**t$EN_VERSION" SYNCED=0

This is a Bug Report cannot sync files under correctly. This problem should exist with $LOCALIZED more than 2 characters. When happened when zh -zh-cn see <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Proposed Solution:** needs to be updated to <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/cc /language zh
/triage accepted
I found this problem when reviewing this PR , the commit time of the version is later than the version, but did not correctly find the difference between the 2 versions.
nice catch!
When the script was developed, I was only focusing on markdown files.


Question: <!-- body --> <del> ## सीखने का वातावरण </del> <ins> ## सीखने का वातावरण  {#learning-environment} </ins> यदि आप कुबेरनेट्स सीख रहे हैं, तो कुबेरनेट्स समुदाय द्वारा समर्थित टूल का उपयोग करें, या स्थानीय मशीन पर कुबेरनेट्स क्लस्टर सेटअप करने के लिए इकोसिस्टम में उपलब्ध टूल का उपयोग करें। [इंस्टॉल टूल्स](/hi/docs/tasks/tools/) देखें। <del> ## प्रोडक्शन वातावरण </del> <ins> ## प्रोडक्शन वातावरण   {#production-environment} </ins> [प्रोडक्शन वातावरण](/hi/docs/setup/production-environment/) के लिए समाधान का मूल्यांकन करते समय, विचार करें कि कुबेरनेट्स क्लस्टर के किन पहलुओं (या _abstractions_) का संचालन आप स्वयं प्रबंधित करना चाहते हैं और किसे आप एक प्रदाता को सौंपना पसंद करते हैं।

The link in the page is not correct. THe link for and under is not correct . Page to be update: It should be updated with the corrct link.
/kind bug
/language hi /sig docs
Page related issue
Hey Can you more elaborate this issue, I don't see any vulnerability/issue there!!
Hi , The links which were provided should be redirecting to the particular path but it is redirecting to the whole page not particular heading.
In hindi doc home page we have एक कुबेरनेट्स क्लस्टर सेटअप करें which is having two link name as सीखने का वातावरण and प्रोडक्शन वातावरण whose link should be and which should redirect to the proper heading.
/assign
Hye ! I find it interesting . Can you assign this issue to me?
it still needs triage and I checked the issue already and found that it's not a valid problem!
Alright
thanks for showing your interest on volunteering! We do have some where help will be much appreciated
/priority awaiting-more-evidence /retitle [hi] Broken link on Hindi docs home page
/triage accepted
Thank you for the report, ! If we need the links to work correctly and redirect to the relevant sections, [सीखने का वातावरण] should redirect to (#स-खन-क-व-त-वरण) AND [प्रोडक्शन वातावरण] should redirect to (#प-र-डक-शन-व-त-वरण) per how the navigation is working on the website currently. This is because, as is evident from the above snippet, the section headers are not being rendered in the links correctly and is due to the difference in the scripts (English alphabet vs Devnagari) being used. More precisely, the vowels (अ - अ:) do not seem to make their way into the section header linking despite being rendered okay on the page.

HOWEVER The correct outcome is that: [सीखने का वातावरण] should redirect to (सीखने का वातावरण) AND [प्रोडक्शन वातावरण] should redirect to (प्रोडक्शन वातावरण) It is likely that other localizations using an alphabet/script that aren't similar to English are facing the same issues. For anyone wishing to take on this issue, a simple change in the link will not be the fix. Instead, the expectation is outlined below: Check with other localizations with an alphabet that's not similar to English how they're rendering their section headers & if they're facing the same problems. Some live localizations that I can think of are Chinese and Korean. If not, understand what are their workarounds to the problem. Bring back the results of the research to this issue and the Slack channel to see how we can implement it.
/retitle Section headers for Hindi localization aren't being rendered correctly leading to broken links
Wow, good issue to work on, taking this :) /assign
BTW, the channel in question is #sig-docs-localizations
I checked other localizations which are not in English, here is what i got Chinese: They have their section headers links in English ( e.g: ) check Korean: Section headers link in korean and it's working (e.g: check )Chinese: They are dealing with this problem by having their section header links in English ( check ) Korean: They are not facing this problem. (check ) To deal in hindi, my approach will be to use the same approach used in chinese i.e having the section header links in english.
the approach used by you is good and the PR raised has solved the issue. I think it would be good.


Question: ヘルプが必要な場合は、ターミナルウィンドウから`kubectl help`を実行してください。 <ins> ## クラスター内認証と名前空間のオーバーライド {#in-cluster-authentication-and-namespace-overrides} デフォルトでは、`kubectl`は最初にPod内で動作しているか、つまりクラスター内で動作しているかどうかを判断します。まず、`KUBERNETES_SERVICE_HOST`と`KUBERNETES_SERVICE_PORT`の環境変数を確認し、サービスアカウントのトークンファイルが`/var/run/secrets/kubernetes.io/serviceaccount/token`に存在するかどうかを確認します。3つともクラスター内で見つかった場合、クラスター内認証とみなされます。 後方互換性を保つため、クラスター内認証時に`POD_NAMESPACE`環境変数が設定されている場合には、サービスアカウントトークンのデフォルトの名前空間が上書きされます。名前空間のデフォルトに依存しているすべてのマニフェストやツールは、この影響を受けます。 **`POD_NAMESPACE`環境変数** `POD_NAMESPACE`環境変数が設定されている場合、名前空間に属するリソースのCLI操作は、デフォルトで環境変数の値になります。例えば、変数に`seattle`が設定されている場合、`kubectl get pods`は、`seattle`名前空間のPodを返します。これは、Podが名前空間に属するリソースであり、コマンドで名前空間が指定されていないためです。`kubectl api-resources`の出力を見て、リソースが名前空間に属するかどうかを判断してください。 明示的に`--namespace <value>`を使用すると、この動作は上書きされます。 **kubectlによるServiceAccountトークンの処理方法** 以下の条件がすべて成立した場合、 * `/var/run/secrets/kubernetes.io/serviceaccount/token`にマウントされたKubernetesサービスアカウントのトークンファイルがある * `KUBERNETES_SERVICE_HOST`環境変数が設定されている * `KUBERNETES_SERVICE_PORT`環境変数が設定されている * kubectlコマンドラインで名前空間を明示的に指定しない kubectlはクラスター内で実行されているとみなして、そのServiceAccountの名前空間(これはPodの名前空間と同じです)を検索し、その名前空間に対して機能します。これは、クラスターの外の動作とは異なります。kubectlがクラスターの外で実行され、名前空間を指定しない場合、kubectlコマンドは、クライアント構成の現在のコンテキストに設定されている名前空間に対して動作します。kubectlのデフォルトの名前空間を変更するには、次のコマンドを使用できます。 ```shell kubectl config set-context --current --namespace=<namespace-name> ``` </ins> ## 操作 以下の表に、`kubectl`のすべての操作の簡単な説明と一般的な構文を示します。

This is a Feature Request What would you like to be Add the describe of in-cluster to kubectl document in Japanese. The target file is Why is this needed There is that describe in English. Comments /language ja /assign
/triage accepted


Question: to track changes. That mechanism has been superseded by [Server-side apply](/docs/reference/using-api/server-side-apply/). <ins> ### kubectl.kubernetes.io/restartedAt {#kubectl-k8s-io-restart-at} Type: Annotation Example: `kubectl.kubernetes.io/restartedAt: "2024-06-21T17:27:41Z"` Used on: Deployment, ReplicaSet, StatefulSet, DaemonSet, Pod This annotation contains the latest restart time of a resource (Deployment, ReplicaSet, StatefulSet or DaemonSet), where kubectl triggered a rollout in order to force creation of new Pods. The command `kubectl rollout restart <RESOURCE>` triggers a restart by patching the template metadata of all the pods of resource with this annotation. In above example the latest restart time is shown as 21st June 2024 at 17:27:41 UTC. You should not assume that this annotation represents the date / time of the most recent update; a separate change could have been made since the last manually triggered rollout. If you manually set this annotation on a Pod, nothing happens. The restarting side effect comes from how workload management and Pod templating works. </ins> ### endpoints.kubernetes.io/over-capacity 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 defined an annotation, . For example, this annotation is set during rolling restarts. That annotation is unregistered because it doesn't appear inside Proposed Solution: Register the annotation, by documenting it in… Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig architecture /sig cli /language en
/assign
/lgtm /assign
I am happy to work on this issue once triage accepted, thanks.
Unassigning myself as PR is already raised by
/triage accepted
/priority backlog
PR that is working on this issue .
PRs to fix this are welcome. what are your plans for ?
hi are you still working on the issue?
How about this
Let me know if no one's working on the issue currently then i can raise this PR. I already have this in my local branch
a PR is welcome if you have code for it, nearly always. It's also polite to try to liaise with anyone else who's mentioned that they plan to do work on the same issue. In this case, you can see things have gone quiet. Opening a PR here can't reasonably be seen as thoughtlessly barging in.
Thanks for confirmation .
Raised the PR for this annotation, please take a look. I'll be happy to improve it based on your reviews.


Question: ### Reclaim Policy PersistentVolumes that are dynamically created by a StorageClass will have the <del> reclaim policy specified in the `reclaimPolicy` field of the class, which can be </del> <ins> [reclaim policy](/docs/concepts/storage/persistent-volumes/#reclaiming) specified in the `reclaimPolicy` field of the class, which can be </ins> either `Delete` or `Retain`. If no `reclaimPolicy` is specified when a StorageClass object is created, it will default to `Delete`.

There's a section for ReclaimPolicy, which states that this can be or . It is not clear as to what those states mean, there's NO explanation. I was researching how to expand disk, and one guide says that the must be , but I cannot find reference as to what this means. My expectation was that these would be explained what they mean, rather than this is the only do option.
Page related to issue: /retitle Lack of explanation for options - Retain and Delete /language en
These concepts are well explained in 'concepts/storage/persistent-'. Maybe a pointer or two suffices?
Please refer link here you will find the brief introduction about the retain or delete. I think this link will be helpful to understand.
/assign
/triage accepted


Question: * Read about [Ingress](/docs/concepts/services-networking/ingress/), which exposes HTTP and HTTPS routes from outside the cluster to Services within your cluster. <del> * Read about [Gateway](https://gateway-api.sigs.k8s.io/), an extension to </del> <ins> * Read about [Gateway](/docs/concepts/services-networking/gateway/), an extension to </ins> Kubernetes that provides more flexibility than Ingress. For more context, read the following:

This is a Feature Request What would you like to be High level documentation for Gateway API with links out to https://gateway- This should include the following: new "Gateway API" page between Service and Ingress in This should provide a high level overview of Gateway API, with a focus on content that is unlikely to become stale. This can likely take some content from both https://gateway- and https://gateway- and would help increase the discoverability of Gateway API. the "Ingress" page to note that the API is effectively frozen and all new features are being to Gateway API (with a corresponding link to the page by 1). the section on the "Service" page that references Ingress and Gateway API to give more prominence to Gateway API. Why is this needed With the upcoming graduation of Gateway API to GA (x-ref ), it's past time to cover it in Kubernetes docs. Comments I'd previously talked with about this at a high level, but definitely let me know if you've got any suggestions for how we can scope/adjust this differently. /sig network /assign
checkout the gateway API in the section and look out for the bugs
/triage accepted /priority important-longterm
How about adding a short link eg that redirects (302) to https://gateway- ?
I'd put Service, Ingress, then Gateway - and leave it in that order until most new clusters include Gateway as an add-on.
Also see


Question:
{{ if not $is_valid }} {{ errorf "%q is not a valid feature-state, use one of %q" $state $valid_states }} {{ else }}
 {{ T "feature_state" }} {{T "feature_state_kubernetes_label" }} {{ $for_k8s_version }} [{{ $state }}]

 {{ T "feature_state" }} {{T "feature_state_kubernetes_label" }} {{ $for_k8s_version }} [{{ $state }}]
  {{ end }} {{- else -}}

This is a Bug Report <!--Required Information--Problem: Documentation layout issue in page under IngressClass scope Namespaced section, see following screenshot: <img width="912" alt="image" src=""Proposed Solution: I would like to create a PR to fix it, the solution is to remove and outside of template Page to Update: Documentation layout issue in Ingress.


Question: ## Kubeadm <del> [`kubeadm`](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/)은 물리적 환경, 클라우드 서버, 또는 가상머신 상에서 안전한 쿠버네티스를 쉽게 프로비저닝하기 위한 커맨드라인 툴이다(현재는 알파 상태). </del> <ins> [`kubeadm`](/ko/docs/setup/production-environment/tools/kubeadm/install-kubeadm/)은 물리적 환경, 클라우드 서버, 또는 가상머신 상에서 안전한 쿠버네티스를 쉽게 프로비저닝하기 위한 커맨드라인 툴이다(현재는 알파 상태). </ins> ## Minikube

<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: In , the link href is (English). The of is recently in . Proposed Solution: In , Before: After: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/assign
/language ko
/triage accepted
Resolved by


On the Kubernetes case studies page (), certain company icons are not visible. !
/retitle Some company logos not rendering on "Case Studies" page /kind bug
I would like to fix this. /assign
We should investigate and fix this. /priority backlog /triage accepted
/area web-development


Question:
 {{ partial "head.html" . }}         {{ partial "navbar.html" . }}

   {{ block "announcement" . }} {{ if .IsHome }}

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: Navbar prevents search input field from being clicked on Can reproduce on Firefox, Chrome on latest builds Proposed Solution: Remove navbar from search page Page to Update: !
is not supposed to look like that screenshot /kind bug /priority critical-urgent /area web-development Thanks for reporting this.
/triage accepted
/retitle Navbar prevents search inputfield from being clicked
Actually /retitle Search page rendering incorrectly


Question: ## APIグループ <del> [API groups](https://git.k8s.io/community/contributors/design-proposals/api-machinery/api-group.md)で、KubernetesのAPIを簡単に拡張することができます。 </del> <ins> [API groups](https://git.k8s.io/design-proposals-archive/api-machinery/api-group.md)で、KubernetesのAPIを簡単に拡張することができます。 </ins> APIグループは、RESTパスとシリアル化されたオブジェクトの`apiVersion`フィールドで指定されます。 KubernetesにはいくつかのAPIグループがあります:

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. --We need to update some links in because these links are broken. True) False) True) False) Why is this needed These links are broken. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
About aggregator - is certainly correct, but we would like to match the English page first. You already did so in PR .
Thank you for your advice! The URL listed in the Issue was incorrect and has been corrected. As you said, PR already uses this URL.
/triage accepted


Question: For instructions on creating and working with cron jobs, and for an example of CronJob manifest, see [Running automated tasks with cron jobs](/docs/tasks/job/automated-tasks-with-cron-jobs).

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: can be set to any value, but . If it's set to any value less than 10s the CronJob will be never scheduled. Proposed Solution: Force the value to be always greater than 10, or warn people there are non-working values Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: 1.15.12
/kind cleanup /language en /triage accepted
Thanks
Relevant to
I recommend adding a warning. There is a v2 controller for CronJob arriving in Kubernetes v1.20 that may eventually honor any setting for ; however, we want to document the shortcoming right now. Specifically I would add a callout, with text similar to: /good-first-issue /sig apps
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 : I recommend adding a warning. There is a v2 controller for CronJob arriving in Kubernetes v1.20 that may eventually honor any setting for ; however, we want to document the shortcoming right now. if is set to a value less than 10 seconds then the CronJob may not be scheduled. /sig apps 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


Question: <ins> --- title: Instalar y Configurar kubectl en Linux content_type: task weight: 10 --- ## {{% heading "prerequisites" %}} Se debe utilizar la versión de kubectl con una minor versión de diferencia con su cluster. Por ejemplo, un cliente con versión v{{< skew currentVersion >}} se puede comunicar con los siguientes versiones de plano de control v{{< skew currentVersionAddMinor -1 >}}, v{{< skew currentVersionAddMinor 0 >}}, and v{{< skew currentVersionAddMinor 1 >}}. Utilizar la última versión compatible de kubectl evita posibles errores. ## Instalar kubectl en Linux Existen los siguientes métodos para instalar kubectl en Linux: # TODO -> tengo dudas si los links dentro del documento van a funcionar si los nombres no son exactamente iguales! - [Instalación del binario para Linux de kubectl con Curl](#install-kubectl-binary-with-curl-on-linux) - [Instalación mediante el administrador de paquetes nativo](#install-using-native-package-management) - [Instalación usando otro administrador de paquetes](#install-using-other-package-management) ### Instalación del binario para Linux de kubectl con Curl 1. Descargar la última versión con el siguiente comando: {{< tabs name="download_binary_linux" >}} {{< tab name="x86-64" codelang="bash" >}} curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl" {{< /tab >}} {{< tab name="ARM64" codelang="bash" >}} curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/arm64/kubectl" {{< /tab >}} {{< /tabs >}} {{< note >}} Para Descargar una versión específica reemplazar la siguiente parte del comando con la versión que desea instalar `$(curl -L -s https://dl.k8s.io/release/stable.txt)` Por ejemplo, para descargar la versión {{< skew currentPatchVersion >}} en linux x86-64: ```bash curl -LO https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/linux/amd64/kubectl ``` Y para Linux ARM64: ```bash curl -LO https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/linux/arm64/kubectl ``` {{< /note >}} 1. Validación del binario (paso opcional) Descargar el archivo checksum: {{< tabs name="download_checksum_linux" >}} {{< tab name="x86-64" codelang="bash" >}} curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl.sha256" {{< /tab >}} {{< tab name="ARM64" codelang="bash" >}} curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/arm64/kubectl.sha256" {{< /tab >}} {{< /tabs >}} Validar el binario de kubectl contra el archivo checksum: ```bash echo "$(cat kubectl.sha256)  kubectl" | sha256sum --check ``` Si es válido va a obtener la siguiente respuesta: ```console kubectl: OK ``` En caso de falla, `sha256` terminará con un estado diferente a cero con una salida similar a: ```console kubectl: FAILED sha256sum: WARNING: 1 computed checksum did NOT match ``` {{< note >}} Descargue la misma versión del binario y el checksum. {{< /note >}} 1. Instalar kubectl ```bash sudo install -o root -g root -m 0755 kubectl /usr/local/bin/kubectl ``` {{< note >}} Si no tiene acceso root en el sistema donde se busca instalar, se puede colocar el binario kubectl en el directorio `~/.local/bin`: ```bash chmod +x kubectl mkdir -p ~/.local/bin mv ./kubectl ~/.local/bin/kubectl # Y después agregue el directorio ~/.local/bin a su $PATH ``` {{< /note >}} 1. Test para asegurar que la versión instalada está actualizada: ```bash kubectl version --client ``` Se puede utilizar lo siguiente para una vista detallada de la versión: ```cmd kubectl version --client --output=yaml ``` ### Instalación mediante el administrador de paquetes nativo {{< tabs name="kubectl_install" >}} {{% tab name="Debian-based distributions" %}} 1. Actualice el índice del paquete `apt`, luego instale los paquetes necesarios para Kubernetes: ```shell sudo apt-get update # apt-transport-https may be a dummy package; if so, you can skip that package sudo apt-get install -y apt-transport-https ca-certificates curl ``` 2. Descarge la llave pública firmada para los repositorios de Kubernetes. La misma llave firmada es usada para todos los repositorios por lo que se puede obviar la versión en la URL: ```shell curl -fsSL https://pkgs.k8s.io/core:/stable:/{{< param "version" >}}/deb/Release.key | sudo gpg --dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpg ``` 3. Agregar el repositorio apropiado de Kubernetes. Si usted quisiera una versión de Kubernetes diferente a {{< param "version" >}}, reemplace {{< param "version" >}} con la versión deseada en el siguiente comando: ```shell # Esto sobrescribe cualquier configuración existente en el archivo /etc/apt/sources.list.d/kubernetes.list echo 'deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/{{< param "version" >}}/deb/ /' | sudo tee /etc/apt/sources.list.d/kubernetes.list ``` {{< note >}} Para actualizar kubectl a una minor release diferente, se debe reemplazar la versión en el archivo `/etc/apt/sources.list.d/kubernetes.list` antes de ejecutar `apt-get update` y `apt-get upgrade`. Este procedimiento se describe con más detalle en [Cambiando el Repositorio de Kubernetes](/docs/tasks/administer-cluster/kubeadm/change-package-repository/). {{< /note >}} 4. Actualice el índice de `apt`, luego instale kubectl: ```shell sudo apt-get update sudo apt-get install -y kubectl ``` {{< note >}} En versiones anteriores a Debian 12 y Ubuntu 22.04 el directorio `/etc/apt/keyrings` no existe por defecto, puede ser creado usando el comando `sudo mkdir -m 755 /etc/apt/keyrings` {{< /note >}} {{% /tab %}} {{% tab name="Red Hat-based distributions" %}} 1. Agregar Kubernetes al repositorio `yum`. Si desea usar una versión de Kubernetes diferente a {{< param "version" >}}, reemplace {{< param "version" >}} con la versión deseada en el siguiente comando: ```bash # Lo siguiente reemplaza cualquier configuración existente en /etc/yum.repos.d/kubernetes.repo cat <<EOF | sudo tee /etc/yum.repos.d/kubernetes.repo [kubernetes] name=Kubernetes baseurl=https://pkgs.k8s.io/core:/stable:/{{< param "version" >}}/rpm/ enabled=1 gpgcheck=1 gpgkey=https://pkgs.k8s.io/core:/stable:/{{< param "version" >}}/rpm/repodata/repomd.xml.key EOF ``` {{< note >}} Para actualizar kubectl a otra versión será necesario modificar la versión en `/etc/yum.repos.d/kubernetes.repo` antes de ejecutar `yum update`. Este procedimiento se describe con más detalle en [Changing The Kubernetes Package Repository](/docs/tasks/administer-cluster/kubeadm/change-package-repository/). {{< /note >}} 2. Instalar kubectl utilizando `yum`: ```bash sudo yum install -y kubectl ``` {{% /tab %}} {{% tab name="SUSE-based distributions" %}} 1. Agregar Kubernetes al repositorio `zypper`. Si desea usar una versión de Kubernetes diferente a {{< param "version" >}}, reemplace {{< param "version" >}} con la versión deseada en el siguiente comando: ```bash # Lo siguiente reemplaza cualquier configuración existente en /etc/zypp/repos.d/kubernetes.repo cat <<EOF | sudo tee /etc/zypp/repos.d/kubernetes.repo [kubernetes] name=Kubernetes baseurl=https://pkgs.k8s.io/core:/stable:/{{< param "version" >}}/rpm/ enabled=1 gpgcheck=1 gpgkey=https://pkgs.k8s.io/core:/stable:/{{< param "version" >}}/rpm/repodata/repomd.xml.key EOF ``` {{< note >}} Para actualizar kubectl a otra versión será necesario modificar la versión en `/etc/zypp/repos.d/kubernetes.repo` antes de ejecutar `zypper update`. Este procedimiento se describe con más detalle en [Changing The Kubernetes Package Repository](/docs/tasks/administer-cluster/kubeadm/change-package-repository/). {{< /note >}} 2. Instalar kubectl usando `zypper`: ```bash sudo zypper install -y kubectl ``` {{% /tab %}} {{< /tabs >}} ### Instalación usando otro administrador de páquetes {{< tabs name="other_kubectl_install" >}} {{% tab name="Snap" %}} Si utiliza Ubuntu o alguna distribución que soporte el administrador de páquetes [snap](https://snapcraft.io/docs/core/install), kubectl esta disponible como una aplicación de [snap](https://snapcraft.io/). ```shell snap install kubectl --classic kubectl version --client ``` {{% /tab %}} {{% tab name="Homebrew" %}} Si utiliza [Homebrew](https://docs.brew.sh/Homebrew-on-Linux) en Linux, kubectl está disponible para su [instalación](https://docs.brew.sh/Homebrew-on-Linux#install). ```shell brew install kubectl kubectl version --client ``` {{% /tab %}} {{< /tabs >}} ## Verificar la configuración de kubectl {{< include "included/verify-kubectl.md" >}} ## Configuraciones opcionales y plugins de kubectl ### Habilitar el autocompletado en la shell Kubectl tiene soporte para autocompletar en Bash, Zsh, Fish y Powershell, lo que puede agilizar el tipeo. A continuación están los procedimientos para configurarlo en Bash, Fisch y Zsh. {{< tabs name="kubectl_autocompletion" >}} {{< tab name="Bash" include="included/optional-kubectl-configs-bash-linux.md" />}} {{< tab name="Fish" include="included/optional-kubectl-configs-fish.md" />}} {{< tab name="Zsh" include="included/optional-kubectl-configs-zsh.md" />}} {{< /tabs >}} ### Instalar el plugin `kubectl convert` {{< include "included/kubectl-convert-overview.md" >}} 1. Descargue la última versión con el siguiente comando: {{< tabs name="download_convert_binary_linux" >}} {{< tab name="x86-64" codelang="bash" >}} curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl-convert" {{< /tab >}} {{< tab name="ARM64" codelang="bash" >}} curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/arm64/kubectl-convert" {{< /tab >}} {{< /tabs >}} 1. Valide el binario (opcional) Descargue el checksum de kubectl-convert: {{< tabs name="download_convert_checksum_linux" >}} {{< tab name="x86-64" codelang="bash" >}} curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl-convert.sha256" {{< /tab >}} {{< tab name="ARM64" codelang="bash" >}} curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/arm64/kubectl-convert.sha256" {{< /tab >}} {{< /tabs >}} Ahora se puede validar el binario utilizando el checksum: ```bash echo "$(cat kubectl-convert.sha256) kubectl-convert" | sha256sum --check ``` Si es válido, la salida será: ```console kubectl-convert: OK ``` En caso de falla, `sha256` terminará con un estado diferente a cero con una salida similar a esta: ```console kubectl-convert: FAILED sha256sum: WARNING: 1 computed checksum did NOT match ``` {{< note >}} Descargue la misma versión del binario y del checksum. {{< /note >}} 1. Instalar kubectl-convert ```bash sudo install -o root -g root -m 0755 kubectl-convert /usr/local/bin/kubectl-convert ``` 1. Verificar si el plugin fue instalado correctamente ```shell kubectl convert --help ``` Si no visualiza ningún error quiere decir que el plugin fue instalado correctamente. 1. Después de instalar el plugin elimine los archivos de instalación: ```bash rm kubectl-convert kubectl-convert.sha256 ``` ## {{% heading "whatsnext" %}} {{< include "included/kubectl-whats-next.md" >}} </ins>

This is a Feature Request What would you like to be Localize to Spanish Why is this needed There is no Spanish localization for this file. Comments /triage accepted /kind feature /language es /sig docs
/assign
Thanks for participating in the Kubernetes Website project. The Spanish translation team would like to help you with your contribution, so please share your goals and skills in order to help you better. We also encourage new contributors to participate in their native speaking language.
/unassign deepak4566
/assign
In the line 150 there is a link to There is the same link in line 185. This file is not available in the spanish directory.


Question: ## {{% heading "prerequisites" %}} <del> These instructions are for Kubernetes {{< skew currentVersion >}}. If you want to check the integrity of components for a different version of Kubernetes, check the documentation for that Kubernetes release. </del> You will need to have the following tools installed: - `cosign` ([install guide](https://docs.sigstore.dev/cosign/installation/)) - `curl` (often provided by your operating system) <ins> - `jq` ([download jq](https://stedolan.github.io/jq/download/)) </ins> ## Verifying binary signatures

This is a Feature Request After release, we don't need . We should update the instructions on the task to include verification using cosign 2.0 <!-- 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 <details<summaryverification using cosign 2.0</summaryAdd a note if cosign version < 2.0 </details<!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Why is this needed There are some breaking changes in cosign 2.0 and we should update the instruction for the verification of images. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/sig release /sig security /retitle Update page Verify Signed Kubernetes Artifacts for cosign 2.0 /kind bug /remove-kind feature /language en /triage accepted Thanks
:+1:
I can work on this /assign
Hey Are you still working on this issue? If not, can I work on this?
Haven't gotten to it as I expected to. Please feel free to work on it /unassign
/assign
FYI
Apologies for not being able to review the PR. I am going through University exams which is ending tomorrow. I just rushed through the changes that you made and you really did awesome work on this. I'll look more into this after the exams. Thanks for working on this.


Question: type will be deleted when its namespace is deleted and access to that resource type is controlled by authorization checks on the namespace scope. <ins> Note: core resources use `/api` instead of `/apis` and omit the GROUP path segment. Examples: * `/api/v1/namespaces` * `/api/v1/pods` * `/api/v1/namespaces/my-namespace/pods` * `/apis/apps/v1/deployments` * `/apis/apps/v1/namespaces/my-namespace/deployments` * `/apis/apps/v1/namespaces/my-namespace/deployments/my-deployment` </ins> You can also access collections of resources (for example: listing all Nodes). The following paths are used to retrieve collections and resources:

While reading Events to learn how to construct api urls I found that the instructions here do not cover how paths for core resources are constructed, mainly that they start with instead of . It hints at this with the example but it should be directly stated to be more clear. after rereading my original post let me me more clear. Core resources start with /api all other resources start with /apis I am asking for this destinction to be made more clear in the docs.
/wg api-expression /language en /triage accepted /priority backlog
/assign
after rereading my original post let me me more clear. Core resources start with /api all other resources start with /apis I am asking for this destinction to be made more clear in the docs.
would you be willing to edit the original description that you wrote for the issue, to include that clarification?
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


Question: content_type: tutorial weight: 10 --- <!-- <del> --- </del> title: Exposing an External IP Address to Access an Application in a Cluster content_type: tutorial weight: 10 <del> --- </del> --> <!-- overview -->

This is a Bug Report Chinese page contentzhdocstutorialsstateless-applicationexpose-external-ip- outdated <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Chinese page contentzhdocstutorialsstateless-applicationexpose-external-ip- is different with English version page. Proposed Solution: Update Chinese page Page to Update: contentzhdocstutorialsstateless-applicationexpose-external-ip- <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language zh
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
/remove-lifecycle rotten
/assign


Question: <ins> apiVersion: v1 kind: Pod metadata: name: volume-test spec: containers: - name: container-test image: busybox:1.28 volumeMounts: - name: all-in-one mountPath: "/projected-volume" readOnly: true volumes: - name: all-in-one projected: sources: - secret: name: mysecret items: - key: username path: my-group/my-username - secret: name: mysecret2 items: - key: password path: my-group/my-password mode: 511 </ins>

This is a Feature Request What would you like to be Localize to Spanish Why is this needed Comments /triage accepted /kind feature /language es /sig docs
Hi Rodolfo, I will take it!
/assign
algún avance al respecto?
disculpa. Lo terminaré hoy, gracias por recordarmenlo Victor.


Question: [build.environment] HUGO_VERSION = "0.70.0" NODE_VERSION = "10.20.0" <ins> RUBY_VERSION = "2.7.1" </ins> [context.production.environment] HUGO_BASEURL = "https://kubernetes.io/"

Hugo warns that it's unnecessarily slow due to an outdated Ruby version. Given that we don't currently specify a Ruby version in , Netlify may be defaulting to an earlier version for maximum breadth of support. (Just a guess!) Slow builds scale poorly. Follow Netlify's advice and specify a Ruby version (are folks OK with 2.7.1?) in : It's a straightforward addition, so anyone can do it, including first-time contributors. Note that this counts as an architectural change, and architectural changes require approval from chairs or tech leads. /sig docs /good-first-issue /cc /priority important-soon
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 : ### What's the problem? /good-first-issue /assign /priority important-soon 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
What are the Ruby dependencies? Is this something that should be set higher up?
I think is as high as our hierarchy gets. As far as dependencies--good question, I honestly don't know off the top of my head. We don't have any obvious dependencies or invocations in the repo. The only thing that comes to mind is a hidden Netlify dependency.
Yes, what library is dependent on Ruby? Guessing one of the post processors, but need to understand why. I thought all post processing used Javascript.
A post processor would make sense.
I'd like this resolved sooner than later. Preview builds are not snappy.
AFAIK the only external processor used by hugo is which are both javascript. I'm pretty sure they have the old version of ruby in there to support older versions of jekyll.
OK. How does this affect the current build if there are no dependencies on Ruby?
I have no idea where it's picking 2.3.6 from I did a little more digging and Netlify's default is 2.6.2 for and 2.7.1 for . I have no idea where it's picking up that version of ruby. I did a search for and didn't find anything.

I also didn't see anything in the env vars defined in netlify's site itself for it.
Ubuntu Xenial 16.04 (default) appears to be set. Meant to say that there is an option (beta) to switch the build-image.
, Q: Where did you see this warning? I'd rather not have a local setting for a language that is not directly used. Can we check back with netlify?
I see it in every build where Ruby isn’t already cached. (Cached builds still use 2.3.6.)
OK. Just trawled through previous netlify discussions.That warning seems to happen in a number of instances Is the search for the ruby installer the problem or something else? Checking out,
Also, should the site add, ? I assume this isn't automatically picked up from the theme directory. build cmd from theme: command = "git submodule update -f --init && cd userguide && npm install postcss-cli && hugo --themesDir ../.." from theme differs from current docs:
Good question--let's open a separate issue for that discussion.
Nothing stands out in template metrics locally. Given that Hugo warns that older versions of Ruby will cause slow builds, it seems reasonable to infer that the search/install process isn't helping.
Created .
Relevant to after testing Ruby with , it looks like Ruby is less responsible for slow builds than post processing, which appears responsible for over 50% of the build time. ,


Question: * [Validate IPv4/IPv6 dual-stack](/docs/tasks/network/validate-dual-stack) networking * Read about [Dual-stack](/docs/concepts/services-networking/dual-stack/) cluster networking <del> * Learn more about the kubeadm [configuration format](/docs/reference/config-api/kubeadm-config.v1beta2/) </del> <ins> * Learn more about the kubeadm [configuration format](/docs/reference/config-api/kubeadm-config.v1beta3/) </ins>

says: the “configuration format” is a hyperlink to , it shall instead point to (beta2 → beta3) says: where “NodeRegistrationOptions” is a hyperlink to . It shall instead point to (beta2 → beta3) says: where “configuration file” is a hypelink to . It shall instead point to (beta2 → beta3) says: where “API referenc” is a hyperlink to It shall instead point to .
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
/sig cluster-lifecycle /remove-kind bug /kind cleanup
/language en


Question: --> 通过创建与[公共顶级域名](https://data.iana.org/TLD/tlds-alpha-by-domain.txt) 同名的名字空间，这些名字空间中的服务可以拥有与公共 DNS 记录重叠的、较短的 DNS 名称。 <del> 所有名字空间中的负载在执行 DNS 查找时，如果查找的名称没有 [尾部句点](https://datatracker.ietf.org/doc/html/rfc1034#page-8)， </del> <ins> 所有名字空间中的负载在执行 DNS 查找时， 如果查找的名称没有[尾部句点](https://datatracker.ietf.org/doc/html/rfc1034#page-8)， </ins> 就会被重定向到这些服务上，因此呈现出比公共 DNS 更高的优先序。 <!--

markdown <img width="681" alt="WX20220809- src="https://user-"
page: /triage accepted /assign
namespace


Question: --- title: 使用 Minikube 安装 Kubernetes <ins> weight: 30 </ins> content_type: concept --- <!--

This is a Bug Report Problem: is missing in Chinese version. Proposed Solution: Add content/zh/docs/setup/learning- Page to Update: content/zh/docs/setup/learning- content/zh/docs/setup/learning-
/language zh /assign


Question: Install CNI plugins (required for most pod network): ```bash <del> CNI_PLUGINS_VERSION="v1.1.1" </del> <ins> CNI_PLUGINS_VERSION="v1.2.0" </ins> ARCH="amd64" DEST="/opt/cni/bin" sudo mkdir -p "$DEST"

This is a Bug Report Problem: The versions of the cri-tools and cni-plugins dependencies was updated in packages, but not in the documentation: Proposed Solution: Update the versions, to match what is in the deb/rpm packages. Currently they are not pinned, but installs the latest: Compared with the deb installation: Page to Update: Kubernetes Version: 27.0 <!--Additional Information:--Related:
/sig cluster-lifecycle /help
This request has been marked as needing help from a contributor. 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 : /sig cluster-lifecycle /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
/triage accepted /priority backlog
/assign
/unassign


Question: <!-- body --> <del> ## コンテナイメージ </del> <ins> ## コンテナイメージ {#container-images} </ins> [コンテナイメージ](/docs/concepts/containers/images/)はすぐに実行可能なソフトウェアパッケージで、アプリケーションの実行に必要なものをすべて含んています。コードと必要なランタイム、アプリケーションとシステムのライブラリ、そして必須な設定項目のデフォルト値を含みます。 設計上、コンテナは不変で、既に実行中のコンテナのコードを変更することはできません。コンテナ化されたアプリケーションがあり変更したい場合は、変更を含んだ新しいイメージをビルドし、コンテナを再作成して、更新されたイメージから起動する必要があります。

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
/triage accepted


Question: TODO: Test and explain how to use additional non-K8s secrets with an existing service account. TODO explain: <del> - The token goes to: "/var/run/secrets/kubernetes.io/serviceaccount/$WHATFILENAME" </del>  No newline at end of file <ins> - The token goes to: "/var/run/secrets/kubernetes.io/serviceaccount/$WHATFILENAME" </ins>

I wish /docs/admin/cluster-components/dns/ page existed It's linked from


Question: --> ### 设置贯穿性字段  {#setting-cross-cutting-fields} <del> 在项目中未所有 Kubernetes 对象设置贯穿性字段是一种常见操作。 </del> <ins> 在项目中为所有 Kubernetes 对象设置贯穿性字段是一种常见操作。 </ins> 贯穿性字段的一些使用场景如下： * 为所有资源设置相同的名字空间

There are some Chinese typo issues in , which should be corrected. For example: <img width="705" alt="image" src="https://user-"The "" should be "“. And, <img width="572" alt="image" src="https://user-"The "“ is wrong and should be "". As I have read the full article, I am planing to submit a PR.
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: ### ローカルのエフェメラルストレージの要求と制限設定 <del> ローカルのエフェメラルストレージを管理するためには_ephemeral-storage_パラメーターを利用することができます。 </del> <ins> ローカルのエフェメラルストレージを管理するためには _ephemeral-storage_ パラメーターを利用することができます。 </ins> Podの各コンテナは、次の1つ以上を指定できます。 * `spec.containers[].resources.limits.ephemeral-storage` * `spec.containers[].resources.requests.ephemeral-storage`

ref: ! [x] [x] [x] [ ] content/ja/docs/concepts/configuration/manage-resources- [ ] [x] content/ja/docs/concepts/configuration/pod-priority- [x] [x] [ ] content/ja/docs/concepts/containers/runtime- [x] content/ja/docs/concepts/overview/kubernetes- [x] content/ja/docs/concepts/extend-kubernetes/api-extension/custom- [x] content/ja/docs/concepts/overview/working-with- [x] content/ja/docs/concepts/overview/working-with-objects/common- [x] content/ja/docs/concepts/overview/working-with-objects/field- [x] content/ja/docs/concepts/overview/working-with- [x] content/ja/docs/concepts/overview/working-with- [ ] content/ja/docs/concepts/scheduling-eviction/assign-pod- [ ] content/ja/docs/concepts/scheduling-eviction/kube- [x] content/ja/docs/concepts/scheduling-eviction/taint-and- [x] [x] content/ja/docs/concepts/security/pod-security- [x] content/ja/docs/concepts/services- [x] content/ja/docs/concepts/storage/persistent- [x] [x] content/ja/docs/concepts/workloads/controllers/cron- [x] [x] [x] [x] content/ja/docs/concepts/workloads/pods/pod- [x] content/ja/docs/reference/access-authn- [x] content/ja/docs/reference/access-authn- [x] content/ja/docs/setup/production-environment/tools/kubeadm/create-cluster- [x] content/ja/docs/setup/production-environment/tools/kubeadm/troubleshooting- [ ] content/ja/docs/tasks/access-application-cluster/web-ui- [x] content/ja/docs/tasks/debug-application-cluster/get-shell-running- [x] content/ja/docs/tasks/run-application/horizontal-pod-autoscale- [x] content/ja/docs/tasks/run-application/run-single-instance-stateful- [x] content/ja/docs/tutorials/stateful-application/basic-stateful- [x] content/ja/docs/tutorials/stateful- (grep) /language ja
/triage accepted
/assign
/kind bug
I'm facing same issue lol :smiley: Feel free to mention me for review if create PRs for this.


Question: ## インフラストラクチャ * [KubeVirt](https://kubevirt.io/user-guide/#/installation/installation)は仮想マシンをKubernetes上で実行するためのアドオンです。通常、ベアメタルのクラスタで実行します。 <ins> * [node problem detector](https://github.com/kubernetes/node-problem-detector)はLinuxノード上で動作し、システムの問題を[Event](/docs/reference/kubernetes-api/cluster-resources/event-v1/)または[ノードのCondition](/ja/docs/concepts/architecture/nodes/#condition)として報告します。 </ins> ## レガシーなアドオン

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: The file might be outdated. en: Under "Networking and Network Policy" section, the entry "Contiv" exists. ja: The entry "Contiv" does not exist. Proposed Solution: Update . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ja
/triage accepted
/assign
I'd like to create a PR for this issue. Please comment if you are working on this issue.
sorry, I have not started to work this issue. please do that.
Thanks for your reply. I'll do it. /assign


Question: * 为控制面[加密通信中的数据](/zh/docs/tasks/tls/managing-tls-in-a-cluster/) * [加密静止状态的数据](/zh/docs/tasks/administer-cluster/encrypt-data/) * [Kubernetes 中的 Secret](/zh/docs/concepts/configuration/secret/) <ins> * [运行时类](/zh/docs/concepts/containers/runtime-class) </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: * [kube-apiserver configuration (v1)](/docs/reference/config-api/apiserver-config.v1/) <ins> * [kube-apiserver encryption (v1)](/docs/reference/config-api/apiserver-encryption.v1/) </ins> * [kubelet configuration (v1alpha1)](/docs/reference/config-api/kubelet-config.v1alpha1/) and [kubelet configuration (v1beta1)](/docs/reference/config-api/kubelet-config.v1beta1/) * [kube-scheduler configuration (v1beta2)](/docs/reference/config-api/kube-scheduler-config.v1beta2/) and

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 Within add a new generated page that documents the format for an encryption configuration. Update to hyperlink to that new reference Why is this needed Within , there is a configuration format for the API server, EncryptionConfiguration. At the moment that format is not documented in Readers may want to look up what that format covers. Comments /sig api-machinery /sig auth /kind feature /language en
/triage accepted
/assign This file is already generated in the generator. All we need to do is to copy it to the website repo.


Question: $ kubectl create -f https://k8s.io/docs/tasks/administer-cluster/namespace-dev.json ``` <ins> Save the following contents into file [`namespace-prod.json`](/docs/admin/namespaces/namespace-prod.json) which describes a production namespace: {% include code.html language="json" file="namespace-prod.json" ghlink="/docs/tasks/administer-cluster/namespace-prod.json" %} </ins> And then let's create the production namespace using kubectl. ```shell

<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [x ] Feature Request [ ] Bug Report Problem: Add the steps to get back out of the kubectl context after running the commands Proposed Solution: point out that the .kube folder has a config file that holds the info Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
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
/remove-lifecycle stale /assign


Question: {{< note >}} एक विशिष्ट संस्करण डाउनलोड करने के लिए, कमांड के इस हिस्से `$(curl -L -s https://dl.k8s.io/release/stable.txt)` को विशिष्ट संस्करण से बदलें। <del> उदाहरण के लिए, Intel macOS पर {{< param "fullversion" >}} संस्करण डाउनलोड करने के लिए, टाइप करें: </del> <ins> उदाहरण के लिए, Intel macOS पर {{< skew currentPatchVersion >}} संस्करण डाउनलोड करने के लिए, टाइप करें: </ins> ```bash <del> curl -LO "https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/darwin/amd64/kubectl" </del> <ins> curl -LO "https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/darwin/amd64/kubectl" </ins> ``` और Apple Silicon macOS के लिए, टाइप करें: ```bash <del> curl -LO "https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/darwin/arm64/kubectl" </del> <ins> curl -LO "https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/darwin/arm64/kubectl" </ins> ``` {{< /note >}}

Parent issue: Substitute the outdated shortcode with the new shortcode in the Hindi language documentation. /assign /triage accepted /language hi
PR has been raised to address this issue.


Question: <ins> --- title: プロセスIDの制限と予約 content_type: concept weight: 40 --- <!-- overview --> {{< feature-state for_k8s_version="v1.20" state="stable" >}} Kubernetesでは、{{< glossary_tooltip term_id="Pod" text="Pod" >}}が使用できるプロセスID(PID)数を制限することができます。また、オペレーティングシステムやデーモンによる使用のために、Podだけではなく{{< glossary_tooltip term_id="node" text="ノード" >}}ごとに割り当て可能なPID数を予約することができます。 <!-- body --> プロセスID(PID)はノードの基本的なリソースです。他のリソース制限に達することなくタスク制限に達することは容易であり、それがホストマシンの不安定性を引き起こす可能性があります。 クラスター管理者はクラスター内で実行しているPodがホストデーモン({{< glossary_tooltip text="kubelet" term_id="kubelet" >}}や{{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}}や場合によってはコンテナランタイムなど)の実行を妨げる、PIDの枯渇を引き起こさないことを保証するメカニズムを必要とします。それに加えて、同ノード上の他のワークロードへの影響を制限するためにPod間でPIDが制限されていることも重要です。 {{< note >}} 特定のLinuxのインストール時に、オペレーティングシステムはPID制限の値を`32768`のような低いデフォルト値に設定することがあります。`/proc/sys/kernel/pid_max`の値を上げることを検討してください。 {{< /note >}} Podが使用できるPID数の制限をkubeletに設定できます。例えば、ノードのホストOSがPIDの最大値を`262144`に設定し、250未満のPodをホストします。この場合、各Podに`1000`PIDを割り当てることで、そのノードで利用可能なPIDを使い切ることを防ぐことができます。管理者がCPUやメモリのようにPIDでもオーバーコミットを行いたい場合、同様にいくつかの追加のリスクがあります。いずれにしても、単一のPodがマシン全体をダウンさせることはできません。このようなリソース制限は単純なフォーク爆弾がクラスター全体の運用に影響を与えるのを防ぐのに役立ちます。 PodごとのPID制限により、管理者はあるPodを他のPodから保護できますが、ホスト上にスケジュールされたすべてのPodがノード全体に影響を与えないことを保証するものではありません。Podごとの制限は、ノードエージェント自体をPID枯渇から保護するものでもありません。 また、Podへの割り当てとは別に、ノードのオーバーヘッドのために一定量のPIDを予約することもできます。これは、CPU、メモリ、その他のリソースをオペレーティングシステムやPodおよびコンテナ外の他の機能で使用するために予約する方法と似ています。 PID制限は、[コンピュータリソース](/ja/docs/concepts/configuration/manage-resources-containers/)のリクエストと制限と並んで重要な機能です。ただし、指定方法は異なります。Podのリソース制限をPodの`.spec`で定義するのではなく、kubeletの設定として制限を設定します。現在、Pod定義のPID制限はサポートされていません。 {{< caution >}} これは、Podに適用される制限が、Podがスケジュールされる場所によって異なる可能性があることを意味します。簡単にするためには、すべてのノードが同じPIDリソースの制限と予約を使用するのが最も簡単です。 {{< /caution >}} ## ノードのPID制限 KubernetesはKubernetesシステムが利用するプロセスID数を予約することができます。予約を設定するために、kubeletのコマンドラインオプションで`--system-reserved`および`--kube-reserved`の`pid=<number>`パラメーターを使用します。指定された値は、システム全体およびKubernetesシステムデーモン用それぞれに、指定された数のプロセスIDが予約されることを宣言します。 ## PodのPID制限 KubernetesはPodで実行するプロセス数を制限することができます。特定のPodのリソース制限として設定するのではなく、ノードレベルでこの制限を指定します。各ノードは異なるPID制限を持つことができます。制限を設定するために、kubeletに`--pod-max-pids`のコマンドラインパラメーターを指定するか、kubeletの[構成ファイル](/docs/tasks/administer-cluster/kubelet-config-file/)の`PodPidsLimit`に設定します。 ## Evictionを基にしたPID Podが誤操作していたり、異常なリソースを消費している時にPodの終了を実行することをkubeletに設定できます。この機能はEvictionと呼ばれています。様々なEvictionシグナルのために[リソース不足への対処の設定](/docs/concepts/scheduling-eviction/node-pressure-eviction/)ができます。`pid.available`Evictionシグナルを使用して、Podによって使用されるPIDの数の閾値を設定します。ソフトとハードのEvictionポリシーを設定できます。しかし、ハードEvictionポリシーを使用しても、PIDの数が非常に速く増加している場合、ノードはPID制限に達することで不安定な状態になる可能性があります。Evictionシグナルの値は定期的に計算されますが、この値は制限を強制するものではありません。 PIDの制限、つまりPod毎、ノード毎にハード制限を設定できます。一度制限に達すると、ワークロードは新しいPIDを取得しようとする際に失敗し始めます。これがPodの再スケジューリングにつながるかどうかは、ワークロードがこれらの失敗にどのように反応するか、PodのLiveness ProbeとReadiness Probeがどのように設定されているかに依存します。しかし、リミットが正しく設定されていれば、あるPodが誤動作している場合でも、他のPodのワークロードやシステムプロセスがPIDを使い果たすことはないと保証することができます。 ## {{% heading "whatsnext" %}} - [PID制限の強化に関するドキュメント](https://github.com/kubernetes/enhancements/blob/097b4d8276bc9564e56adf72505d43ce9bc5e9e8/keps/sig-node/20190129-pid-limiting.md)で詳細情報を確認できます。 - 歴史的背景について学ぶために、[Kubernetes 1.14での安定性向上のためのプロセスID制限](/blog/2019/04/15/process-id-limiting-for-stability-improvements-in-kubernetes-1.14/)をご覧ください。 - [コンテナのリソース管理](/ja/docs/concepts/configuration/manage-resources-containers/)についてご覧ください。 - [リソース不足時の対応設定](/docs/concepts/scheduling-eviction/node-pressure-eviction/)の方法について学ぶことができます。 </ins>  No newline at end of file

Note that this issue is for Japanese Speaker This is a Feature Request What would you like to be Translate content/en/docs/concepts/policy/pid- into Japanese Why is this needed There is no Japanese translation for this page Comments File to translate: Original: /area localization /language ja /assign
Thanks! /triage accepted
/assign
/assign


Question: <ins> --- title: Leases api_metadata: - apiVersion: "coordination.k8s.io/v1" kind: "Lease" content_type: concept weight: 30 --- <!-- overview --> Los sistemas distribuidos suelen necesitar _leases_, que proporcionan un mecanismo para bloquear recursos compartidos y coordinar la actividad entre los miembros de un conjunto. En Kubernetes, el concepto de lease (arrendamiento) está representado por objetos [Lease](/docs/reference/kubernetes-api/cluster-resources/lease-v1/) en el {{< glossary_tooltip text="grupo API" term_id="api-group" >}} de `coordination.k8s.io`, que se utilizan para capacidades críticas del sistema, como los heartbeats del nodo y la elección del líder a nivel de componente. <!-- body --> ## Heartbeats del nodo {#node-heart-beats} Kubernetes utiliza la API Lease para comunicar los heartbeats de los nodos kubelet al servidor API de Kubernetes. Para cada `Nodo` , existe un objeto `Lease` con un nombre que coincide en el espacio de nombres `kube-node-lease`. Analizando a detalle, cada hearbeat es una solicitud **update** a este objeto `Lease`, actualizando el campo `spec.renewTime` del objeto Lease. El plano de control de Kubernetes utiliza la marca de tiempo de este campo para determinar la disponibilidad de este «Nodo». Ve [Objetos Lease de nodos](/docs/concepts/architecture/nodes/#heartbeats) para más detalles. ## Elección del líder Kubernetes también utiliza Leases para asegurar que sólo una instancia de un componente se está ejecutando en un momento dado. Esto lo utilizan componentes del plano de control como `kube-controller-manager` y `kube-scheduler` en configuraciones de HA, donde sólo una instancia del componente debe estar ejecutándose activamente mientras las otras instancias están en espera. ## Identidad del servidor API {{< feature-state feature_gate_name="APIServerIdentity" >}} A partir de Kubernetes v1.26, cada `kube-apiserver` utiliza la API Lease para publicar su identidad al resto del sistema. Aunque no es particularmente útil por sí mismo, esto proporciona un mecanismo para que los clientes puedan descubrir cuántas instancias de `kube-apiserver` están operando el plano de control de Kubernetes. La existencia de los objetos leases de kube-apiserver permite futuras capacidades que pueden requerir la coordinación entre cada kube-apiserver. Puedes inspeccionar los leases de cada kube-apiserver buscando objetos leases en el namespace `kube-system` con el nombre `kube-apiserver-<sha256-hash>`. También puedes utilizar el selector de etiquetas `apiserver.kubernetes.io/identity=kube-apiserver`: ```shell kubectl -n kube-system get lease -l apiserver.kubernetes.io/identity=kube-apiserver ``` ``` NAME                                        HOLDER                                                                           AGE apiserver-07a5ea9b9b072c4a5f3d1c3702        apiserver-07a5ea9b9b072c4a5f3d1c3702_0c8914f7-0f35-440e-8676-7844977d3a05        5m33s apiserver-7be9e061c59d368b3ddaf1376e        apiserver-7be9e061c59d368b3ddaf1376e_84f2a85d-37c1-4b14-b6b9-603e62e4896f        4m23s apiserver-1dfef752bcb36637d2763d1868        apiserver-1dfef752bcb36637d2763d1868_c5ffa286-8a9a-45d4-91e7-61118ed58d2e        4m43s ``` El hash SHA256 utilizado en el nombre del lease se basa en el nombre de host del sistema operativo visto por ese servidor API. Cada kube-apiserver debe ser configurado para utilizar un nombre de host que es único dentro del clúster. Las nuevas instancias de kube-apiserver que utilizan el mismo nombre de host asumirán los leases existentes utilizando una nueva identidad de titular, en lugar de instanciar nuevos objetos leases. Puedes comprobar el nombre de host utilizado por kube-apiserver comprobando el valor de la etiqueta `kubernetes.io/hostname`: ```shell kubectl -n kube-system get lease apiserver-07a5ea9b9b072c4a5f3d1c3702 -o yaml ``` ```yaml apiVersion: coordination.k8s.io/v1 kind: Lease metadata: creationTimestamp: "2023-07-02T13:16:48Z" labels: apiserver.kubernetes.io/identity: kube-apiserver kubernetes.io/hostname: master-1 name: apiserver-07a5ea9b9b072c4a5f3d1c3702 namespace: kube-system resourceVersion: "334899" uid: 90870ab5-1ba9-4523-b215-e4d4e662acb1 spec: holderIdentity: apiserver-07a5ea9b9b072c4a5f3d1c3702_0c8914f7-0f35-440e-8676-7844977d3a05 leaseDurationSeconds: 3600 renewTime: "2023-07-04T21:58:48.065888Z" ``` Los leases caducados de los kube-apiservers que ya no existen son recogidos por los nuevos kube-apiservers después de 1 hora. Puedes desactivar el lease de identidades del servidor API desactivando la opción `APIServerIdentity` de los [interruptores de funcionalidades](/docs/reference/command-line-tools-reference/feature-gates/). ## Cargas de trabajo {#custom-workload} Tu propia carga de trabajo puede definir su propio uso de los leases. Por ejemplo, puede ejecutar un {{< glossary_tooltip term_id=controller text=controlador >}} en la que un miembro principal o líder realiza operaciones que sus compañeros no realizan. Tú defines un Lease para que las réplicas del controlador puedan seleccionar o elegir un líder, utilizando la API de Kubernetes para la coordinación. Si utilizas un lease, es una buena práctica definir un nombre para el lease que esté obviamente vinculado a el producto o componente. Por ejemplo, si tienes un componente denominado Ejemplo Foo, utilice un lease denominado `ejemplo-foo`. Si un operador de clúster u otro usuario final puede desplegar varias instancias de un componente, selecciona un nombre prefijo y elije un mecanismo (como el hash del nombre del despliegue) para evitar colisiones de nombres para los leases. Puedes utilizar otro enfoque siempre que consigas el mismo resultado: los distintos productos de software no entren en conflicto entre sí. </ins>  No newline at end of file

This is a Feature Request Translate this page into Spanish. What would you like to be The translation will be to docs/concepts/architecture/leases Why is this needed There is no Spanish translation for this file. It would be great if we could read this in Spanish. Comments The Spanish translation team would like to facilitate your contribution's journey, any doubt participate in the weekly meetings in the kubernetes slack channel We also encourage new contributors to participate in their native speaking language . /triage accepted /kind feature /language es /sig docs
/assign
Gracias cualquier duda estamos en el canal


Question: .button { display: inline-block; border-radius: 6px; <del> padding: 0 20px; line-height: 40px; </del> <ins> padding: 6px 20px; line-height: 1.3rem; </ins> color: white; background-color: $blue; text-decoration: none;

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: ! The space between lines in button is too wide, causing ugly labels especially when the window is not wide or in localized pages which use more characters for the button text (i.e. ). The new docsy theme narrows this page width so it tends to happen more. Proposed Solution: The current stylesheet specifies 0px as vertical padding and set 40px as line-height. The problem can be fixed by specifying a reasonable vertical padding and less line-height. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--I've written a code to fix this problem. I'll send a PR to fix this problem. /assign
/kind cleanup


Question: * The [deprecation policy](/docs/reference/using-api/deprecation-policy/) for Kubernetes explains the project's approach to removing features and components.

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: link At 435 line: See [Support Device Monitoring]() for more details. from link At 479 line: - : Enable service to route traffic based upon the Node topology of the cluster. See [ServiceTopology]() for more details. Proposed Solution: with correct link from link /docs/concepts/services-networking/service-topology/ Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign


Question: <!-- This page covers how to customize the components that kubeadm deploys. For control plane components <del> you can use flags in the `ClusteConfiguration` structure or patches per-node. For the kubelet </del> <ins> you can use flags in the `ClusterConfiguration` structure or patches per-node. For the kubelet </ins> and kube-proxy you can use `KubeletConfiguration` and `KubeProxyConfiguration`, accordingly. All of these options are possible via the kubeadm configuration API. For more details on each field in the configuration you can navigate to our <del> [API reference pages](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta3). </del> <ins> [API reference pages](/docs/reference/config-api/kubeadm-config.v1beta3/). </ins> --> 本页面介绍了如何自定义 kubeadm 部署的组件。 <del> 你可以使用 `ClusteConfiguration` 结构中定义的参数，或者在每个节点上应用补丁来定制控制平面组件。 </del> <ins> 你可以使用 `ClusterConfiguration` 结构中定义的参数，或者在每个节点上应用补丁来定制控制平面组件。 </ins> 你可以使用 `KubeletConfiguration` 和 `KubeProxyConfiguration` 结构分别定制 kubelet 和 kube-proxy 组件。 所有这些选项都可以通过 kubeadm 配置 API 实现。

!
/language zh /triage accepted
/kind bug
/assign
/retitle [zh] typo in kubeadm API


Question: Pod runs a Container based on the provided Docker image. ```shell <del> kubectl create deployment hello-node --image=registry.k8s.io/echoserver:1.4 </del> <ins> kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.39 -- /agnhost netexec --http-port=8080 </ins> ``` 2. View the Deployment:

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. --I decided to try to learn a bit of Kubernetes on my new M1 Mac. It all worked except for the command, as that image does not support ARM. A bit of Googling and a visit to StackOverflow fixed it for me, but it would be better if that information was in the core guide. For others following in my footsteps, I have created a pull request with the ARM image info. Why is this needed ARM-based devices are becoming increasingly popular dev platforms, especially for early prototyping and learning. A Getting Started guide that worked on these hosts would be preferable to one which doesn't. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --I will link this Issue to my pull request. I realize the version number, not just the repo and name, are different from the existing image. However, being on an ARM device, I have no way of testing the original image, so I didn't change it.
I agree, it would be nice that the "getting started" guide is working on both platforms or at least propose an alternative image for ARM. Feel free to link this issue from the PR you made and thanks for taking the time! /triage accepted /priority backlog /language en
Oops, I had a typo in the pull request link. Linked.