kubernetes/website

This is a Bug Report Problem: The Dynamic Resource Allocation concept page was split into several pages under content/en/docs/concepts/resource-management/dynamic-resource-allocation/. A in-page link still point to anchors that moved to a different page, so clicking them does nothing. Proposed Solution: Replace the in-page anchors with full paths. In device-taints.md, [above](#admin-access) should link to /docs/concepts/resource-management/dynamic-resource-allocation/dra-api/#admin-access. Page to Update: https://kubernetes.io/docs/concepts/resource-management/dynamic-resource-allocation/device-taints/ /good-first-issue

This is a Bug Report Problem: I ran into this while researching a kubectl plugin idea for CronJobs: listing the next runs across a cluster, soonest first, in a chosen time zone, and flagging runs that were missed or skipped. Checking how the controller handles missed schedules, I found that the CronJob page says two things the controller does not do. Job creation says: If there are more than 100 missed schedules, then it does not start the Job and logs the error. and the example below it says: If the CronJob controller happens to be down from 08:29:00 to 10:21:00, the Job will not start as the number of missed Jobs which missed their schedule is greater than 100. The controller does start a Job. With more than 100 missed schedules it records a TooManyMissedTimes Warning event, then creates a Job for the most recent missed schedule, as it does when fewer were missed. The caution under Schedule suspension says: When .spec.suspend changes from true to false on an existing CronJob

This is a task issue What needs doing Look at issue #28690 Look at pull request #55693 (if necessary) read the docs about contributing to Kubernetes docs Then, open a new pull request that makes a change equivalent to #55693. If you did that manually, credit @p1930n as the original author, and yourself. If you used any AI agent, mention the AI agent you used as well as your own identity and @p1930n. You will need to write a description for your pull request that helps people understand the change you are making and how to check it. Why is this needed PR #55693 is stale. Comments /language en /priority backlog /help /triage accepted

This is a Feature Request What would you like to be added Translate the following Kubernetes documentation page into Korean: English: https://kubernetes.io/docs/concepts/storage/ephemeral-storage/ Target file:  content/en/docs/concepts/storage/ephemeral-storage.md  Why is this needed Kubernetes Korean documentation includes content about local ephemeral storage within the resource-management documentation, but the dedicated documentation page is not currently available in Korean. As a result, users navigating directly to the localized page cannot access a Korean translation of the full content. Adding this translation would improve documentation completeness and accessibility for Korean-speaking Kubernetes users. Additional context The related Korean documentation page is: https://kubernetes.io/ko/docs/concepts/configuration/manage-resources-containers/#로컬-임시-ephemeral-스토리지 However, the standalone page corresponding to /docs/concepts/storage/ephemeral-storage/ still

This is a feature request Problem: The preview of the Kubernetes v1.37 docs for Pod level resource managers includes a page-level glossary, with entries for: Pod level resources specification Guaranteed container Exclusive slice Pod shared pool These definitions are only mentioned on that page. Proposed Solution: This issue proposes adding "Pod shared pool" to the main glossary. Additional Information: /help /language en /priority backlog If v1.37 has been released, the change to make will be against the main branch; otherwise, it will be against dev-1.37. AI agents working on this feature request should mention "This was submitted by an AI agent and has not been checked by a human" in the PR description.