Question: - `CustomResourceWebhookConversion`: Enable webhook-based conversion on resources created from [CustomResourceDefinition](/docs/concepts/extend-kubernetes/api-extension/custom-resources/). troubleshoot a running Pod. <del> - `DisableAcceleratorUsageMetrics`: [Disable accelerator metrics collected by the kubelet](/docs/concepts/cluster-administration/monitoring.md). </del> <ins> - `DisableAcceleratorUsageMetrics`: [Disable accelerator metrics collected by the kubelet](/docs/concepts/cluster-administration/system-metrics/). </ins> - `DevicePlugins`: Enable the [device-plugins](/docs/concepts/cluster-administration/device-plugins/) based resource provisioning on nodes. - `DefaultPodTopologySpread`: Enables the use of `PodTopologySpread` scheduling plugin to do

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: Line 426: broken link - : [Disable accelerator metrics collected by the kubelet](/docs/concepts/cluster-). Line 477: duplicated - : When  is enabled for [local ephemeral storage](/docs/concepts/configuration/manage-compute-resources-container/) and the backing filesystem for [emptyDir volumes](/docs/concepts/storage/volumes/#emptydir) supports project quotas and they are enabled, use project quotas to monitor [emptyDir volume](/docs/concepts/storage/volumes/#emptydir) storage consumption rather than filesystem walk for better performance and accuracy. [local ephemeral storage](/docs/concepts/configuration/manage-resources-containers/) and the backing filesystem for [emptyDir volumes](/docs/concepts/storage/volumes/#emptydir) supports project quotas and they are enabled, use project quotas to monitor [emptyDir volume](/docs/concepts/storage/volumes/#emptydir) storage consumption rather than filesystem walk for better performance and accuracy. Proposed Solution: Line 426: - : [Disable accelerator metrics collected by the kubelet](/docs/concepts/cluster-administration/system-metrics/). Line 477: - : When  is enabled for [local ephemeral storage](/docs/concepts/configuration/manage-compute-resources-container/) and the backing filesystem for [emptyDir volumes](/docs/concepts/storage/volumes/#emptydir) supports project quotas and they are enabled, use project quotas to monitor [emptyDir volume](/docs/concepts/storage/volumes/#emptydir) storage consumption rather than filesystem walk for better performance and accuracy. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign


Question: <ins> --- title: 変更のレビュー weight: 30 --- <!-- overview --> このセクションでは、コンテンツのレビュー方法について説明します。 <!-- body --> </ins>

This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign


Question: Cuidado. {{< /warning >}} <del> ### Ambiente de teste embutido do Katacoda Este botão permite aos usuários executar o Minikube dentro dos seus navegadores utilizando o terminal do Katacoda. Ele diminui a barreira de entrada permitindo que as pessoas utilizem o Minikube com um único clique ao invés de precisar fazer todo o processo de instalação e configuração das ferramentas Minikube e Kubectl na máquina local. O ambiente de teste embutido está configurado para executar `minikube start` e permite aos usuários completar tutoriais na mesma janela que a documentação. {{< caution >}} Esta sessão é limitada a 15 minutos. {{< /caution >}} Por exemplo: ``` {{</* kat-button */>}} ``` The output is: {{< kat-button >}} </del> ## Problemas comuns com _shortcodes_ {#common-shortcode-issues} ### Listas ordenadas

The terminal to use the interactive tutorials is using Katacoda, however, it was purchased by O'Reilly and is outside the domain that the terminal is using to run.
Hi You can ask support queries in channels.
Page related to issue: /language pt
/retitle [pt-br] Remove the obsolete online interactive tutorial from the page
For anyone willing to assist on this, please refer to PR for information regarding the implementation of similar changes carried out on the main website (i.e. English pages).
/good-first-isssue
/triage accepted /assign
/retitle [pt-br] Obsolete online interactive tutorial in the Using Minikube to Create a Cluster page /kind bug


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: <!-- body --> ## Control Plane Components <del> The control plane's components make global decisions about the cluster (for example, scheduling), as well as detecting and responding to cluster events (for example, starting up a new {{< glossary_tooltip text="pod" term_id="pod">}} when a deployment's `replicas` field is unsatisfied). </del> <ins> The control plane's components make global decisions about the cluster (for example, scheduling), as well as detecting and responding to cluster events (for example, starting up a new {{< glossary_tooltip text="pod" term_id="pod">}} when a Deployment's `{{< glossary_tooltip text="replicas" term_id="replica" >}}` field is unsatisfied). </ins> Control plane components can be run on any machine in the cluster. However, for simplicity, set up scripts typically start all control plane components on

Just like the pods and the control plane have hover which makes it easier to understand. There should be a hover that should explain what does replica mean here and in what context we are using it as for a beginner it might will be confusing to understand what replica is
Would you be able to provide us with the web page's URL that requires modification? If it's possible, it would be helpful to include the URL in the issue description as well. /language en /triage needs-information
Reference:
/remove-triage needs-information
/retitle Include in glossary and add tooltip for it on "Kubernetes Components" page /language en
Can I work on it now?
/triage accepted Anyone - including you - is welcome to open a pull request. This is open source in action! /priority backlog
/assign


Question: <!-- Now modify your nginx replicas to start an https server using the certificate in the secret, and the Service, to expose both ports (80 and 443): --> <del> 现在修改 Nginx 副本，启动一个使用在秘钥中的证书的 https 服务器和 Servcie，都暴露端口（80 和 443）： </del> <ins> 现在修改 nginx 副本，启动一个使用在秘钥中的证书的 HTTPS 服务器和 Servcie，暴露端口（80 和 443）： </ins> {{< codenew file="service/networking/nginx-secure-app.yaml" >}}

Nginx https 404
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
Hi It sounds like you wanted to provide feedback about a web page. Which web page was that? /triage needs-information


Question: {{< /note >}} <del> ## Non Graceful node shutdown {#non-graceful-node-shutdown} {{< feature-state state="beta" for_k8s_version="v1.26" >}} A node shutdown action may not be detected by kubelet's Node Shutdown Manager, either because the command does not trigger the inhibitor locks mechanism used by kubelet or because of a user error, i.e., the ShutdownGracePeriod and ShutdownGracePeriodCriticalPods are not configured properly. Please refer to above section [Graceful Node Shutdown](#graceful-node-shutdown) for more details. When a node is shutdown but not detected by kubelet's Node Shutdown Manager, the pods that are part of a StatefulSet will be stuck in terminating status on the shutdown node and cannot move to a new running node. This is because kubelet on the shutdown node is not available to delete the pods so the StatefulSet cannot create a new pod with the same name. If there are volumes used by the pods, the VolumeAttachments will not be deleted from the original shutdown node so the volumes used by these pods cannot be attached to a new running node. As a result, the application running on the StatefulSet cannot function properly. If the original shutdown node comes up, the pods will be deleted by kubelet and new pods will be created on a different running node. If the original shutdown node does not come up, these pods will be stuck in terminating status on the shutdown node forever. To mitigate the above situation, a  user can manually add the taint `node.kubernetes.io/out-of-service` with either `NoExecute` or `NoSchedule` effect to a Node marking it out-of-service. If the `NodeOutOfServiceVolumeDetach`[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled on `kube-controller-manager`, and a Node is marked out-of-service with this taint, the pods on the node will be forcefully deleted if there are no matching tolerations on it and volume detach operations for the pods terminating on the node will happen immediately. This allows the Pods on the out-of-service node to recover quickly on a different node. During a non-graceful shutdown, Pods are terminated in the two phases: 1. Force delete the Pods that do not have matching `out-of-service` tolerations. 2. Immediately perform detach volume operation for such pods. {{< note >}} - Before adding the taint `node.kubernetes.io/out-of-service` , it should be verified that the node is already in shutdown or power off state (not in the middle of restarting). - The user is required to manually remove the out-of-service taint after the pods are moved to a new node and the user has checked that the shutdown node has been recovered since the user was the one who originally added the taint. {{< /note >}} </del> ### Pod Priority based graceful node shutdown {#pod-priority-graceful-node-shutdown} {{< feature-state state="alpha" for_k8s_version="v1.23" >}}

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: is in the wrong place: it should be part of the Graceful node shutdown heading, but it's actually under the Non-graceful node shutdown section. Proposed Solution: Reorganize the existing text. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /kind bug /help /triage accepted /priority backlog
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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: is in the wrong place: it should be part of the Graceful node shutdown heading, but it's actually under the Non-graceful node shutdown section. Reorganize the existing text. <!--Kubernetes Version:--/language en /kind bug /help /triage accepted /priority backlog 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> apiVersion: v1 kind: Service metadata: name: mongo labels: app.kubernetes.io/name: mongo app.kubernetes.io/component: backend spec: ports: - port: 27017 targetPort: 27017 selector: app.kubernetes.io/name: mongo app.kubernetes.io/component: backend </ins>

In the section of There is no file with the specified URL, and the output of running this command is:
In PR the is deleted, which is used in the 'Creating MongoDB deployment and service' page. /kind bug
/triage accepted /retitle Example missing from Use Port Forwarding to Access Applications in a Cluster
/assign will add these yaml's
Fix it here


Question: ports: - containerPort: 80 <del> # file konfigurasi </del> <ins> # berkas konfigurasi </ins> spec: strategy: type: Recreate # nilai yang diperbarui

This issue is intended for contributor workshop as part of Cloud Native Day Indonesia on 7th Nov 2020. Please don't take it if you are not part of the workshop. There are several old translated pages that contain the english glossary "file", supposed to use Indonesian "berkas" as per KBBI. Please claim the task to fix them by giving comments on this Github issue. /language id Tasks to fix "file" -"berkas": [x] docs/tasks/manage-kubernetes-objects/imperative-[x] docs/tasks/manage-kubernetes-objects/declarative-[ ] docs/tasks/manage-kubernetes-objects/imperative-[ ] docs/tasks/configure-pod-container/configure-pod-[ ] docs/tasks/administer-cluster/sysctl-[ ] [x] [ ] docs/concepts/storage/storage-[ ] docs/concepts/services-networking/connect-applications-[ ] docs/concepts/services-[x] [x] docs/concepts/cluster-
/triage accepted
/assign
I'm taking this page docs/tasks/manage-kubernetes-objects/imperative-
/reopen
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
i'm taking this page docs/tasks/manage-kubernetes-objects/declarative-
may i change this file:
thanks feel free to raise the PR and link this issue
/reopen
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
I take this page :
please let me change another part. I will try to change this file
sure just mention this issue number when you raise the pull request /reopen
Reopened this issue. <detailsIn response to : please let me change another part sure just mention this issue number when you raise the pull request 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
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-contributor-experience at . /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-contributor-experience at . /lifecycle rotten
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /close
Closing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details


Question: <!-- body --> <del> [View the dashboard](https://datastudio.google.com/reporting/fede2672-b2fd-402a-91d2-7473bdb10f04). </del> <ins> [View the dashboard](https://lookerstudio.google.com/u/0/reporting/fe615dc5-59b0-4db5-8504-ef9eacb663a9/page/4VDGB/). </ins> <del> This dashboard is built using Google Data Studio and shows information collected on kubernetes.io using Google Analytics. </del> <ins> This dashboard is built using [Google Looker Studio](https://lookerstudio.google.com/overview) and shows information collected on kubernetes.io using Google Analytics 4 since August 2022. </ins> ### Using the dashboard

This is a Bug Report Problem: The dashboard linked to is currently broken because the data has moved or it no longer has access <img width="1501" alt="Screenshot 2023-10-02 at 12 53 28" src=""Proposed Solution: Restore access to the data for the dashboard Page to Update:
It was working fine few days back, who knows what happened to it now /priority backlog /sig docs /area web-development
/triage accepted I think Google may have switched off the old analytics mechanism.
/assign
If it is so how to proceed with connecting to them now. It says " Please contact the data source owner to fix it."
Even though I suspect I know the cause, I don't have advice right now on how contributors can fix it. /uncc
Maybe we can simply remove the link or even the whole page. Does anyone live on this statistics?
I opened the issue because I was looking for the data, but since it wasn't noticed for a bit maybe not many people are
+1 on this - I think it is helpful to use this data for prioritizing improvements. Is there somewhere I can look in the meantime?
Not that I know of. We would instead need to work on an actual fix.
yes
FWIW, the data till September-ish has been restored. This is because we switched over to the GA4 plugin from Google UA sometime around then for Analytics. I tried adding the GA4 plugin as a brand new data source. However, due to the mismatch in the fields reported between the two, it wasn't a successful endeavour. Maybe can comment on this, since they were working on the GA4 transition earlier this year? <img width="1206" alt="Screenshot 2023-12-11 at 9 11 40 AM" src=""
Raising the priority to critical/urgent, since this affects our annual report creation.
I can take a look at this if you'd like. I set up the dashboard originally
: Yes please, that would be helpful. The dashboards seem to be broken again.
I will take a look! I have a suspicion that we need a whole new dashboard because google analytics 4 is completely different, but will keep you updated. Please let me know if there is anything specific I can help look up for the annual report.

Sorry for not catching this earlier /assign
Just to follow up, based on this comment from the migration issue, data in UA was deleted in 2024Q1, The old UA data was used to populate the dashboard and the new G4 analytics are not compatible with UA, so we will need to make a new dashboard. I've been testing out a few options, but google analytics 4 tracks things differently, so its a little bit tricky to get a dashboard that shows the same information. heres a screenshot of the pageview metrics from the g4 dashboard for the whole site for 2023. total page views 109 million, top pages (aside from search and home pages): (formerly called kubectl Cheat Sheet) which are the same top pages from last year. <img width="1306" alt="Screen Shot 2024-01-11 at 11 30 05 AM" src=""
I have a new dashboard in progress: This link should be viewable for everyone, but note that not all the graphs are updated to show meaningful data. I wanted to share out the link b/c it should at least be able to show the top pages and page views for the annual report. The existing dashboard is also back to working, the historical data is still available up to September 2023, when new tracking in UA stopped. Data from UA will be deleted on July 1, 2024 so there is still time to download it if we want to keep all the site history. (the dashboard thats up on the site was not working bc the data source was changed to the GA4 data, which is incompatible with the graphs. Apologies if it was me that did this, i honestly can't remember).
This issue is labeled with but has not been updated in over 30 days, and should be re-triaged. Critical-urgent issues must be actively worked on as someone's top priority right now. You can: Confirm that this issue is still relevant with (org members only) Deprioritize it with Close this issue with For more details on the triage process, see /remove-triage accepted


Question: You can modify Node objects regardless of the setting of `--register-node`. For example, you can set labels on an existing Node, or mark it unschedulable. --> <del> #### 手动节点管理 </del> <ins> ### 手动节点管理 </ins> 你可以使用 {{< glossary_tooltip text="kubectl" term_id="kubectl" >}} 来创建和修改 Node 对象。

The Chinese version of the chapter introducing the concept of misses the explanation of the info field compared to the English version. Please check it.
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
this is fixed here


Question: and all are used to determine which issuers are accepted. --> 服务帐号令牌颁发者的标识符。 <del> 颁发者将在已办法令牌的 "iss" 声明中检查此标识符。 </del> <ins> 颁发者将在已颁发令牌的 "iss" 声明中检查此标识符。 </ins> 此值为字符串或 URI。 如果根据 OpenID Discovery 1.0 规范检查此选项不是有效的 URI，则即使特性门控设置为 true， ServiceAccountIssuerDiscovery 功能也将保持禁用状态。

<html <!--StartFragment----service-account-issuer strings | "iss" URI OpenID Discovery 1.0 URI true ServiceAccountIssuerDiscovery OpenID service-account-issuer HTTPS URL URL {service-account-issuer}/.well-known/openid-configuration OpenID <!--EndFragment--“” </body</html
/language zh I assume this is a bug report. If possible, clarify whether the issue is with the upstream (English) docs or with the way those docs have been localized. /triage needs-information
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /triage bug 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
/kind bug /triage accepted
/assign


Question: addresses of the pods that are running the Hello World application. To verify these are pod addresses, enter this command: <del> kubectl get pods --output=wide </del> <ins> ```shell kubectl get pods --output=wide ``` </ins> The output is similar to this: <del> NAME                         ...  IP         NODE hello-world-2895499144-1jaz9 ...  10.0.1.6   gke-cluster-1-default-pool-e0b8d269-1afc hello-world-2895499144-2e5uh ...  10.0.1.8   gke-cluster-1-default-pool-e0b8d269-1afc hello-world-2895499144-9m4h1 ...  10.0.0.6   gke-cluster-1-default-pool-e0b8d269-5v7a hello-world-2895499144-o4z13 ...  10.0.1.7   gke-cluster-1-default-pool-e0b8d269-1afc hello-world-2895499144-segjf ...  10.0.2.5   gke-cluster-1-default-pool-e0b8d269-cpuc </del> <ins> ``` NAME                         ...  IP         NODE hello-world-2895499144-1jaz9 ...  10.0.1.6   gke-cluster-1-default-pool-e0b8d269-1afc hello-world-2895499144-2e5uh ...  10.0.1.8   gke-cluster-1-default-pool-e0b8d269-1afc hello-world-2895499144-9m4h1 ...  10.0.0.6   gke-cluster-1-default-pool-e0b8d269-5v7a hello-world-2895499144-o4z13 ...  10.0.1.7   gke-cluster-1-default-pool-e0b8d269-1afc hello-world-2895499144-segjf ...  10.0.2.5   gke-cluster-1-default-pool-e0b8d269-cpuc ``` </ins> 1. Use the external IP address (`LoadBalancer Ingress`) to access the Hello World application: <del> curl http://<external-ip>:<port> </del> <ins> ```shell curl http://<external-ip>:<port> ``` </ins> where `<external-ip>` is the external IP address (`LoadBalancer Ingress`) of your Service, and `<port>` is the value of `Port` in your Service

This is a Bug Report There are some commands in the tutorial that are missing code formatting. This is a request to update those commands and remove any extra lines in the page. <!--Required Information--Problem: The tutorial has commands that are not formatted as code. For example, kubectl get deployments hello-world Add code formatting: Proposed Solution: Identify the commands that are missing code formatting. Add the code formatting to the commands. Clean up any extra lines in the page. Page to Update: This is a good issue for a first time contributor. If you need more information, feel free to ask in this issue. It is a good idea to build your changes locally.
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/triage accepted /language en Thanks - another good spot
Is this PR currently being worked on?
it seems already formatted, right?
I don't see any issues with the page as well, and it looks like it was last modified July 27, 2020 at 4:18. Are we missing something?
Let me look. I'd like a first time contributor to work on this issue.
The page renders correctly, however, it would be helpful to clean up the formatting of the page such as extra lines and spaces. Also, the page should use code blocks around any commands (instead of indentation). Let me know if you need more information. Thanks!
i'm a first timer in kubernetes. But i saw nothing wrong in formatting code nor indentation. Only i think there is missing some instruction in creating apps. Should be better to follow Just my 2cent. wdyt?
/assign


Question: Set the value of the `replicas` field to 2. | Set the value of the `replicas` field to `2`. {{< /table >}} <ins> ## Referring to Kubernetes API resources This section talks about how we reference API resources in the documentation. ### Clarification about "resource" Kubernetes uses the word "resource" to refer to API resources, such as `pod`, `deployment`, and so on. We also use "resource" to talk about CPU and memory requests and limits. Always refer to API resources as "API resources" to avoid confusion with CPU and memory resources. ### When to use Kubernetes API terminologies The different Kubernetes API terminologies are: - Resource type: the name used in the API URL (such as `pods`, `namespaces`) - Resource: a single instance of a resource type (such as `pod`, `secret`) - Object: a resource that serves as a "record of intent". An object is a desired state for a specific part of your cluster, which the Kubernetes control plane tries to maintain. Always use "resource" or "object" when referring to an API resource in docs. For example, use "a `Secret` object" over just "a `Secret`". ### API resource names Always format API resource names using [UpperCamelCase](https://en.wikipedia.org/wiki/Camel_case), also known as PascalCase, and code formatting. For inline code in an HTML document, use the `<code>` tag. In a Markdown document, use the backtick (`` ` ``). Don't split an API object name into separate words. For example, use `PodTemplateList`, not Pod Template List. For more information about PascalCase and code formatting, please review the related guidance on [Use upper camel case for API objects](/docs/contribute/style/style-guide/#use-upper-camel-case-for-api-objects) and [Use code style for inline code, commands, and API objects](/docs/contribute/style/style-guide/#code-style-inline-code). For more information about Kubernetes API terminologies, please review the related guidance on [Kubernetes API terminology](/docs/reference/using-api/api-concepts/#standard-api-terminology). </ins> ## Code snippet formatting ### Don't include the command prompt

Kubernetes uses the word "resource" to refer to API resources, such as , , and so on. We also use "resource" to talk about CPU and memory requests and limits. Update the with a new section to clarify how we talk about API resources in our documentation. [ ] Add a new section under Documentation formatting standards called "Referring to Kubernetes API resources" (or similar). [ ] In your new section, add guidance for the following (use a combination of paragraphs and bulleted lists): Differentiate between an HTTP API resource and a CPU/memory resource (you can use the first line of this issue description) Differentiate between Kubernetes API terminology and when to use: Resource type: the name used in the API URL (such as , ) Resource: a single instance of a resource type (such as , ) Object: a resource that serves as a "record of intent". An object is a desired state for a specific part of your cluster, which the Kubernetes control plane tries to maintain. Add a rule to always mention "resource" or "object" when referring to an API resource in docs. For example, use "a object" over just "a ". Add a rule to always format API resource names with PascalCase and . (link users to and for full guidance) [ ] Review other API sections on the page to remove duplicate content or conflicting guidance. For example, has the following, which can be moved and merged into your new section: [ ] Link to for more information at the end of the section. /sig docs /help-wanted /cc
/language en /triage accepted
I could take this up /assign
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command.

<detailsIn response to : /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
have you completely solved this issue?
Yes, the pointers mentioned in the issue description have been addressed in the linked PR above. Kindly pick up another . Thanks for showing your interest


Question: # change is that the Hugo version is now an overridable argument rather than a fixed # environment variable. <del> FROM docker.io/library/golang:1.20-alpine </del> <ins> FROM docker.io/library/golang:1.23.0-alpine3.20 </ins> LABEL maintainer="Luc Perkins <lperkins@linuxfoundation.org>"

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: You cannot run to get a local website preview, nor can you run to build the container locally. Proposed Solution: Fix local previewing by ensuring that builds a working container image <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: This is relevant to contributor experience. Optionally, we could run CI tests whenever there is a change to , or , and verify that we can: build a container image run Hugo inside that image (smoke test)
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
I am unable to produce this because being blocked to , the command never worked for me (in China). I'm curious though what kind of errors we have encountered and why an upgrade of Go is required.
you can read more on this thread TLDR; the error was: ! Due to the latest Hugo upgrade that requires Golang 1.23 when building the image. The fix works locally: ! +1 to running a test in the CI. Would that be something completely new or a pre-existing pipeline to enhance? Asking because I don't see any other GitHub workflow aside from . Note: I'm still getting accustomed to the codebase so this question might sound silly._
Got it. A change to Go version is necessary.
To test the container image build locally, run . You need access to the Docker registry; you don't need access to push to Google.


Question: <ins> --- title: 节点资源管理器 content_type: concept weight: 50 --- <!-- --- reviewers: - derekwaynecarr - klueska title: Node Resource Managers content_type: concept weight: 50 --- --> <!-- overview --> <!-- In order to support latency-critical and high-throughput workloads, Kubernetes offers a suite of Resource Managers. The managers aim to co-ordinate and optimise node's resources alignment for pods configured with a specific requirement for CPUs, devices, and memory (hugepages) resources. --> Kubernetes 提供了一组资源管理器，用于支持延迟敏感的、高吞吐量的工作负载。 资源管理器的目标是协调和优化节点资源，以支持对 CPU、设备和内存（巨页）等资源有特殊需求的 Pod。 <!-- body --> <!-- The main manager, the Topology Manager, is a Kubelet component that co-ordinates the overall resource management process through its [policy](/docs/tasks/administer-cluster/topology-manager/). The configuration of individual managers is elaborated in dedicated documents: --> 主管理器，也叫拓扑管理器（Topology Manager），是一个 Kubelet 组件， 它通过[策略](/zh/docs/tasks/administer-cluster/topology-manager/)， 协调全局的资源管理过程。 各个管理器的配置方式会在专项文档中详细阐述： <!-- - [CPU Manager Policies](/docs/tasks/administer-cluster/cpu-management-policies/) - [Device Manager](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#device-plugin-integration-with-the-topology-manager) - [Memory Manger Policies](/docs/tasks/administer-cluster/memory-manager/) --> - [CPU 管理器策略](/zh/docs/tasks/administer-cluster/cpu-management-policies/) - [设备管理器](/zh/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#device-plugin-integration-with-the-topology-manager) - [内存管理器策略](/zh/docs/tasks/administer-cluster/memory-manager/) </ins>

This is a Feature Request translate /docs/concepts/policy/node-resource- into Chinese. What would you like to be /zh/docs/concepts/policy/node-resource-
/triage accepted


Question: kubectl get pod liveness-exec ``` <del> The output shows that `RESTARTS` has been incremented: </del> <ins> The output shows that `RESTARTS` has been incremented. Note that the `RESTARTS` counter increments as soon as a failed container comes back to the running state: </ins> ``` NAME            READY     STATUS    RESTARTS   AGE

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 documentation on readiness probes is unclear. It describes how to configure readiness for a single container, but when it comes to the restart behavior, it's not exactly clear, if just the container or the complete pod is restarted: the documentation says: but then command is used to show that the restart counter of the pod has been increased. It is not clear in the documentation, if this restart counter relates to all containers in the pod (meaning that all containers in that pod have been restarted due to failed readiness checks of a single container in that pod) or just a single container in the pod. In the example it does not matter because the pod consists of just a single container. Proposed Solution: Please clarify if a single failing container causes a restart of the whole pod or just of the affected container, and how it relates to the RESTARTS field of the output of the command. Page to Update:
/remove-kind bug This is a request to improve docs; the existing docs are unclear, not wrong. /language en /sig node /triage accepted
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
I would like to work on it.
/assign


Question: metadata: # ... spec: <ins> serviceAccountName: bob-the-bot </ins> containers: - name: nginx image: nginx:1.7.9 <del> serviceAccountName: bob-the-bot </del> ``` Service account bearer tokens are perfectly valid to use outside the cluster and

This is a... [ ] Feature Request [X] Bug Report Problem: Incorrect example at "Service Account Tokens". The documentation states: But in the example the serviceAccountName field has been set in the container field. Proposed Solution: Replace: With: Page to Update:
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
/lifecycle frozen /remove-lifecycle stale


Question: name: system:kube-scheduler apiGroup: rbac.authorization.k8s.io --- <ins> apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: name: my-scheduler-as-volume-scheduler subjects: - kind: ServiceAccount name: my-scheduler namespace: kube-system roleRef: kind: ClusterRole name: system:volume-scheduler apiGroup: rbac.authorization.k8s.io --- </ins> apiVersion: apps/v1 kind: Deployment metadata:

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: I followed the steps in tutorial. At the end of it the annotation-second-scheduler POD got into the pending state. Client Version: v1.17.0 Server Version: v1.17.0 Errors visible in my-scheduler POD: Proposed Solution: Remove lock-object-namespace and lock-object-name from There is no lock-object-namespace namespace, hence my-scheduler won't not work properly. In addition to that, add the following lines to clusterrole system:kube-scheduler: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
It looks to me as if ought to tell the reader to add a new namespace to hold lock objects. Does that sound right? /sig scheduling
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale
/assign
could you confirm if you were trying to set up leader election or not?


Question: |    node-1 *drained*  |       node-2        |       node-3       | *no node*          | |:--------------------:|:-------------------:|:------------------:|:------------------:| <del> |                      | pod-b *available*   | pod-c *available*  | pod-e *pending*    | </del> <ins> |                      | pod-b *terminating* | pod-c *available*  | pod-e *pending*    | </ins> |                      | pod-d *available*   | pod-y              |                    | At this point, the cluster administrator needs to

<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: The last table after the paragraph shows that pod-b available, which I think that it's wrong, because previously it says "It will succeed at evicting pod-b" Proposed Solution: pod-b terminating Page to Update:
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale
/priority backlog
/kind bug
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale
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: distros | 배포판 | Docker | 도커 | Dockerfile | Dockerfile | <ins> Docker Swarm | Docker Swarm | </ins> Downward API | 다운워드(Downward) API | draining | 드레이닝(draining) | egress | 이그레스, 송신(egress) |

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. --There are several Vendor's solution names that need to be maintained in the English when localizing documents. So, I suggest this word to be . English --- --- Docker Swarm Why is this needed This is for standardization of terminology when document is localized. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --Page to update: - /language ko
/assign
/language ko


Question: kubectl version --client --output=yaml ``` <del> 1. After installing the plugin, clean up the installation files: ```powershell del kubectl.exe kubectl.exe.sha256 ``` </del> {{< note >}} [Docker Desktop for Windows](https://docs.docker.com/docker-for-windows/#kubernetes)

I was doing the step-by-step installation for v1.26.3 and found this as the final step for installing on Windows: installing the plugin, clean up the installation files: del Please correct me if I am wrong, but isn't the kube controller that I just installed? It isn't an installer, it's the product. Your instruction should not be to delete it. If I delete then I won't have kubectl installed anymore. Make sense?
/kind bug /language en /triage accepted For Windows, we don't provide our own installable package and the instructions don't explain putting the kubectl binary anywhere special. Until that changes, let's not advise readers to delete .
do we have to comment down or delete the 5th instruction there ?
/assign


Question: {{< note >}} While any plugin can access the list of "waiting" Pods and approve them <del> (see [`FrameworkHandle`](https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/20180409-scheduling-framework.md#frameworkhandle)), we expect only the permit </del> <ins> (see [`FrameworkHandle`](https://git.k8s.io/enhancements/keps/sig-scheduling/624-scheduling-framework#frameworkhandle)), we expect only the permit </ins> plugins to approve binding of reserved Pods that are in "waiting" state. Once a Pod is approved, it is sent to the [PreBind](#pre-bind) phase. {{< /note >}}

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: "FrameworkHandle" link is broken. Proposed Solution: The link should be ( ) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en /triage accepted
/assign


Question: {{< feature-state for_k8s_version="v1.5" state="alpha" >}} <del> You can replicate Kubernetes control plane nodes in `kube-up` or `kube-down` scripts for Google Compute Engine. </del> <ins> You can replicate Kubernetes control plane nodes in `kube-up` or `kube-down` scripts for Google Compute Engine. However this scripts are not suitable for any sort of production use, it's widely used in the project's CI. </ins> This document describes how to use kube-up/down scripts to manage a highly available (HA) control plane and how HA control planes are implemented for use with GCE.

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: In , and scripts are mentioned. But according to 's , And the in (where the and scripts exist) says that Proposed Solution: ~Update to not mention and scripts.~ Delete and redirect it to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/kind cleanup /triage accepted
/sig cluster-lifecycle (ish)
/reopen The page still mentions those scripts.
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
I think it would probably be best to instead drop all reference to them, we have if we need to document details to upstream contributors, previously we did not and sort of did double-duty IMHO
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]:
Let's delete and redirect it to /lifecycle frozen do you agree with that approach? If so, please update the issue description to highlight it as a plan.
→ Yes! → Done!
/assign
Thanks all.


Question: </TABLE> </DIV> </DIV> <del> <SCRIPT src="/js/jquery-2.2.0.min.js"></SCRIPT> </del> <ins> <SCRIPT src="/js/jquery-3.2.1.min.js"></SCRIPT> </ins> <SCRIPT src="jquery.scrollTo.min.js"></SCRIPT> <del> <SCRIPT src="/js/bootstrap.min.js"></SCRIPT> </del> <ins> <SCRIPT src="/js/bootstrap-3.3.7.min.js"></SCRIPT> </ins> <SCRIPT src="navData.js"></SCRIPT> <SCRIPT src="scroll.js"></SCRIPT> </BODY>

<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [ ] Bug Report Problem: api doc reference not working properly due to jquery- and not found. 404 (Not Found) 404 (Not Found) Proposed Solution: put back the missing JS file Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--11 12 13 <!--Additional Information:--
12 works. 1.11 and 1.13 doesn't work.


Question: Lease | 리스(Lease) | API 오브젝트인 경우 lifecycle | 라이프사이클 | LimitRange | 리밋레인지(LimitRange) | API 오브젝트인 경우 <ins> limit | 한도(limit) | 리소스의 개수나 용량을 한정하기 위한 수치로 사용된 경우 선택적으로 사용 (API 오브젝트의 속성으로 limit을 사용한 경우는 가능한 영문 유지) </ins> Linux | 리눅스 | load | 부하 | LocalSubjectAccessReview | 로컬서브젝트액세스리뷰(LocalSubjectAccessReview) | API 오브젝트인 경우

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: / . '' '' . English | -- | -- Default Limit | Default Request | max limit/request ratio | / Resource Limit | Proposed Solution: / '' '' , . LimitRange API yaml English -- -- Default Limit Default Request max limit/request ratio Resource Limit limit ResourceQuota, LimitRange request ResourceQuota, LimitRange Page to Update: - <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ko
/assign
. before : LimitRange after : ResourceQuota, LimitRange LimitRange ResourceQuota .


Question: To build and test the site locally, run: ```bash <ins> # install dependencies npm ci </ins> make serve ```

This is a Bug Report As discussed in the SIG-Docs meeting, the current steps for building doc website in README is incomplete in the following point of views. It requires yarn on top of npm, but is missing and package- is there. did not work for me but I need further investigation on it. The build step is going to be equal in containerized and local in , but yarn installation or npm ci is currently missing in . <!--Required Information--Proposed Solution: and remove yarn from the dependency the npm command inside of the container Page to Update: N/A
Here's my cat picture after the sig-docs meeting lol !
AIUI, the live website build (within Netlify) relies on , and does not use Yarn.
/area web-development
Could you have a quick look if npm ci in local works just fine?
Yes, I believe so.
worked in my local environment
/kind bug /priority important-longterm
/sig contributor-experience I suppose


Question: sudo chown root: /usr/local/bin/kubectl ``` <ins> {{< note >}} Make sure `/usr/local/bin` is in your PATH environment variable. {{< /note >}} </ins> 1. Test to ensure the version you installed is up-to-date: ```bash

Hello, I installed Kubernetes using this method "Install kubectl binary with curl on MacOS". In step 5, I get the error "kubectl: command not found". MacOS version: 10.12.6 Could you please give a solution? Regards, Myat
Can you send me the reference document?
/kind support
reference document:
You can run . Check if is in the PATH. !
Let's mention that must be in your . This was a support request, but it's also a hint about how to improve the docs /remove-kind support /language en
/assign
Let me improve it.
/sig node
/remove-sig node
/sig cli
/triage accepted


Question: ``` `periodSeconds` indicates the length of time in the past for which the policy must hold true. <ins> The maximum value that you can set for `periodSeconds` is 1800 (half an hour). </ins> The first policy _(Pods)_ allows at most 4 replicas to be scaled down in one minute. The second policy _(Percent)_ allows at most 10% of the current replicas to be scaled down in one minute.

Facing error HorizontalPodAutoscaler.autoscaling "test" is invalid: spec.behavior.scaleDown.policies[0].periodSeconds: Invalid value: 3600: must be less than or equal to 1800 It is a limitation, I'd like to avoid scaling down a maximum of 1 pod every 1 hour not half an hour Add a scale down policy for a periodSeconds of 1 hour If the issue not resolved, better to modify the documentation to clearly mention that this is a limitation and the maximum value of must be less than or equal half an hour <details</details<detailsAWS EKS </details<details</details<details</details<details</details<details</details
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. 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
/sig Docs
For Reference This is a well-thought-out limit set in this PR:
However, mentioning this in yaml or in a note in the Default behaviour section doesn't sound bad. You can raise the issue in for contribution related help please go through t
Let's move this to k/website /transfer website
/sig autoscaling /kind feature /remove-kind bug
/assign
/triage accepted /priority backlog


Question: {{< feature-state for_k8s_version="v1.16" state="beta" >}} <del> As of Kubernetes v1.16, RuntimeClass includes support for heterogeneous clusters through its `scheduling` fields. Through the use of these fields, you can ensure that pods running with this RuntimeClass are scheduled to nodes that support it. To use the scheduling support, you must have the [RuntimeClass admission controller](/docs/reference/access-authn-authz/admission-controllers/#runtimeclass) enabled (the default, as of 1.16). </del> <ins> By specifying the `scheduling` field for a RuntimeClass, you can set constraints to ensure that Pods running with this RuntimeClass are scheduled to nodes that support it. If `scheduling` is not set, this RuntimeClass is assumed to be supported by all nodes. </ins> To ensure pods land on nodes supporting a specific RuntimeClass, that set of nodes should have a common label which is then selected by the `runtimeclass.scheduling.nodeSelector` field. The

RuntimeClass feature gate is GA in 1.20. According to , a GA feature cannot be disabled and the feature gate is no longer needed. The explanation below can be removed.
triage/accepted
/language en
/triage accepted
/assign


Question: <ins> --- title: Kerangka Kerja Penjadwalan (Scheduling Framework) content_type: concept weight: 60 --- <!-- overview --> {{< feature-state for_k8s_version="1.15" state="alpha" >}} Kerangka kerja penjadwalan (_Scheduling Framework_) adalah arsitektur yang dapat dipasang (_pluggable_) pada penjadwal Kubernetes untuk membuat kustomisasi penjadwal lebih mudah. Hal itu dilakukan dengan menambahkan satu kumpulan "plugin" API ke penjadwal yang telah ada. _Plugin_ dikompilasi ke dalam penjadwal. Beberapa API memungkinkan sebagian besar fitur penjadwalan diimplementasikan sebagai _plugin_, sambil tetap mempertahankan penjadwalan "inti" sederhana dan terpelihara. Silahkan merujuk pada [proposal desain dari kerangka penjadwalan] [kep] untuk informasi teknis lebih lanjut tentang desain kerangka kerja tersebut. [kep]: https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/20180409-scheduling-framework.md <!-- body --> # Alur kerja kerangka kerja Kerangka kerja penjadwalan mendefinisikan beberapa titik ekstensi. _Plugin_ penjadwal mendaftar untuk dipanggil di satu atau lebih titik ekstensi. Beberapa _plugin_ ini dapat mengubah keputusan penjadwalan dan beberapa hanya bersifat informasi. Setiap upaya untuk menjadwalkan satu Pod dibagi menjadi dua fase, **Siklus Penjadwalan (_Scheduling Cycle_)** dan **Siklus Pengikatan (_Binding Cycle_)**. ## Siklus Penjadwalan dan Siklus Pengikatan Siklus penjadwalan memilih sebuah Node untuk Pod, dan siklus pengikatan menerapkan keputusan tersebut ke klaster. Secara bersama-sama, siklus penjadwalan dan siklus pengikatan diartikan sebagai sebuah "konteks penjadwalan (_scheduling context_)". Siklus penjadwalan dijalankan secara serial, sementara siklus pengikatan dapat berjalan secara bersamaan. Siklus penjadwalan atau pengikatan dapat dibatalkan jika Pod telah ditentukan untuk tidak terjadwalkan atau jika terdapat kesalahan internal. Pod akan dikembalikan ke antrian dan dicoba lagi. ## Titik-titik ekstensi Gambar berikut menunjukkan konteks penjadwalan Pod dan titik-titik ekstensi yang diperlihatkan oleh kerangka penjadwalan. Dalam gambar ini "Filter" setara dengan "Predicate" dan "Scoring" setara dengan "Priority Function". Satu _plugin_ dapat mendaftar di beberapa titik ekstensi untuk melakukan pekerjaan yang lebih kompleks atau _stateful_. {{< figure src="/images/docs/scheduling-framework-extensions.png" title="Titik-titik ekstensi dari kerangka kerja Penjadwalan" >}} ### QueueSort {#queue-sort} _Plugin_ ini digunakan untuk mengurutkan Pod-Pod dalam antrian penjadwalan. _Plugin_ QueueSort pada dasarnya menyediakan fungsi `Less (Pod1, Pod2)`. Hanya satu jenis _plugin_ QueueSort yang dapat diaktifkan dalam waktu yang bersamaan. ### PreFilter {#pre-filter} _Plugin_ ini digunakan untuk melakukan pra-proses informasi tentang Pod, atau untuk memeriksa tertentu kondisi yang harus dipenuhi oleh klaster atau Pod. Jika _plugin_ PreFilter menghasilkan hasil yang salah, siklus penjadwalan dibatalkan. ### Filter _Plugin_ ini digunakan untuk menyaring Node yang tidak dapat menjalankan Pod. Untuk setiap Node, penjadwal akan memanggil _plugin_ Filter sesuai dengan urutan mereka dikonfigurasi. Jika ada _plugin_ Filter menandai Node menjadi _infeasible_, maka _plugin_ yang lainnya tidak akan dipanggil untuk Node itu. Node-Node dapat dievaluasi secara bersamaan. ### PostFilter {#post-filter} Plugin ini disebut setelah fase Filter, tetapi hanya ketika tidak ada node yang layak ditemukan untuk pod. Plugin dipanggil dalam urutan yang dikonfigurasi. Jika plugin postFilter menandai node sebagai 'Schedulable', plugin yang tersisa tidak akan dipanggil. Implementasi PostFilter yang khas adalah preemption, yang mencoba membuat pod dapat di menjadwalkan dengan mendahului Pod lain. ### PreScore {#pre-score} _Plugin_ ini digunakan untuk melakukan pekerjaan "pra-penilaian", yang menghasilkan keadaan yang dapat dibagi untuk digunakan oleh _plugin-plugin_ Score. Jika _plugin_ PreScore mengeluarkan hasil salah, maka siklus penjadwalan dibatalkan. ### Score {#score} _Plugin_ ini digunakan untuk menentukan peringkat Node yang telah melewati fase penyaringan. Penjadwal akan memanggil setiap _plugin_ Score untuk setiap Node. Akan ada kisaran bilangan bulat yang telah ditetapkan untuk mewakili skor minimum dan maksimum. Setelah fase [NormalizeScore](#normalize-scoring), penjadwal akan menggabungkan skor Node dari semua _plugin_ sesuai dengan bobot _plugin_ yang telah dikonfigurasi. ### NormalizeScore {#normalize-score} _Plugin_ ini digunakan untuk memodifikasi skor sebelum penjadwal menghitung peringkat akhir Node-Node. _Plugin_ yang mendaftar untuk titik ekstensi ini akan dipanggil dengan hasil [Score](#score) dari _plugin_ yang sama. Hal ini dilakukan sekali untuk setiap _plugin_ dan setiap siklus penjadwalan. Sebagai contoh, anggaplah sebuah _plugin_ `BlinkingLightScorer` memberi peringkat pada Node-Node berdasarkan berapa banyak kedipan lampu yang mereka miliki. ```go func ScoreNode(_ *v1.pod, n *v1.Node) (int, error) { return getBlinkingLightCount(n) } ``` Namun, jumlah maksimum kedipan lampu mungkin kecil jika dibandingkan dengan `NodeScoreMax`. Untuk memperbaikinya, `BlinkingLightScorer` juga harus mendaftar untuk titik ekstensi ini. ```go func NormalizeScores(scores map[string]int) { highest := 0 for _, score := range scores { highest = max(highest, score) } for node, score := range scores { scores[node] = score*NodeScoreMax/highest } } ``` Jika ada _plugin_ NormalizeScore yang menghasilkan hasil yang salah, maka siklus penjadwalan dibatalkan. {{< note >}} _Plugin_ yang ingin melakukan pekerjaan "pra-pemesanan" harus menggunakan titik ekstensi NormalizeScore. {{< /note >}} ### Reserve Ini adalah titik ekstensi yang bersifat informasi. _Plugin_ yang mempertahankan keadaan _runtime_ (alias "_stateful plugins_") harus menggunakan titik ekstensi ini untuk diberitahukan oleh penjadwal ketika sumber daya pada suatu Node dicadangkan untuk Pod yang telah disiapkan. Proses ini terjadi sebelum penjadwal benar-benar mengikat Pod ke Node, dan itu ada untuk mencegah kondisi balapan (_race conditions_) ketika penjadwal menunggu agar pengikatan berhasil. Ini adalah langkah terakhir dalam siklus penjadwalan. Setelah Pod berada dalam status dicadangkan, maka itu akan memicu _plugin_ [Unreserve](#unreserve) (apabila gagal) atau _plugin_ [PostBind](#post-bind) (apabila sukses) di akhir siklus pengikatan. ### Permit _Plugin_ Permit dipanggil pada akhir siklus penjadwalan untuk setiap Pod untuk mencegah atau menunda pengikatan ke Node kandidat. _Plugin_ Permit dapat melakukan salah satu dari ketiga hal ini: 1. **approve**  Setelah semua _plugin_ Permit menyetujui sebuah Pod, Pod tersebut akan dikirimkan untuk diikat. 2. **deny**  Jika ada _plugin_ Permit yang menolak sebuah Pod, Pod tersebut akan dikembalikan ke antrian penjadwalan. Hal ini akan memicu _plugin_ [Unreserve](#unreserve). 3. **wait** (dengan batas waktu)  Jika _plugin_ Permit menghasilkan "wait", maka Pod disimpan dalam daftar Pod "yang menunggu" internal, dan siklus pengikatan Pod ini dimulai tetapi akan langsung diblokir sampai mendapatkan [_approved_](#frameworkhandle). Jika waktu tunggu habis, ** wait ** menjadi ** deny ** dan Pod dikembalikan ke antrian penjadwalan, yang memicu _plugin_ [Unreserve](#unreserve). {{< note >}} Ketika setiap _plugin_ dapat mengakses daftar Pod-Pod "yang menunggu" dan menyetujuinya (silahkan lihat [`FrameworkHandle`](#frameworkhandle)), kami hanya mengharapkan _plugin_ Permit untuk menyetujui pengikatan Pod dalam kondisi "menunggu" yang telah dipesan. Setelah Pod disetujui, akan dikirim ke fase [PreBind](#pre-bind). {{< /note >}} ### PreBind {#pre-bind} _Plugin_ ini digunakan untuk melakukan pekerjaan apa pun yang diperlukan sebelum Pod terikat. Sebagai contoh, _plugin_ PreBind dapat menyediakan _network volume_ dan melakukan _mounting_ pada Node target sebelum mengizinkan Pod berjalan di sana. Jika ada _plugin_ PreBind yang menghasilkan kesalahan, maka Pod [ditolak](#unreserve) dan kembali ke antrian penjadwalan. ### Bind _Plugin_ ini digunakan untuk mengikat Pod ke Node. _Plugin-plugin_ Bind tidak akan dipanggil sampai semua _plugin_ PreBind selesai. Setiap _plugin_ Bind dipanggil sesuai urutan saat dikonfigurasi. _Plugin_ Bind dapat memilih untuk menangani atau tidak Pod yang diberikan. Jika _plugin_ Bind memilih untuk menangani Pod, ** _plugin_ Bind yang tersisa dilewati **. ### PostBind {#post-bind} Ini adalah titik ekstensi bersifat informasi. _Plugin-plugin_ PostBind dipanggil setelah sebuah Pod berhasil diikat. Ini adalah akhir dari siklus pengikatan, dan dapat digunakan untuk membersihkan sumber daya terkait. ### Unreserve Ini adalah titik ekstensi bersifat informasi. Jika sebuah Pod telah dipesan dan kemudian ditolak di tahap selanjutnya, maka _plugin-plugin_ Unreserve akan diberitahu. _Plugin_ Unreserve harus membersihkan status yang terkait dengan Pod yang dipesan. _Plugin_ yang menggunakan titik ekstensi ini sebaiknya juga harus digunakan [Reserve](#unreserve). ## _Plugin_ API Ada dua langkah untuk _plugin_ API. Pertama, _plugin_ harus mendaftar dan mendapatkan konfigurasi, kemudian mereka menggunakan antarmuka titik ekstensi. Antarmuka (_interface_) titik ekstensi memiliki bentuk sebagai berikut. ```go type Plugin interface { Name() string } type QueueSortPlugin interface { Plugin Less(*v1.pod, *v1.pod) bool } type PreFilterPlugin interface { Plugin PreFilter(context.Context, *framework.CycleState, *v1.pod) error } // ... ``` ## Konfigurasi _plugin_ Kamu dapat mengaktifkan atau menonaktifkan _plugin_ dalam konfigurasi penjadwal. Jika kamu menggunakan Kubernetes v1.18 atau yang lebih baru, kebanyakan [plugin-plugin penjadwalan](/docs/reference/scheduling/profiles/#scheduling-plugins) sudah digunakan dan diaktifkan secara bawaan. Selain _plugin-plugin_ bawaan, kamu juga dapat mengimplementasikan _plugin-plugin_ penjadwalan kamu sendiri dan mengonfigurasinya bersama-sama dengan _plugin-plugin_ bawaan. Kamu bisa mengunjungi [plugin-plugin penjadwalan](https://github.com/kubernetes-sigs/scheduler-plugins) untuk informasi lebih lanjut. Jika kamu menggunakan Kubernetes v1.18 atau yang lebih baru, kamu dapat mengonfigurasi sekumpulan _plugin_ sebagai profil penjadwal dan kemudian menetapkan beberapa profil agar sesuai dengan berbagai jenis beban kerja. Pelajari lebih lanjut di [multi profil](/docs/reference/scheduling/profiles/#multiple-profiles). </ins>

This is tracking issue of our progress from Q1 2021 onwards. In the beginning of this milestone, as per our , we have translated 220 pages from 84 contributors (the script from main repo shows 260+ pages), with around 8,000 views per month. In this milestone, we still continuing on updating the obsolete pages. We are not officially listing down target pages to translate, but feel free if you have spare time to translate some. Please check this documentation about which gives step-by-step on how to start to contribute and translate using official guidelines. There is a list of outdated pages (40 out of 162 pages for this milestone) and please feel free if you want to take part on this work.

[X] removed [X] removed content/en//docs/tasks/tools/install- [X] removed [X] removed content/en//docs/tasks/example-task- [X] removed content/en//docs/tasks/administer-cluster/cluster- [X] removed content/en//docs/setup/learning- [X] removed content/en//docs/concepts/configuration/assign-pod- [X] removed content/en//docs/concepts/configuration/pod- [ ] removed content/en//docs/concepts/configuration/manage-compute-resources- [X] moved content/en//docs/concepts/configuration/resource-bin- [X] moved content/en//docs/concepts/configuration/taint-and- [X] renamed content/en//docs/concepts/scheduling/scheduling- [X] renamed content/en//docs/concepts/scheduling/scheduler-perf- [X] renamed content/en//docs/concepts/scheduling/kube- [X] renamed [ ] removed content/en//docs/concepts/workloads/pods/pod-[ ] removed [ ] removed content/en//docs/concepts/workloads/controllers/jobs-run-to- [ ] removed content/en//docs/concepts/extend-kubernetes/poseidon-firmament-alternate- [ ] removed [ ] removed content/en//docs/concepts/cluster-administration/cluster-administration- [ ] removed content/en//docs/concepts/cluster- [ ] removed content/en//docs/concepts/cluster-administration/cloud- [ ] removed content/en//docs/concepts/cluster-administration/controller-[X] removed content/en//docs/concepts/cluster- [X] removed [X] removed [X] removed [X] modified content/en/includes/task-tutorial- [X] modified content/en/docs/home/supported-doc- [ ] modified [ ] modified content/en/docs/tasks/debug-application-cluster/resource-usage-[ ] modified content/en/docs/tasks/run-application/horizontal-pod-autoscale- [ ] modified content/en/docs/tasks/run-application/horizontal-pod- [ ] modified content/en/docs/tasks/run-application/run-stateless-application- [ ] modified content/en/docs/tasks/run-application/force-delete-stateful-set- [ ] modified content/en/docs/tasks/tools/install- [ ] modified [ ] modified content/en/docs/tasks/configure-pod-container/configure-service- [ ] modified content/en/docs/tasks/configure-pod-container/configure-persistent-volume- /language id /cc
/triage accepted
I'm taking the 4th part, as I've done the in
Thanks .

it is updated.
is moved to as mentioned here
is removed and redirect to official minikube webpage , as mentioned here
The whole pages are move into including as mentioned here
The whole are removed in , I'm going to remove the directory as well as it's unused now.
is moved to via
is removed via
Just sharing a useful trick for finding related PR which delete/modified a file: e.g. The output will be similar with this: Please note the commit hash in the output (, in the case of the example above). You can use the same command to find which commit modified a file by changing the filter from to (refer to for more filters). In case of modified file, you might get multiple commit hashes, pick the latest one (contains the recent changes), or just pick ones that suit your needs. Go to, e.g., (replace with your commit hash in step 1). Find the related PR with the commit, e.g. via web UI: ! In bottom left hand corner near the branch name, in this case , you can see the PR id . Click on the link and you will be redirected to the respective PR page, then you can analyse what changes has been made and what actions needed to incorporate it to our localization.
is removed here together with others.
is removed here
Hi ... it seems this issue is automatically closed. Do you have any idea how to re-opened it?
/reopen
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Thanks :)
/reopen
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Hi .... I think we need to close this issue, because it has already behind the schedule. Do we need to complete all within 1-2 weeks? or we need to carry forward to next quarter?
Hi All, I have opened Q2 2021 tracking issue


Question: [thirdparty_message_vendor] other = """Items on this page refer to vendors external to Kubernetes. The Kubernetes project authors aren't responsible for those third-party products or projects. To add a vendor, product or project to this list, read the content guide before submitting a change. More information."""  [translated_by] other = "Translated By"  [ui_search_placeholder] other = "Search this site"

This is a Feature Request What would you like to be In , the "author" metadata was to the front matter. Currently, some l10n teams are also setting "translator" metadata. This is one of the initiatives to promote the localization of blog posts. FYI: I would like to add "translator" metadata to the blog's front matter, just like the author metadata. Why is this needed To promote the localization of blog articles. This would be a significant motivation for those involved in localization. Comments
/area web-development /area blog /area localization
/assign
This is a great idea. It will be very motivating for localization contributors.
Thank you for your interest in this issue, mengjiao-liu ! I've opened a pull request to resolve it - . please have a look :)
Would be nice to add this feature. /priority backlog /triage accepted


Question: <ins> --- title: 使用 Kind 安装 Kubernetes weight: 40 content_type: concept --- <!-- overview --> <!-- Kind is a tool for running local Kubernetes clusters using Docker container "nodes". --> Kind 是一个使用 Docker 容器“节点”运行本地 Kubernetes 集群的工具。 <!-- body --> <!-- ## Installation See [Installing Kind](https://kind.sigs.k8s.io/docs/user/quick-start/). --> ## 安装  {#installation} 参见[安装 Kind ](https://kind.sigs.k8s.io/docs/user/quick-start/)。 </ins>

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: The `expiration` field controls the expiry of the token. Expired tokens are rejected when used for authentication and ignored during ConfigMap signing. <del> The expiry value is encoded as an absolute UTC time using RFC3339. Enable the </del> <ins> The expiry value is encoded as an absolute UTC time using [RFC3339](https://datatracker.ietf.org/doc/html/rfc3339). Enable the </ins> `tokencleaner` controller to automatically delete expired tokens. ## Token Management with kubeadm

This is a Feature Request What would you like to be Add the following hyperlink to under the in reference docs. Why is this needed Adding the hyperlink will help the readers to know about RFC3339. Proposed Solution: Where to add this link: In above code instead of it should be Comments /sig docs /language en
/sig auth /triage accepted /good-first-issue Please save this for a new contributor to the Kubernetes documentation. This is a great opportunity for new contributor to make their first contribution to the k8s project.
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /sig auth /triage accepted /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details


Question: * [Daemon Sets](http://kubernetes.io/docs/admin/daemons/) which ensure that all or some of the nodes in your cluster run a copy of a Pod. * [Deployments](http://kubernetes.io/docs/user-guide/deployments/) which provide declarative updates for Pods and Replica Sets (the next-generation [Replication Controller](http://kubernetes.io/docs/user-guide/replication-controller/)) The Details page for a Deployment lists resource details, as well as new and old Replica Sets. The resource details also include information on the [RollingUpdate](http://kubernetes.io/docs/user-guide/rolling-updates/) strategy, if any. <del> * [Pet Sets](http://kubernetes.io/docs/user-guide/load-balancer/) (nominal Services, also known as load-balanced Services) for legacy application support. </del> <ins> * [Pet Sets](http://kubernetes.io/docs/user-guide/petset/) (nominal Services, also known as load-balanced Services) for legacy application support. </ins> * [Replica Sets](http://kubernetes.io/docs/user-guide/replicasets/) for using label selectors. * [Jobs](http://kubernetes.io/docs/user-guide/jobs/) for creating one or more Pods, ensuring that a specified number of them successfully terminate, and tracking the completions. * [Replication Controllers](http://kubernetes.io/docs/user-guide/replication-controller/)

[ ] Feature Request [x] Bug Report /kind bug Flex volume docs still stay the feature is Alpha. We made it GA in Kube 1.8 time frame. We have to update the docs to reflect it. /sig storage Kubernetes version: 1.9 or master
Create new docs issue
Fixed in


Question: <!--more--> Containers decouple applications from underlying host infrastructure to make deployment easier in different cloud or OS environments, and for easier scaling. <ins> The applications that run inside containers are called containerized applications. The process of bundling these applications and their dependencies into a container image is called containerization. </ins>

This is a Feature Request What would you like to be Add Abbreviation of in as this word mentioned in . Why is this needed This change will help to understand about containerized applications for the people who are unfamiliar with . Comments kind/feature
/assign
When you say ”abbreviation”, do you mean “explanation”? We might like to borrow from or We also already have - maybe we can expand that? /language en
Hi Yes, basic Explanation/information about . Yes, my idea is same to expand this by adding about . WDYT? If you think it's better to borrow from here, i can follow the same. Please provide your opinion.
Hi Can you please comment on above.
I recommend expanding rather than adding a new entry for “containerized application”. I don't mind whether or not you borrow from the Cloud Native Glossary - feel free to do it whichever way you prefer.
Thanks for your comment, I will work on it and raise PR soon.
Fixed it here .
Should we make this change? Any objections?
Personally, I like what's done here, and I was just waiting for someone with "better experience" in the glossary entries to approve it.
Hi Thanks for sharing your feedback. Can anyone else please comment on it.
/triage accepted


Question: requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: <del> - key: topology.kubernetes.io/zone </del> <ins> - key: kubernetes.io/os </ins> operator: In values: <del> - antarctica-east1 - antarctica-west1 </del> <ins> - linux </ins> preferredDuringSchedulingIgnoredDuringExecution: - weight: 1 preference:

Description of Node Affinity example pod spec "pods/pod-with-node-" contains an error: does not apply. The spec shows instead that key "" should be "". Under the Node Affinity Weight section, the following note is also out-of-place: It needs to be moved to the previous section.
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
This issue is a duplicate of . /triage duplicate

Just above this anchor #node-affinity-per-scheduling-profile, the note block is referring to the Pod spec pod-with-node- 2 above, but it's placement appears to refer to the one immediately above. It takes a little bouncing around the page to sort it out :)
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

Only minor confusion, after the first example Pod spec, where "In this example, the following rules apply:" the bullet points that follow are misleading where first bullet refers to the example below, the second to the example above.
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details

! The label with the key not exist in the example for node affinity:
/kind bug /language en /triage accepted Thanks for reporting this. I would fix this discrepancy by copying the example manifest to make a new example, that does use the key key. The Git history might show a previous version that already did, which would make it easier to write the copy. The reason I'd make that copy is because I suspect that more than one page relies on the same example (and that's why an unhelpful change has slipped through).
/assign


Question: requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: <del> - key: topology.kubernetes.io/zone </del> <ins> - key: kubernetes.io/os </ins> operator: In values: <del> - antarctica-east1 - antarctica-west1 </del> <ins> - linux </ins> preferredDuringSchedulingIgnoredDuringExecution: - weight: 1 preference:

pods/pod-with-node-affinity.yaml
Page: /language zh
/triage accepted The YAML file was not sync'ed with English version.
/assign


Question: } window.getPaginationAnchors = (pages) => { <del> var pageAnchors = '', searchTerm  = window.location.search.split("=")[1].split("&")[0]; </del> <ins> var pageAnchors = '', searchTerm  = window.location.search.split("=")[1].split("&")[0].replace(/%20/g, ' '); </ins> var currentPage = window.location.search.split("=")[2]; currentPage = (!currentPage) ?  1 : currentPage.split("&")[0];

Searching keyword including space is not working. If you search one keyword, for example, "command", it will work. But, if "command and args" is input, the search result shows "Fetching results..." and do not return the result.
Hello, Thank you for pointing out the issue! I confirmed the same problem happens when searching the keyword "command and args" (). And I'll investigate the cause of this problem and fix it. /assign
BTW this applies to users using Bing search from China. See PR
are these symptoms still occurring? We're seeing different reports.
I have confirmed that this issue has dissapeared! Thank you for dealing with!
I'm glad to hear that!
I've had this problem now. But it disappeared because I used a different browser (chrome to Firefox).


Question: --- reviewers: - sig-cluster-lifecycle  title: Creating a single control-plane cluster with kubeadm   title: Creating a cluster with kubeadm  content_type: task weight: 30 ---   The `kubeadm` tool helps you bootstrap a minimum viable Kubernetes cluster that conforms to best practices. In fact, you can use `kubeadm` to set up a cluster that will pass the [Kubernetes Conformance tests](https://kubernetes.io/blog/2017/10/software-conformance-certification).   Creating a minimum viable Kubernetes cluster that conforms to best practices. In fact, you can use `kubeadm` to set up a cluster that will pass the [Kubernetes Conformance tests](https://kubernetes.io/blog/2017/10/software-conformance-certification).  `kubeadm` also supports other cluster lifecycle functions, such as [bootstrap tokens](/docs/reference/access-authn-authz/bootstrap-tokens/) and cluster upgrades.

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 title of used to be “Creating a single master cluster with kubeadm” and PR changed that to “Creating a single control-plane cluster with kubeadm” to match guidelines on terminology. However, the current title does not read as idiomatic English and could also mislead readers. All Kubernetes clusters should have exactly 1 control plane. You might have 0 control planes I suppose, in which case you need to fix that so that your workloads remain managed. You can't have 2 control planes for 1 cluster. What you can do is run your control plane across multiple hosts and even zones, to provide resilience. For that reason, it isn't the control plane that is single; instead, this page explains how to deploy a cluster where the control plane runs on only one computer. Proposed Solution: Change the title of the page. Pick wording that makes it clear that it's a simple cluster setup and isn't suitable for keeping your cluster within a low error budget (this is because if the one control plane host fails then you lose all control loops, the persisted data in etcd, and the Kubernetes cluster API). You don't need to go into all that detail so long as the reader is aware that another page explains how to do roughly the same thing but with availability taken into consideration. Also reword the following text from the body of the page: Optionally, add or revise introductory text to clarify the limitations of what this page is teaching. For example, consider if text “a minimum viable Kubernetes cluster that conforms to best practices” is the right fit? Page to Update: Additional Information: /sig cluster-lifecycle /language en /kind cleanup /priority backlog /good-first-issue If you're looking to pick this up as a first issue and would like advice, go ahead and reply - a Kubernetes contributor will help you to get started. Also, because this issue is not especially urgent, if you have already made a few contributions to this documentation, please consider leaving this one as a starting point for someone new.
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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: The title of used to be “Creating a single control-plane cluster with kubeadm” and PR changed that to “Creating a single control-plane cluster with kubeadm” to match guidelines on terminology. However, the current title does not read as idiomatic English and could also mislead readers. Change the title of the page. Pick wording that makes it clear that it's a simple cluster setup and isn't suitable for keeping your cluster within a low error budget, because if the one control plane host fails then you lose all control loops, the persisted data in etcd, and the Kubernetes cluster API. /sig cluster-lifecycle /language en /kind cleanup /priority backlog /good-first-issue If you're looking to pick this up as a first issue and would like advice, go ahead and reply - a Kubernetes contributor will help you to get started. Also, because this issue is not especially urgent, if you have already made a few contributions to this documentation, please consider leaving this one as a starting point for someone new. 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
my vote goes for: "Creating a cluster with kubeadm" and the page should link to the HA guide which is an optional extension. Install a single control-plane Kubernetes cluster or high-availability cluster "Creating a minimum viable Kubernetes cluster that conforms to best practices", seems good to me. The HA guide link (link under "high-availability cluster") can be moved under "higher availabilty" in this sentence: "Use multiple control-plane nodes. You can read Options for Highly Available topology to pick a cluster topology that provides higher availabilty." it's currently a bullet item here:
I think I can help with this one, if it's OK /assign
Anyone is welcome to open a pull request that makes the changes suggested, or otherwise helps get the issue done.


Question: ### kubectlの自動補完を有効にする <del> すべてのシェルセッションにてkubectlの補完スクリプトをsourceできるようにしなければなりません。 </del> <ins> 次に、kubectl補完スクリプトがすべてのシェルセッションで読み込まれるように設定する必要があります。 </ins> これを行うには複数の方法があります: <del> - 補完スクリプトを`~/.bash_profile`内でsourceする: </del> <ins> - 補完スクリプトを`~/.bash_profile`内で読み込ませる: </ins> ```bash echo 'source <(kubectl completion bash)' >>~/.bash_profile

This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Update Why is this needed Reflect the following feedback on this file, too. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/area localization /triage accepted


Question: ``` 크론 잡을 삭제하면 생성된 모든 잡과 파드가 제거되고 추가 잡 생성이 중지된다. <del> [가비지(garbage) 수집](/ko/docs/concepts/workloads/controllers/garbage-collection/)에서 잡 제거에 대해 상세한 내용을 읽을 수 있다. </del> <ins> [가비지(garbage) 수집](/ko/docs/concepts/architecture/garbage-collection/)에서 잡 제거에 대해 상세한 내용을 읽을 수 있다. </ins> ## 크론 잡 명세 작성

This is a Feature Request Translate in Korean What would you like to be Translate in Korean Why is this needed This file is not translated yet. Comments Page to translate : /language ko /assign Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/triage accepted
Resolved by page: /close
Closing this issue. <detailsIn response to : Resolved by Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details


Question: {{% capture overview %}} An [Ingress](/docs/concepts/services-networking/ingress/) is an API object that defines rules which allow external access <del> to services in a cluster. An [Ingress controller](/docs/concepts/services-networking/ingress-controllers/) fulfills the rules set in the Ingress. {{< caution >}} For the Ingress resource to work, the cluster **must** also have an Ingress controller running. {{< /caution >}} </del> <ins> to services in a cluster. An [Ingress controller](/docs/concepts/services-networking/ingress-controllers/) fulfills the rules set in the Ingress. </ins> This page shows you how to set up a simple Ingress which routes requests to Service web or web2 depending on the HTTP URI.

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 page has a cautionary note about a prerequisite: this note belongs on the page, however the best place for it is in the Prerequisites section. Proposed Solution: Edit the page to move the caution note to be the very first thing inside the prerequisites section. Page to Update: /language en /kind cleanup /good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: The page has a cautionary note about a prerequisite: Caution: For the Ingress resource to work, the cluster must also have an Ingress controller running. Edit the page to move the caution note to be the very first thing inside the prerequisites section. /kind cleanup /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
If you are looking to work on this and would like help, please reply here. I'll watch for replies.
Isn't there an effort underway to move minikube related pages onto the minikube site? and
I can work on this one! Should I?
I am looking to start contributing. looks like ..I can start with this.
Go for it! Contributions welcome. Bear in mind when it comes to deciding if you want to work on this. I think this example only happens to use Minikube; a separate PR could rework it to explain how to try out Ingress with a different kind of learning environment.
I'm reviewing the content and looks like the tutorial is explaining how to deploy the Ingress Controller, which is exactly what the caution note is mentioning. IMHO, the caution node should be removed instead of moved to other section.
another good point is that is saying the user could use Kubernetes playgrounds (Katacoda, play-with-k8s) which are not Minikube.
Sure, it's OK to remove the caution note. sounds like it could be a new separate issue(?)


Question: taints specifies the taints the Node API object should be registered with.  If this field is unset, i.e. nil, in the kubeadm init process it will be defaulted to 'node-role.kubernetes.io/master=""'. If you don't want to taint your control-plane node, set this field to an empty list, i.e. taints: [] in the YAML file. This field is   If this field is unset, i.e. nil, in the kubeadm init process it will be defaulted with a control-plane taint for control-plane nodes. If you don't want to taint your control-plane node, set this field to an empty list, i.e. taints: [], in the YAML file. This field is  solely used for Node registration.

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: while cleaning up mentions of the legacy "master" taint in kubeadm docs: saw the following: it seems the generated reference API docs for kubeadm still include the "master" taint. Proposed Solution: cleanup mentions of the old taint from kubeadm's API reference docs at perhaps these need to be synced with: for dev-1.25 and main at k/website we removed the old taint from there before 1.24 was released. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/sig cluster-lifecycle /priority important-soon /kind cleanup
cc


Question:
Open the /_data/concepts.yaml file.	Open the /_data/concepts.yaml file.

  ### Use the international standard for punctuation inside quotes

Do	Don't

events are recorded with an associated "stage".	events are recorded with an associated "stage."

The copy is called a "fork".	The copy is called a "fork."

  ## Inline code formatting ### Use code style for inline code and commands

This is a... [x] Feature Request [ ] Bug Report Problem: From : We should document that K8s follows the international standard for punctuation inside quotes. For example, the American standard: the international standard: Proposed Solution: Add a page for punctuation to the .