Question: バグを報告する場合は、そのバグを再現するための詳細な情報を含めてください。 * Kubernetes のバージョン: `kubectl version` <del> * クラウドプロバイダー、OSディストリビューション、ネットワーク構成、Dockerバージョン </del> <ins> * クラウドプロバイダー、OSディストリビューション、ネットワーク構成、コンテナランタイムバージョン </ins> * 問題を再現するための手順

This is a Feature Request What would you like to be We need to update according to the English text, because it is outdated. Why is this needed "Questions", "Stack Overflow" and "Bugs and feature requests" sections are outdated. Questions: Change the URL /docs/reference/kubectl/overview/ to /docs/reference/kubectl/ for . Stack Overflow: Update the statement for how to ask a new question. Bugs and feature requests: Change "Docker version" to "container runtime version". Comments /language ja
/triage accepted
/assign


Question:
The Control Plane is responsible for managing the cluster. The Control Plane coordinates all activities in your cluster, such as scheduling applications, maintaining applications' desired state, scaling applications, and rolling out new updates.

A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster. Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes control plane. The node should also have tools for handling container operations, such as containerd or Docker. A Kubernetes cluster that handles production traffic should have a minimum of three nodes because if one node goes down, both an etcd member and a control plane instance are lost, and redundancy is compromised. You can mitigate this risk by adding more control plane nodes.

A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster. Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes control plane. The node should also have tools for handling container operations, such as {{< glossary_tooltip text="containerd" term_id="containerd" >}} or {{< glossary_tooltip term_id="cri-o" >}}. A Kubernetes cluster that handles production traffic should have a minimum of three nodes because if one node goes down, both an etcd member and a control plane instance are lost, and redundancy is compromised. You can mitigate this risk by adding more control plane nodes.

In the third sentence on the second paragraph it reads: | operations, such as containerd or Docker. It is not clear if is a typo or a new term.
I believe writing "such as containerd or Docker" was not necessary because it was not very accurate , only writing till operations is fine enough . But still it is not an issue there .
is a container runtime that manages the lifecycle of a container.
/retitle "Using Minikube to Create a Cluster" unclear on meaning of containerd /language en Page to Update: For additional info, adding a hyperlink pointing to the corresponding official doc of the container runtime would be useful here.
I think the sentence is referring to the container tools and containerd manage the lifecycle of container on VMs.
Yeah, I get that. For someone new not familiar that this is a tool, might be confused. I originally thought it ws a typo and later realized it was referring to a dameon process. Not sure if there could be a link to docs of containerd so the reader won't get confused.
yes i also think adding link to docs of containerd would be useful for the reader to get clear understanding.
/assign
/kind documentation /triage accepted Improvements are welcome!
We could add a reference to our glossary entry:
/language en /priority backlog /help
This request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /language en /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
It is not the only problem on that page, the description of minikube is not very accurate (anymore) either... But it will soon need to change anyway, when the online tutorials disappear, so probably time for a rewrite ?
/assign


Question: ### kubelet [kubelet](/docs/admin/kubelet) is the primary node agent. It: * Watches for pods that have been assigned to its node (either by apiserver or via local configuration file) and: <del> * Mounts the pod's required volumes * Downloads the pod's secrets * Run the pod's containers via docker (or, experimentally, rkt). * Periodically executes any requested container liveness probes. * Reports the status of the pod back to the rest of the system, by creating a "mirror pod" if necessary. </del> <ins> * Mounts the pod's required volumes * Downloads the pod's secrets * Run the pod's containers via docker (or, experimentally, rkt). * Periodically executes any requested container liveness probes. * Reports the status of the pod back to the rest of the system, by creating a "mirror pod" if necessary. </ins> * Reports the status of the node back to the rest of the system. ### kube-proxy

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 used but it has already been deprecated and this is v1 section. ! Proposed Solution: It should be replaced with . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--


Question: For example: - a localization branch sourced from `main` must be merged into `main`. <del> - a localization branch sourced from `release-{{ skew "prevMinorVersion" }}` must be merged into `release-{{ skew "prevMinorVersion" }}`. </del> <ins> - a localization branch sourced from `release-{{% skew "prevMinorVersion" %}}` must be merged into `release-{{% skew "prevMinorVersion" %}}`. </ins> {{< note >}} If your localization branch was created from `main` branch but it is not merged into `main` before new release branch `{{< release-branch >}}` created, merge it into both `main` and new release branch `{{< release-branch >}}`. To merge your localization branch into new release branch `{{< release-branch >}}`, you need to switch upstream branch of your localization branch to `{{< release-branch >}}`.

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 skew used in the examples in the branching strategy section of the is incorrect and this leads to being rendered instead of something like Proposed Solution: Changing the shortcode to use and instead of and should fix this. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--Please let us know if any help is needed! /good-first-issue /help
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: The skew used in the examples in the branching strategy section of the is incorrect and this leads to being rendered instead of something like <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Please let us know if any help is needed! /help </details
/assign
/triage accepted
Hi is this what you are asking to do in this pr --! sorry, actually I am new to k8s so not much familiar with its related terminologies!
Your PR is the right fix :) You don't see the change in markdown because this is something hugo does. If you visit the deployed preivew on the PR you'll see your change in action.


Question: ## Setup <del> Ensure the RuntimeClass feature gate is enabled (it is by default). See [Feature Gates](/docs/reference/command-line-tools-reference/feature-gates/) for an explanation of enabling feature gates. The `RuntimeClass` feature gate must be enabled on API server _and_ kubelets. 1. Configure the CRI implementation on nodes (runtime dependent). 2. Create the corresponding RuntimeClass resources. </del> <ins> 1. Configure the CRI implementation on nodes (runtime dependent) 2. Create the corresponding RuntimeClass resources </ins> ### 1. Configure the CRI implementation on nodes

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: <!-- 1.  Generate the server certificate using the ca.key, ca.crt and server.csr: --> <del> 1.  基于 ca.key、ca.key 和 server.csr 等三个文件生成服务端证书： </del> <ins> 1.  基于 ca.key、ca.crt 和 server.csr 等三个文件生成服务端证书： </ins> openssl x509 -req -in server.csr -CA ca.crt -CAkey ca.key  -CAcreateserial -out server.crt -days 10000

There is a translation error here. " " should be changed to " ".
/kind bug /language zh /triage accepted /assign


Question: 1. Create a cluster with no Pod Security Standards applied: ```shell <del> kind create cluster --name psa-wo-cluster-pss --image kindest/node:v1.23.0 </del> <ins> kind create cluster --name psa-wo-cluster-pss --image kindest/node:v1.24.0 </ins> ``` The output is similar to this: ``` Creating cluster "psa-wo-cluster-pss" ... <del> ✓ Ensuring node image (kindest/node:v1.23.0) 🖼 </del> <ins> ✓ Ensuring node image (kindest/node:v1.24.0) 🖼 </ins> ✓ Preparing nodes 📦 ✓ Writing configuration 📜 ✓ Starting control-plane 🕹

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: Apply Pod Security Standards at the Cluster Level documents Pod Security admission defaults, but for Kubernetes v1.23 rather than any more recent release. Proposed Solution: Either: Edit to automatically render with the version of Kubernetes being documented Update for Kubernetes v1.24 Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /priority backlog /lifecycle frozen /triage accepted
What would need to change here? The Kubernetes minor version in the commands or also the version in the intro paragraph? (wouldn't that remain 1.23 since that's when the feature went beta?)
The tutorial shows you how to deploy a v1.23.x cluster; it should be v1.24. Maybe if we don't specify any version explicitly, that's good enough (I haven't checked, and I'm not very familiar with ). Making that version always match the latest release is left as an exercise for the reaser.
Hi, I have a question if we automatically render the Kubernetes version being documented for the page, would it be okay to mention something along the lines of : ? Thanks.
You can use this shortcode to show the version: See for an example.
Great, now I can try to work on this issue on the lines of the example. Thanks. /assign


Question: /docs/setup/minikube/     /docs/tasks/tools/ 302 /docs/setup/learning-environment/     /docs/tasks/tools/  302! <ins> /zh/docs/setup/learning-environment/     /zh/docs/tasks/tools/  302! </ins> /docs/setup/learning-environment/kind/  /docs/tasks/tools/  302 /docs/setup/learning-environment/minikube/  /docs/tasks/tools/ 302 /docs/setup/cri/     /docs/setup/production-environment/container-runtimes/   301

No content in this page. !
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 /kind bug BTW the fix for this is to copy the redirect that's configured for the English version of the page.
/assign


Question: The `hosts` file content would look like this: ```shell <del> kubectl exec hostaliases-pod -- cat /etc/hosts </del> <ins> kubectl logs hostaliases-pod </ins> ``` ```none

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: When the status of the pod is Completed, the command below does not work: kubectl exec hostaliases-pod -- cat /etc/hosts With the error : error: cannot exec into a container in a completed pod; current phase is Succeeded Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--v1.18.3 <!--Additional Information:--
i am not certain about this but we can't exec into a pod which is completed.There is a regarding this feature to be implemented .But cant find any updates there.
Fixed. /close
Closing this issue. <detailsIn response to : Fixed. /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: * 클라이언트는 `node2:nodePort`로 패킷을 보낸다. * `node2`는 소스 IP 주소(SNAT)를 패킷 상에서 자신의 IP 주소로 교체한다. <del> * `noee2`는 대상 IP를 패킷 상에서 파드의 IP로 교체한다. </del> <ins> * `node2`는 대상 IP를 패킷 상에서 파드의 IP로 교체한다. </ins> * 패킷은 node 1로 라우팅 된 다음 엔드포인트로 라우팅 된다. * 파드의 응답은 node2로 다시 라우팅된다. * 파드의 응답은 클라이언트로 다시 전송된다.

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: Mismatch between descriptive node names ! Proposed Solution: Change node name from 'noee2' to 'node2' Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language ko /assign


Question: ### Upgrade the kubelet configuration <del> 1.  Call the following command: </del> <ins> -  Call the following command: </ins> ```shell sudo kubeadm upgrade node

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--indentation issue Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--18 <!--Additional Information:--fix the page indentation
/sig cluster-lifecycle docs hi, can you show which section you think is wrong or maybe provide a screenshot?
/sig cluster-lifecycle docs Attached screenshots
i don't see the attachments, possibly because you replied via email. try adding them using the GitHub web UI.
! ! ! !
Page alignment or indentation not proper looks.
ok, i can confirm this. hi, was this broken by this PR, or maybe something on the hugo side changed recently?
The Hugo upgrade was PR
/kind bug /priority important-longterm
I've tried to make a work around for this. It looks like tabs shortcodes with code snippets inside them don't play well with shortcodes (see issue ).
I will take a stab at cleaning this up assuming work isn't currently being done. We might have to adjust the page slightly until capture is removed. /assign
I can share some WIP in case it helps
thanks for taking a look and
oof, sorry I saw this after I opened the PR. That does help! I was scratching my head on some of these bugs. Let me know if you want me to modify my PR to incorporate some of your suggestions or vice versa. I was poking fun of the page on twitter and felt obligated to try to fix it :smile:
Busy at the moment I'm afraid. Feel free to snarf any bits that look useful.


Question: There are two paths to extending the API with [custom resources](/docs/concepts/api-extension/custom-resources/): <del> 1. [CustomResourceDefinition](/docs/tasks/extend-kubernetes/custom-resource-definitions/) </del> <ins> 1. [CustomResourceDefinition](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/) </ins> lets you declaratively define how the API server should provide your chosen resource API. 1. You can also [implement your own extension API server](/docs/tasks/extend-kubernetes/setup-extension-api-server/) and use the [aggregator](/docs/tasks/extend-kubernetes/configure-aggregation-layer/)

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: There is a broken link to "CustomResourceDefinition" in concepts/overview/kubernetes-api/ URL: The linked page receives a 404 error: Proposed Solution: The link should be updated to link to 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> apiVersion: v1 kind: Pod metadata: name: envfrom-secret spec: containers: - name: envars-test-container image: nginx envFrom: - secretRef: name: test-secret </ins>

Translate into Japanese. This page has not been translated. /language ja /assign
/triage accepted


Question: <del> --- reviewers: - bsalamat - k82cn - ahg-g title: Resource Bin Packing for Extended Resources content_type: concept weight: 50 --- <!-- overview --> {{< feature-state for_k8s_version="v1.16" state="alpha" >}} The kube-scheduler can be configured to enable bin packing of resources along with extended resources using `RequestedToCapacityRatioResourceAllocation` priority function. Priority functions can be used to fine-tune the kube-scheduler as per custom needs. <!-- body --> ## Enabling Bin Packing using RequestedToCapacityRatioResourceAllocation Before Kubernetes 1.15, Kube-scheduler used to allow scoring nodes based on the request to capacity ratio of primary resources like CPU and Memory. Kubernetes 1.16 added a new parameter to the priority function that allows the users to specify the resources along with weights for each resource to score nodes based on the request to capacity ratio. This allows users to bin pack extended resources by using appropriate parameters improves the utilization of scarce resources in large clusters. The behavior of the `RequestedToCapacityRatioResourceAllocation` priority function can be controlled by a configuration option called `requestedToCapacityRatioArguments`. This argument consists of two parameters `shape` and `resources`. Shape allows the user to tune the function as least requested or most requested based on `utilization` and `score` values. Resources consists of `name` which specifies the resource to be considered during scoring and `weight` specify the weight of each resource. Below is an example configuration that sets `requestedToCapacityRatioArguments` to bin packing behavior for extended resources `intel.com/foo` and `intel.com/bar` ```json { "kind" : "Policy", "apiVersion" : "v1", ... "priorities" : [ ... { "name": "RequestedToCapacityRatioPriority", "weight": 2, "argument": { "requestedToCapacityRatioArguments": { "shape": [ {"utilization": 0, "score": 0}, {"utilization": 100, "score": 10} ], "resources": [ {"name": "intel.com/foo", "weight": 3}, {"name": "intel.com/bar", "weight": 5} ] } } } ], } ``` **This feature is disabled by default** ### Tuning RequestedToCapacityRatioResourceAllocation Priority Function `shape` is used to specify the behavior of the `RequestedToCapacityRatioPriority` function. ```yaml {"utilization": 0, "score": 0}, {"utilization": 100, "score": 10} ``` The above arguments give the node a score of 0 if utilization is 0% and 10 for utilization 100%, thus enabling bin packing behavior. To enable least requested the score value must be reversed as follows. ```yaml {"utilization": 0, "score": 100}, {"utilization": 100, "score": 0} ``` `resources` is an optional parameter which by defaults is set to: ``` yaml "resources": [ {"name": "CPU", "weight": 1}, {"name": "Memory", "weight": 1} ] ``` It can be used to add extended resources as follows: ```yaml "resources": [ {"name": "intel.com/foo", "weight": 5}, {"name": "CPU", "weight": 3}, {"name": "Memory", "weight": 1} ] ``` The weight parameter is optional and is set to 1 if not specified. Also, the weight cannot be set to a negative value. ### How the RequestedToCapacityRatioResourceAllocation Priority Function Scores Nodes This section is intended for those who want to understand the internal details of this feature. Below is an example of how the node score is calculated for a given set of values. ``` Requested Resources intel.com/foo : 2 Memory: 256MB CPU: 2 Resource Weights intel.com/foo : 5 Memory: 1 CPU: 3 FunctionShapePoint {{0, 0}, {100, 10}} Node 1 Spec Available: intel.com/foo : 4 Memory : 1 GB CPU: 8 Used: intel.com/foo: 1 Memory: 256MB CPU: 1 Node Score: intel.com/foo  = resourceScoringFunction((2+1),4) = (100 - ((4-3)*100/4) = (100 - 25) = 75                       # requested + used = 75% * available = rawScoringFunction(75) = 7                        # floor(75/10) Memory         = resourceScoringFunction((256+256),1024) = (100 -((1024-512)*100/1024)) = 50                       # requested + used = 50% * available = rawScoringFunction(50) = 5                        # floor(50/10) CPU            = resourceScoringFunction((2+1),8) = (100 -((8-3)*100/8)) = 37.5                     # requested + used = 37.5% * available = rawScoringFunction(37.5) = 3                        # floor(37.5/10) NodeScore   =  (7 * 5) + (5 * 1) + (3 * 3) / (5 + 1 + 3) =  5 Node 2 Spec Available: intel.com/foo: 8 Memory: 1GB CPU: 8 Used: intel.com/foo: 2 Memory: 512MB CPU: 6 Node Score: intel.com/foo  = resourceScoringFunction((2+2),8) =  (100 - ((8-4)*100/8) =  (100 - 50) =  50 =  rawScoringFunction(50) = 5 Memory         = resourceScoringFunction((256+512),1024) = (100 -((1024-768)*100/1024)) = 75 = rawScoringFunction(75) = 7 CPU            = resourceScoringFunction((2+6),8) = (100 -((8-8)*100/8)) = 100 = rawScoringFunction(100) = 10 NodeScore   =  (5 * 5) + (7 * 1) + (10 * 3) / (5 + 1 + 3) =  7 ``` </del>

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 Migrate the content from into somewhere inside Why is this needed is not about configuration in the way that ConfigMap and Secret are; instead, it's much more about scheduling. Comments /language en /kind cleanup Initially, a straightforward cut-and-paste would be fine, so I'll mark this as: /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 Feature Request <!-- See for guidance on writing an actionable issue description. --Migrate the content from into somewhere inside is not about configuration in the way that ConfigMap and Secret are; instead, it's much more about scheduling. /language en /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
Also see
/assign
BTW, this change also means adding a from to the new URL.


Question: `diff`        | `kubectl diff -f FILENAME [flags]`| ファイルまたは標準出力と、現在の設定との差分を表示します。 `drain`    | `kubectl drain NODE [options]` | メンテナンスの準備のためにNodeをdrainします。 `edit`        | kubectl edit (-f FILENAME | TYPE NAME | TYPE/NAME) [flags] | デファルトのエディタを使い、サーバー上の1つ以上のリソースリソースの定義を編集し、更新します。  `events`      | `kubectl events` | イベントを一覧表示します。  `exec`        | `kubectl exec POD [-c CONTAINER] [-i] [-t] [flags] [-- COMMAND [args...]]` | Pod内のコンテナに対して、コマンドを実行します。 `explain`    | `kubectl explain  [--recursive=false] [flags]` | 様々なリソースのドキュメントを取得します。例えば、Pod、Node、Serviceなどです。 `expose`        | kubectl expose (-f FILENAME | TYPE NAME | TYPE/NAME) [--port=port] [--protocol=TCP|UDP] [--target-port=number-or-name] [--name=name] [--external-ip=external-ip-of-service] [--type=type] [flags] | ReplicationController、Service、Podを、新しいKubernetesサービスとして公開します。

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


Question: ### Podオーバーヘッド <del> {{< feature-state for_k8s_version="v1.18" state="beta" >}} </del> <ins> {{< feature-state for_k8s_version="v1.24" state="stable" >}} </ins> Podが稼働する時に関連する _オーバーヘッド_ リソースを指定できます。オーバーヘッドを宣言すると、クラスター(スケジューラーを含む)がPodとリソースに関する決定を行うときにオーバーヘッドを考慮することができます。 <del> Podオーバーヘッドを使うためには、PodOverhead[フィーチャーゲート](/ja/docs/reference/command-line-tools-reference/feature-gates/)を有効にしなければなりません。(デフォルトではonです) </del> PodのオーバーヘッドはRuntimeClass内の`overhead`フィールドによって定義されます。 このフィールドを使用することで、RuntimeClassを使用して稼働するPodのオーバーヘッドを指定することができ、Kubernetes内部で使用されるオーバーヘッドを確保することができます。

This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/containers/runtime- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/containers/runtime- is outdated. Comments /language ja /assign
/triage accepted


Question: title: "Scheduling, Preemption and Eviction" weight: 95 content_type: concept <del> description: > In Kubernetes, scheduling refers to making sure that Pods are matched to Nodes so that the kubelet can run them. Preemption is the process of terminating Pods with lower Priority so that Pods with higher Priority can schedule on Nodes. Eviction is the process of proactively terminating one or more Pods on resource-starved Nodes. </del> no_list: true ---

This is a Bug Report Problem: The description and its proceeding text on the scheduling index page are almost duplicated. Proposed Solution: The following text on the index page needs to be removed: Page to Update: /language en
/assign
I have a specific fix in mind: suppress the display of the page description at the start of the page. That way, we retain the tooltips that we want, and we avoid the duplication.
/language en /priority backlog /triage accepted


Question: <!--overview--> <!-- <del> This page shows you how to specify the type of [cascading deletion](/docs/concepts/workloads/controllers/garbage-collection/#cascading-deletion) </del> <ins> This page shows you how to specify the type of [cascading deletion](/docs/concepts/architecture/garbage-collection/#cascading-deletion) </ins> to use in your cluster during {{<glossary_tooltip text="garbage collection" term_id="garbage-collection">}}. --> 本页面向你展示如何设置在你的集群执行{{<glossary_tooltip text="垃圾收集" term_id="garbage-collection">}} <del> 时要使用的[级联删除](/zh/docs/concepts/workloads/controllers/garbage-collection/#cascading-deletion) </del> <ins> 时要使用的[级联删除](/zh/docs/concepts/architecture/garbage-collection/#cascading-deletion) </ins> 类型。 ## {{% heading "prerequisites" %}}

There is a bug: ,%E4%BA%86%E8%A7%A3%E5%9E%83%E5%9C%BE%E6%94%B6%E9%9B%86.,-%E5%8F%8D%E9%A6%88 This hyperlink is 404, it should be ""
/assign
/triage accepted
The issue was solved by PR . If there is any problem, please give feedback again. /close
Closing this issue. <detailsIn response to : The issue was solved by PR . If there is any problem, please give feedback again. /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: <!-- ### cloud-controller-manager <del> {{< glossary_definition term_id="cloud-controller-manager" length="short" >}} </del> The cloud-controller-manager only runs controllers that are specific to your cloud provider. If you are running Kubernetes on your own premises, or in a learning environment inside your own PC, the cluster does not have a cloud controller manager.

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: Original text hast been kept along with translated text Proposed Solution: Delete original English text Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--<img width="863" alt="" src="https://user-"
Looks like the is still working even when being commented out. I have encountered this a hundred times when tidying up the Chinese localization, and this is one of the reasons I don't like this shortcode.
/assign


Question: <!-- overview --> This page shows how to enable and configure encryption of secret data at rest. ## {{% heading "prerequisites" %}} * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} * etcd v3.0 or later is required <!-- steps --> ## Configuration and determining whether encryption at rest is already enabled The `kube-apiserver` process accepts an argument `--encryption-provider-config` <del> that controls how API data is encrypted in etcd. An example configuration is provided below. </del> <ins> that controls how API data is encrypted in etcd. The configuration is provided as an API named [`EncryptionConfiguration`](/docs/reference/config-api/apiserver-encryption.v1/). An example configuration is provided below. </ins> {{< caution >}} <del> **IMPORTANT:** For multi-master configurations (with two or more control plane nodes) the encryption configuration file must be the same! Otherwise, the kube-apiserver can't decrypt data stored inside the key-value store. </del> <ins> **IMPORTANT:** For high-availability configurations (with two or more control plane nodes), the encryption configuration file must be the same! Otherwise, the `kube-apiserver` component cannot decrypt data stored in the etcd. </ins> {{< /caution >}} ## Understanding the encryption at rest configuration.

This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Within add a new generated page that documents the format for an encryption configuration. Update to hyperlink to that new reference Why is this needed Within , there is a configuration format for the API server, EncryptionConfiguration. At the moment that format is not documented in Readers may want to look up what that format covers. Comments /sig api-machinery /sig auth /kind feature /language en
/triage accepted
/assign This file is already generated in the generator. All we need to do is to copy it to the website repo.


Question: ```shell # replace x with the patch version you picked for this upgrade <del> sudo kubeadm upgrade apply v{{< skew latestVersion >}}.x </del> <ins> sudo kubeadm upgrade apply v{{< skew currentVersion >}}.x </ins> ``` Once the command finishes you should see: ``` <del> [upgrade/successful] SUCCESS! Your cluster was upgraded to "v{{< skew latestVersion >}}.x". Enjoy! </del> <ins> [upgrade/successful] SUCCESS! Your cluster was upgraded to "v{{< skew currentVersion >}}.x". Enjoy! </ins> [upgrade/kubelet] Now that your control plane is upgraded, please proceed with upgrading your kubelets if you haven't already done so. ```

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 https://v1- explains how to upgrade a Kubernetes cluster created with kubeadm from version 1.20.x to version 1.21.x, and from version 1.21.x to 1.21.y. (Should be from version 1.19.x to version 1.20.x, and from version 1.20.x to 1.20.y.) Proposed Solution: In Replace =- =- ... Page to Update: https://v1- <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/assign
I think we should fix the shortcode to use the documented version, rather than the most recent release. /sig cluster-lifecycle /language en
the intent behind seems to be misleading if is fed at build time pointing at the latest current k8s version. while extending the latestVersion shortcodes i expected to be static and hardcoded per k/website release branch. i can send PRs for this but i'd need to understand more about the "documented" version that you mentioned. i.e. making latestVersion fixed to 1.20 in the 1.20 release branch seems reasonable to me.
^ for additional opinions.
Despite a misleading name, is supposed to use not . AIUI.
i can see is being used in a few places: should all of these be modified to use or only the shortcodes in ? and for which branches - and ?
is useful, it does represent the most recent release.
ok, i can PR the change for 1.20, and master since this is only a problem for the kubeadm upgrade docs. is also used here, but the versions there are just examples. https://v1-
here are the PRs:
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
/remove-lifecycle stale
/triage accepted
/priority-important longterm
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority-important longterm Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/priority important-longterm


Question: RELEASE="$(curl -sSL https://dl.k8s.io/release/stable.txt)" ARCH="amd64" cd $DOWNLOAD_DIR <del> sudo curl -L --remote-name-all https://storage.googleapis.com/kubernetes-release/release/${RELEASE}/bin/linux/${ARCH}/{kubeadm,kubelet,kubectl} sudo chmod +x {kubeadm,kubelet,kubectl} </del> <ins> sudo curl -L --remote-name-all https://dl.k8s.io/release/${RELEASE}/bin/linux/${ARCH}/{kubeadm,kubelet} sudo chmod +x {kubeadm,kubelet} </ins> RELEASE_VERSION="v0.4.0" curl -sSL "https://raw.githubusercontent.com/kubernetes/release/${RELEASE_VERSION}/cmd/kubepkg/templates/latest/deb/kubelet/lib/systemd/system/kubelet.service" | sed "s:/usr/bin:${DOWNLOAD_DIR}:g" | sudo tee /etc/systemd/system/kubelet.service

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 “without a package manager” section of suggests that people download components from within However, recommends downloading from To me, the URLs seem more official and also make it easier for us to bolt in a CDN or whatever if we want to serve content from not-Google. Proposed Solution: Revise the “without a package manager” tab in to recommend downloading and from If possible, avoid fetching the latest release version via HTTP. This website repo already has the release information available so we can cut out a step (and make the docs more accurate when people are reading docs for previous Kubernetes versions). For the download, refer readers to Continue to recommend downloading from GitHub Continue to recommend downloading CNI tooling from GitHub Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: The same page also recommends downloading packages (RPM, ) from Google. This issue doesn't cover the packaged downloads, just the direct downloads of the files. This issue also doesn't cover a change to how people download and install that tool. This issue also doesn't cover a change to how people download CNI tooling. /sig release /sig cluster-lifecycle /language en
If we remove the RELEASE version fetch step, we'd need a step to choose a Kubernetes version right? So something like "Choose the Kubernetes version you want to install from the Releases page." And then another line in the actual command that downloads kubeadm and the rest that says "Replace $RELEASE with the Kubernetes version that you selected". Am I off track here? also /triage accepted
You can already choose which Kubernetes version you're reading the docs for, so it ought to be enough to signpost readers to the choice. To help readers, we can also link from to the same doc in each of the supported docs versions - I think that'd need a shortcode, but it could be done.
For example, https://v1- could explain how to install v1.21.x (whatever is latest for v1.21).
/priority important-longterm
/assign
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]:


Question: <ins> --- title: Gateway API id: gateway-api date: 2023-10-19 full_link: /docs/concepts/services-networking/gateway/ short_description: > An API for modeling service networking in Kubernetes. aka: tags: - networking - architecture - extension --- A family of API kinds for modeling service networking in Kubernetes. <!--more--> Gateway API provides a family of extensible, role-oriented, protocol-aware API kinds for modeling service networking in Kubernetes. </ins>

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


Question: <p>{{ T "announcement_message" | markdownify }}</p> </div> <del> </main> </del> <ins> </aside> </ins> </section> {{ end }}  No newline at end of file

The announcement banner text (merged in ) is being used as the Google search snippet for docs pages. This may not have been your intention. !
SIG Docs doesn't have a good way to improve Google's indexing algorithm. The text is in an HTML element which should mark it as an aside: content only indirectly related to the main content. I'd characterize this as a Google bug. There are a lot of Google people in the Kubernetes ecosystem but probably not from the web search side. Do you agree with that characterization? /triage awaiting-more-evidence
The label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : SIG Docs doesn't have a good way to improve Google's indexing algorithm. The text is in an HTML element which should mark it as an aside: content only indirectly related to the main content. /triage awaiting-more-evidence Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/priority awaiting-more-evidence
I can't find anything suggesting Google has ever ignored elements, and I can find a comment from someone at Google saying they explicitly ignore them ( via ). The supported way to mark something not to go in a snippet is the attribute: , . I can raise a feature request with the search team to ask them to treat like but from a Kubernetes users perspective, changing the site will get to a better outcome quicker.
It sounds useful to add to the announcements.
I would adjust to "fix now"
Yikes, sorry guys! I would also mark as fix now
/priority fix-now
The label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : /priority fix-now Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/remove-priority awaiting-more-evidence /priority critical-urgent

This is a Feature Request The HTML partials, and frontpage-, contain a element which duplicates the element found in the body of the page. This became an issue as the docsy theme updates page anchors in the script . This script depends upon the element and failed to find the H1 - H6 level headings on the page to udpate. What would you like to be Investigate how to include the announcement banner on the docs pages (front page, docs, blog, and so on) without the element. Investigate changes to the corresponding stylesheet. Why is this needed Clean up or adjust the preexisting, related code as well as the current templates and stylesheet. Provide a flexible way to add and remove content such as announcement or banners on the pages. Comments For additional information, see PR .
/assign
/kind cleanup /priority important-soon
/reopen There might be more to do here.
Reopened this issue. <detailsIn response to : /reopen There might be more to do here. 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 don't think there's any more work that needs doing here! you can close this off :)
Good. The only thing noted is some different styling per main section (docs vs case studies). /close
Closing this issue. <detailsIn response to : Good. The only thing noted is some different styling per main section (docs vs case studies). /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: EOF ``` <del> 1. Configure your kubelet on the node to use this directory by running it with </del> <ins> 1. Configure the kubelet on that node to set a `staticPodPath` value in the [kubelet configuration file](/docs/reference/config-api/kubelet-config.v1beta1/). See [Set Kubelet Parameters Via A Configuration File](/docs/tasks/administer-cluster/kubelet-config-file/) for more information. An alternative and deprecated method is to configure the kubelet on that node to look for static Pod manifests locally, using a command line argument. To use the deprecated approach, start the kubelet with the </ins> `--pod-manifest-path=/etc/kubernetes/manifests/` argument. <del> On Fedora, edit `/etc/kubernetes/kubelet` to include this line: ``` KUBELET_ARGS="--cluster-dns=10.254.0.10 --cluster-domain=kube.local --pod-manifest-path=/etc/kubernetes/manifests/" ``` or add the `staticPodPath: <the directory>` field in the [kubelet configuration file](/docs/reference/config-api/kubelet-config.v1beta1/). </del> 1. Restart the kubelet. On Fedora, you would run: ```shell

On: But I get: Sorry, I can't provide a PR at this moment.
/kind bug /sig node /language en /priority important-longterm Static pods are on the syllabus for the CKA qualification, so we should especially avoid recommending a deprecated approach.
Maybe it makes sense to change to docs from to , too, since that what kubeadm creates.
This has been previously discussed within the SIG; migrating off of command line flags is a backlog item. Other components have a similar problem. For the foreseeable future, the command line flags will definitely work and continue to be supported. We are ensuring any new command line flags are as config options and attempting to migrate over any flags that are not currently supported in the config API. So, while technically deprecated, I think this is still okay. It would be great to have docs for both.
/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 think this is still worth tracking, but isn't a short term priority. /reopen /lifecycle frozen
Reopened this issue. <detailsIn response to : I think this is still worth tracking, but isn't a short term priority. /lifecycle frozen 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
/help
This request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/retitle Create static Pods: has been deprecated
/assign I will try to work on a PR for this issue.


Question: /docs/concepts/configuration/manage-compute-resources-container/ /docs/concepts/configuration/manage-resources-containers/ 301 /docs/concepts/configuration/resource-bin-packing/      /docs/concepts/scheduling-eviction/resource-bin-packing/ 301 /docs/concepts/configuration/scheduler-perf-tuning/      /docs/concepts/scheduling-eviction/scheduler-perf-tuning/    301 <ins> /id/docs/concepts/configuration/scheduler-perf-tuning/      /id/docs/concepts/scheduling-eviction/scheduler-perf-tuning/    301 </ins> /docs/concepts/configuration/scheduling-framework/     /docs/concepts/scheduling-eviction/scheduling-framework/    301 <ins> /id/docs/concepts/configuration/scheduling-framework/     /id/docs/concepts/scheduling-eviction/scheduling-framework/    301 </ins> /docs/concepts/configuration/taint-and-toleration/     /docs/concepts/scheduling-eviction/taint-and-toleration/ 301 /id/docs/concepts/configuration/taint-and-toleration/     /id/docs/concepts/scheduling-eviction/taint-and-toleration/ 301 /docs/concepts/extend-kubernetes/extend-cluster/      /docs/concepts/extend-kubernetes/ 301

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: resources: * [Installation](https://github.com/sigstore/cosign#installation) <del> * [Configuration Options](https://github.com/sigstore/cosign/tree/main/config) </del> <ins> * [Configuration Options](https://github.com/sigstore/cosign/blob/main/USAGE.md#detailed-usage) </ins>

The and link in the section are broken.
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 don't know if the issue is open or not, but I would like to work in it.
Looks like installation of cosign has moved from to
/assign
What about Configuration link?
Hi Instead of Configuration we can add Detailed usage of cosign there -


Question: <ins> --- title: Replica id: replica date: 2023-06-11 full_link: short_description: > Replicas are copies of pods, ensuring availability, scalability, and fault tolerance by maintaining identical instances. aka: tags: - fundamental - workload --- A copy or duplicate of a {{< glossary_tooltip text="Pod" term_id="pod" >}} or a set of pods. Replicas ensure high availability, scalability, and fault tolerance by maintaining multiple identical instances of a pod. <!--more--> Replicas are commonly used in Kubernetes to achieve the desired application state and reliability. They enable workload scaling and distribution across multiple nodes in a cluster. By defining the number of replicas in a Deployment or ReplicaSet, Kubernetes ensures that the specified number of instances are running, automatically adjusting the count as needed. Replica management allows for efficient load balancing, rolling updates, and self-healing capabilities in a Kubernetes cluster. </ins>

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: ... ``` <del> contains a single `from` element allowing connections from Pods with the label `role=client` in namespaces with the label `user=alice`. But *this* policy: </del> <ins> This policy contains a single `from` element allowing connections from Pods with the label `role=client` in namespaces with the label `user=alice`. But the following policy is different: </ins> ```yaml ...

I spent one hour to do one sample exercice about network policy because of your wrong configuration !!! +++++++++++++++++++++ policyTypes: # should remove space in the 2nd & 3rd line Ingress Egress ++++++++++++++++++++++ egress: to: ipBlock: cidr: 10.0.0.0/24 ports: # "-" is missing before ports protocol: TCP port: 5978
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
/retitle Invalid manifest in Network Policies page Thanks for reporting the bug /kind bug /language en Please paste in the entire invalid manifest (surround it by <tt`</ttif you can) so we know which part of the page is wrong. We could guess, but it's easier if you're explicit about this
/triage accepted /assign


Question: 컨테이너는 CPU 1개를 요구하는 컨테이너의 절반만큼 CPU를 보장한다. `0.1` 이라는 표현은 "백 밀리cpu"로 읽을 수 있는 `100m` 표현과 동일하다. 어떤 사람들은 "백 밀리코어"라고 말하는데, 같은 것을 의미하는 것으로 이해된다. <del> `0.1` 과 같이 소수점이 있는 요청은 API에 의해 `100m` 로 변환되며, `1m` 도 허용되지 않게 정밀하다. 이러한 이유로, `100m` 형식이 선호될 수 있다. </del> <ins> `0.1` 과 같이 소수점이 있는 요청은 API에 의해 `100m` 으로 변환되며, `1m` 보다 더 정밀한 단위는 허용되지 않는다. 이러한 이유로, `100m` 과 같은 형식이 선호될 수 있다. </ins> CPU는 항상 절대 수량으로 요청되며, 상대적 수량은 아니다. 0.1은 단일 코어, 이중 코어 또는 48코어 시스템에서 동일한 양의 CPU이다.

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: ] ] Proposed Solution: Page to Update: - <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ko /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: A request with a decimal point, like , is converted to by the API, and precision finer than is not allowed. For this reason, the form might be preferred. API , . , . API , . , . - <!--Kubernetes Version:--/good-first-issue </details
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign


Question: * For IPv4 endpoints, the DNS system creates A records. * For IPv6 endpoints, the DNS system creates AAAA records. <ins> When you define a headless Service without a selector, the `port` must match the `targetPort`. </ins> ## Discovering services For clients running inside your cluster, Kubernetes supports two primary modes of

Need to mention that for headless services without selector, the Port need to be the same as the TargetPort.
hey, can i get some more context related to this? I would like to work on this issue
you can see some information about this here: do we really need port for a headless service? | | | | | | do we really need port for a headless service? It might be a question based on curiosity which couldn't find help on google.Consider this part of the yaml fo... | | | Headless service targetPort not resolving containerPort name · Issue · kubernetes/kubernetes | | | | | | Headless service targetPort not resolving containerPort name · Issue ... It seems that my headless service definition does not correctly resolve the containerPort name. I receive this e... | | | On Friday, March 10, 2023 at 10:17:59 PM MST, Khush Patibandha hey, can i get some more context related to this? I would like to work on this issue — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID:
/sig network /kind bug /triage accepted /retitle Service concept unclear on vs consistency for headless Services
Fixed on
See for the PR we should review here.


Question: <ins> FROM node:6.14.2 EXPOSE 8080 COPY server.js . CMD [ "node", "server.js" ] </ins>

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: is a missing page; however, is part of the for a localization. Proposed Solution: Localize “Hello Minikube” into Spanish Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language es /kind bug
/assign


Question: FOO_SERVICE_PORT=<サービスが実行されているポート> ``` <del> サービスは専用のIPアドレスを持ち、[DNSアドオン](http://releases.k8s.io/{{< param "fullversion" >}}/cluster/addons/dns/)が有効の場合、DNSを介してコンテナで利用可能です。 </del> <ins> サービスは専用のIPアドレスを持ち、[DNSアドオン](http://releases.k8s.io/v{{< skew currentPatchVersion >}}/cluster/addons/dns/)が有効の場合、DNSを介してコンテナで利用可能です。 </ins>

Problem: Based on , I have created this issue/task to help update the [ja] language documentation. Proposed Solution: Page to Update: In the branch, I found: Results for "fullversion" in "k8s-website/content/ja" /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/concepts/containers/container- 46: IPDNS /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/concepts/services-networking/connect-applications- 146: /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/concepts/services- 283: )Service /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/setup/learning- 220: {{< param "fullversion" }}: 223: minikube start --kubernetes-version {{< param "fullversion" }} /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/tasks/tools/install- 34: Linux{{< param "fullversion" }}: 37: curl -LO {{< param "fullversion" }}/bin/linux/amd64/kubectl 116: macOS{{< param "fullversion" }}: 119: curl -LO {{< param "fullversion" }}/bin/darwin/amd64/kubectl 181: {{< 181: "fullversion" }}){{< param "fullversion" }} 186: curl -LO {{< param "fullversion" }} /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/tasks/administer-cluster/kubeadm/adding-windows- 107: Kubernetes{{< param "fullversion" }} 111: releases/latest/download/kube- kubectl apply -f - 150: .PrepareNode.

ps1 -KubernetesVersion {{% param "fullversion" %}} /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/tasks/administer-cluster/kubeadm/upgrading-windows- 35: # {{% param "fullversion" %}} 36: -Lo C:k {{% param "fullversion" %}} 70: -Lo C:k {{% param "fullversion" %}} 86: {{< param "fullversion" }}: 89: releases/latest/download/kube- kubectl apply -f - /sig docs /sig localization /language ja cc:
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: All the other documents need to change into or appropriatly. Since several languages are involved, I'd like to share this issue to check all localizations complete the task. Proposed Solution: Page to Update: /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/concepts/services-networking/connect-applications- /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/concepts/services- /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/setup/learning- /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/tasks/tools/install- /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/tasks/administer-cluster/kubeadm/adding-windows- /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/tasks/administer-cluster/kubeadm/upgrading-windows- /sig localization /language ja cc: 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
cc:
/triage accepted /area localization /priority backlog


Question:
Once you have a running Kubernetes cluster, you can deploy your containerized applications on top of it. To do so, you create a Kubernetes Deployment configuration. The Deployment instructs Kubernetes how to create and update instances of your application. Once you've created a Deployment, the Kubernetes  master schedules mentioned application instances onto individual Nodes in the cluster.   master schedules the application instances included in that Deployment to run on individual Nodes in the cluster.

Once the application instances are created, a Kubernetes Deployment Controller continuously monitors those instances. If the Node hosting an instance goes down or is deleted, the Deployment controller replaces the instance with an instance on another Node in the cluster. This provides a self-healing mechanism to address machine failure or maintenance.

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: There's either a typo in the of Module 2 of the tutorial, or the sentence is very awkwardly worded. The sentence: Once you've created a Deployment, the Kubernetes master schedules mentioned application instances onto individual Nodes in the cluster. doesn't appear to make any sense. Is the Kubernetes master scheduling the "mentioned application instances"? What application instances were mentioned? What does "scheduling" in this context mean? Proposed Solution: If this sentence is written as intended, it could use clarification. However it seems like there might be one or more typos, where words have been accidentally substituted. Those substitutions should be corrected if that's the case. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
I think the sentence is true. It looks like there is room to clarify and improve the wording. explains scheduling in a Kubernetes context. <hr /Does this wording work better ?
I think that's an improvement and I believe I understand the sentence as intended now. I think my confusion largely stemmed from the word "mentioned." My understanding now is that "mentioned application instances" in this context means "the application instances mentioned in the Deployment you've created," right? So maybe: I think "scheduling" might be another point of confusion, just because it's only been mentioned in the tutorial once before: . It might not be necessary to give an expanded definition of scheduling here, but I do think the phrasing used in that previous mention of scheduling is more accessible: "schedules ... to run on the cluster's nodes" rather than "schedules ... onto individual Nodes". "Scheduling something" is a familiar phrase, but "scheduling something onto something" is a little less clear at first. So then maybe: ?
- would you also be interesting in proposing that fix as a pull request?
Done!


Question: ### Approve Certificate Request <del> Use kubeadmin to create a CSR and approve it. </del> <ins> Use kubectl to create a CSR and approve it. </ins> Get the list of CSRs ```

/language zh
/reopen This was incorrectly
Reopened this issue. <detailsIn response to : /reopen This was incorrectly 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: #### IP address ranges for Service virtual IP addresses {#service-ip-static-sub-range} <del> {{< feature-state for_k8s_version="v1.25" state="beta" >}} </del> <ins> {{< feature-state for_k8s_version="v1.26" state="stable" >}} </ins> Kubernetes divides the `ClusterIP` range into two bands, based on the size of the configured `service-cluster-ip-range` by using the following formula

This is a Bug Report Problem: The FEATURE STATE of the following features is mentioned wrongly(outdated) under the docs: : The corresponding feature gate is and mentioned Feature State is : The corresponding feature gate is and mentioned Feature State is Proposed Solution: According to the docs, for Feature State should be and for Feature State should be Page to Update:
/language en /sig docs /sig network
/assign
Fixed it here:
/retitle Feature gates and incorrectly marked as beta
/triage accepted


Question: ### Language specific Zoom meetings If the localization project needs a separate meeting time, contact a SIG Docs Co-Chair or Tech <del> Lead to create a new reoccurring Zoom meeting and calendar invite. This is only needed when the </del> <ins> Lead to create a new reoccurring Zoom meeting and calendar invite. This is only needed when </ins> the team is large enough to sustain and require a separate meeting. Per CNCF policy, the localization teams must upload their meetings to the SIG Docs YouTube

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. --This extra "the" should be removed for better readability. ! Why is this needed For the improvement of the docs this extra "the" should be removed. file link :-
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
: Please check the comments against PR . Thank you for suggesting this amendment, however, we'd request that when you suggest such trivial edits you check the entire document for any other mistakes that might need rectification.


Question:
Objectives

उद्देश्य

जानें कुबेरनेट्स क्लस्टर क्या है।

जानें मिनिक्यूब क्या है।

This is a Bug Report Objective should be replace by उद्देश्य in content/hi/docs/tutorials/kubernetes-basics/create-cluster/cluster- <!--Required Information--Problem: Objective is english word in hindi content Proposed Solution: Replace with उद्देश्य 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
/kind documentation
/assign


Question:
Kubernetesクラスター

  Kubernetesは、単一のユニットとして機能するように接続された、可用性の高いコンピュータのクラスターをまとめあげます。Kubernetesの抽象化により、コンテナ化されたアプリケーションを個々のマシンに特に結び付けることなくクラスターにデプロイできます。この新しいデプロイモデルを利用するには、アプリケーションを個々のホストから切り離す方法でアプリケーションをパッケージ化(つまり、コンテナ化)する必要があります。コンテナ化されたアプリケーションは、アプリケーションがホストに深く統合されたパッケージとして特定のマシンに直接インストールされていた従来のデプロイモデルよりも柔軟で、より迅速に利用可能です。Kubernetesはより効率的な方法で、クラスター全体のアプリケーションコンテナの配布とスケジューリングを自動化します。Kubernetesはオープンソースのプラットフォームであり、プロダクションレディです。   Kubernetesは、単一のユニットとして機能するように接続された、可用性の高いコンピューターのクラスターをまとめあげます。Kubernetesの抽象化により、コンテナ化されたアプリケーションを個々のマシンに特に結び付けることなくクラスターにデプロイできます。この新しいデプロイモデルを利用するには、アプリケーションを個々のホストから切り離す方法でアプリケーションをパッケージ化(つまり、コンテナ化)する必要があります。コンテナ化されたアプリケーションは、アプリケーションがホストに深く統合されたパッケージとして特定のマシンに直接インストールされていた従来のデプロイモデルよりも柔軟で、より迅速に利用可能です。Kubernetesはより効率的な方法で、クラスター全体のアプリケーションコンテナの配布とスケジューリングを自動化します。Kubernetesはオープンソースのプラットフォームであり、プロダクションレディです。

Kubernetesクラスターは以下の2種類のリソースで構成されています:

This is a Feature Request What would you like to be fix the notation variations of the term "computer" valid: invalid: | Why is this needed In Japanese documents, There are notation variations. The Japanese localization of k/website has rules, so we want to follow them. Comments FYI: Japanese Localization document: command /language ja /area localization /help /good-first-issue
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
PTAL before woking
PR
/remove-help


Question: ``` {{< tabs name="tab-cri-cri-o-installation" >}} <del> {{< tab name="Debian" >}} </del> <ins> {{% tab name="Debian" %}} </ins> ```shell # Debian 개발 배포본(Unstable/Sid)

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Broken layout for tabs on "Container runtimes" page as below. ! Proposed Solution: TBD Page to Update: /language ko <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/retitle Broken layout for tabs on "Container runtimes" page in Korean
This problem is due to incorrect tab code. We should fix this like the below: (Line 71, 125, 126, 180) to
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Hey folks, I'm happy to help you with this /assign


Question: ## Using the `cgroupfs` driver <del> As this guide explains using the `cgroupfs` driver with kubeadm is not recommended. To continue using `cgroupfs` and to prevent `kubeadm upgrade` from modifying the </del> <ins> To use `cgroupfs` and to prevent `kubeadm upgrade` from modifying the </ins> `KubeletConfiguration` cgroup driver on existing setups, you must be explicit about its value. This applies to a case where you do not wish future versions of kubeadm to apply the `systemd` driver by default.

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 following sentence is not complete: As this guide explains using the cgroupfs driver with kubeadm is not recommended. What would you like to be : More information needs to be after "explains", or rephrase it from scratch. 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
/language en
/language en /sig cluster-lifecycle
do you mean that the sentence: As this guide explains using the cgroupfs driver with kubeadm is not recommended. should link to one of the earlier paragraphs on the same page (same guide)? The page explains that the systemd driver is recommended for kubeadm based setups instead of the cgroupfs driver, because kubeadm manages the kubelet as a systemd service. if you have a particular change in mind, please send a PR for review.
technically, as per the overall page context, the sentence: As this guide explains using the cgroupfs driver with kubeadm is not recommended. can be deleted entirely... the section is providing an alternative after the main point has been made earlier - i.e. "cgroupfs driver = not recommended".


Question: section.k8s-birthday-override:has(div.k8s-birthday-override.revert-to-previous input:not(:checked)) + section { display: none; visibility: hidden; <ins> } /* Apply site-wide table styles for tables in alert callouts (note, caution, warning) */ .alert { &.alert-info, &.alert-caution, &.alert-danger { > table { @extend .table-striped; @extend .table-responsive; @extend .table; } } </ins> }  No newline at end of file

Problem: ! Proposed Solution: I have no idea because I have never used Hugo Page to Update:
/area web-development /triage accepted
Can I take care of it?
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
It is not clear what is the next step to take this issue to closure. I see tried a number of things in Is the issue that the table "borders" are not rendered correctly in the Note admonition? It seems Hugo is not able to render the borders of the table when it is inside a Note admonition block. In this case it should be reported as a bug to Hugo, right? In the meanwhile, I propose we remove the part of having support for a table inside a Note from the Propose to remove from the below section. !
I have raised a for support in the Hugo forums.
There is an answer on the Hugo forum stating that this is not a Hugo issue. The suggestion is to fix the CSS. Any pointers?


Question: # Tài liệu Kubernetes <del> [![Netlify Status](https://api.netlify.com/api/v1/badges/be93b718-a6df-402a-b4a4-855ba186c97d/deploy-status)](https://app.netlify.com/sites/kubernetes-io-main-staging/deploys) [![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest) </del> <ins> [![Trạng thái Netlify](https://api.netlify.com/api/v1/badges/be93b718-a6df-402a-b4a4-855ba186c97d/deploy-status)](https://app.netlify.com/sites/kubernetes-io-main-staging/deploys) [![Phiên bản GitHub](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest) </ins> <del> Chào mừng! Kho lưu trữ này chứa tất cả các tài nguyên cần thiết để xây dựng [trang web của Kubernetes và các tài liệu](https://kubernetes.io/). Chúng tôi rất vui vì bạn muốn đóng góp. </del> <ins> Kho lưu trữ này chứa các tài sản cần thiết để xây dựng [trang web và tài liệu Kubernetes](https://kubernetes.io/). Chúng tôi rất vui mừng khi bạn muốn đóng góp! </ins> <del> ## Đóng góp cho tài liệu </del> <ins> - [Đóng góp vào tài liệu](#contributing-to-the-docs) - [READMEs địa phương](#localization-readmes) </ins> <del> Bạn có thể click vào nút **Fork** ở góc trên bên phải màn hình để tạo bản sao của kho lưu trữ này trong tài khoản GitHub của bạn. Bản sao này được gọi là một bản *fork*. Thực hiện bất kì thay đổi nào mà bạn muốn trong bản fork của bạn và khi bạn sẵn sang gửi những thay đổi đó cho chúng tôi, hãy đến bản fork của bạn và tạo một Pull Request mới để cho chúng tôi biết về nó. </del> <ins> ## Sử dụng kho lưu trữ này </ins> <del> Một khi Pull Request của bạn được tạo, reviewer sẽ chịu trách nhiệm cung cấp các phản hồi rõ ràng, có thể thực hiện được. Là chủ sở hữu của pull request, **bạn có trách nhiệm sửa đổi Pull Request của mình để giải quyết các phản hồi bởi reviewer.**  Ngoài ra, lưu ý rằng bạn có thể có nhiều hơn một reviewer cung cấp cho bạn các phản hồi hoặc bạn có thể nhận được phản hồi từ reviewer khác với reviewer ban đầu được chỉ định. Hơn nữa, trong một số trường hợp, một trong những reviewer của bạn có thể yêu cầu đánh giá kỹ thuật từ [Kubernetes tech reviewer](https://github.com/kubernetes/website/wiki/Tech-reviewers) khi cần. Các reviewers sẽ cố gắng hết sức để cung cấp phản hồi một cách kịp thời nhưng thời gian phản hồi có thể thay đổi tùy theo hoàn cảnh. </del> <ins> Bạn có thể chạy trang web này ở chế độ local bằng cách sử dụng [Hugo (Phiên bản mở rộng)](https://gohugo.io/), hoặc bạn có thể chạy nó trong một container runtime. Chúng tôi mạnh mẽ khuyến nghị sử dụng container runtime, vì nó mang lại tính nhất quán trong triển khai với trang web thực tế. </ins> <del> Để biết thêm thông tin về việc đóng góp cho tài liệu Kubernetes, hãy xem: </del> <ins> ## Yêu cầu tiên quyết </ins> <del> * [Bắt đầu đóng góp](https://kubernetes.io/docs/contribute/start/) * [Các giai đoạn thay đổi tài liệu](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally) * [Sử dụng các trang templates](https://kubernetes.io/docs/contribute/style/page-content-types/) * [Hướng dẫn biểu mẫu tài liệu](http://kubernetes.io/docs/contribute/style/style-guide/) * [Địa phương hóa tài liệu Kubernetes](https://kubernetes.io/docs/contribute/localization/) </del> <ins> Để sử dụng kho lưu trữ này, bạn cần cài đặt các phần mềm sau trên máy tính của bạn: - [npm](https://www.npmjs.com/) - [Go](https://go.dev/) - [Hugo (Phiên bản mở rộng)](https://gohugo.io/) - Một container runtime, như [Docker](https://www.docker.com/). </ins> <del> ## Chạy website cục bộ dùng Docker </del> <ins> Trước khi bắt đầu, hãy cài đặt các phụ thuộc. Sao chép kho lưu trữ và di chuyển đến thư mục: </ins> <del> Cách được đề xuất để chạy trang web Kubernetes cục bộ là dùng [Docker](https://docker.com) image chứa trình tạo web tĩnh [Hugo](https://gohugo.io). </del> <ins> ```bash git clone https://github.com/kubernetes/website.git cd website ``` </ins> <del> > Nếu bạn làm việc trên môi trường Windows, bạn sẽ cần thêm môt vài công cụ mà bạn có thể cài đặt với [Chocolatey](https://chocolatey.org). `choco install make` </del> <ins> Trang web Kubernetes sử dụng [chủ đề Docsy Hugo](https://github.com/google/docsy#readme). Ngay cả khi bạn dự định chạy trang web trong một vùng chứa, chúng tôi thực sự khuyên bạn nên kéo mô-đun con và các phần phụ thuộc phát triển khác bằng cách chạy như sau: </ins> <del> > Nếu bạn không muốn dùng Docker để chạy trang web cục bộ, hãy xem [Chạy website cục bộ dùng Hugo](#chạy-website-cục-bộ-dùng-hugo) dưới đây. </del> <ins> ### Windows ```powershell # fetch submodule dependencies git submodule update --init --recursive --depth 1 ``` </ins> <del> Nếu bạn có Docker đang [up và running](https://www.docker.com/get-started), build `kubernetes-hugo` Docker image cục bộ: </del> <ins> ### Linux / other Unix </ins> ```bash <del> make container-image </del> <ins> # fetch submodule dependencies make module-init </ins> ``` <del> Khi image đã được built, bạn có thể chạy website cục bộ: </del> <ins> ## Chạy trang web bằng container Để xây dựng trang web trong một container, chạy lệnh sau: </ins> ```bash <ins> # Bạn có thể đặt biến $CONTAINER_ENGINE thành tên của bất kỳ công cụ container giống Docker nào </ins> make container-serve ``` <del> Mở trình duyệt và đến địa chỉ http://localhost:1313 để xem website. Khi bạn thay đổi các file nguồn, Hugo cập nhật website và buộc làm mới trình duyệt. </del> <ins> Nếu bạn thấy lỗi, điều đó có thể có nghĩa là container Hugo không có đủ tài nguyên điện toán. Để giải quyết nó, hãy tăng số lượng sử dụng CPU và bộ nhớ được phép cho Docker trên máy của bạn ([macOS] (<https://docs.docker.com/desktop/setings/mac/>) và [windows] (https: // tài liệu .Docker.com/Desktop/Cài đặt/Windows/)). Mở trình duyệt của bạn để <http://localhost:1313> để xem trang web. Khi bạn thay đổi các tệp nguồn, Hugo cập nhật trang web và buộc phải làm mới trình duyệt. ## Chạy trang web cục bộ bằng cách sử dụng Hugo Đảm bảo cài đặt phiên bản mở rộng Hugo được chỉ định bởi biến môi trường `Hugo_version` trong tệp [`netlify.toml`] (netlify.toml#l11). Để cài đặt các phụ thuộc, triển khai và kiểm tra trang web cục bộ, chạy: - Đối với MacOS và Linux ```bash npm ci make serve ``` - Đối với Windows (PowerShell) ```powershell npm ci hugo.exe server --buildFuture --environment development ``` Điều này sẽ khởi động máy chủ Hugo cục bộ trên cổng 1313. Mở trình duyệt của bạn thành <http://localhost:1313> để xem trang web. Khi bạn thay đổi các tệp nguồn, Hugo cập nhật trang web và buộc phải làm mới trình duyệt. ## Xây dựng các trang tài liệu tham khảo API Các trang tài liệu tham khảo API nằm trong `content/en/docs/reference/kubernetes-api` được xây dựng từ Swagger specification, còn được gọi là OpenAPI specification, sử dụng <https://github.com/kubernetes-sigs/reference-docs/tree/master/gen-resourcesdocs>. Để cập nhật các trang tài liệu tham khảo cho một phiên bản Kubernetes mới, làm theo các bước sau: 1. Kéo về submodule `api-ref-generator`: ```bash git submodule update --init --recursive --depth 1 ``` 2. Cập nhật Swagger specification: ```bash curl 'https://raw.githubusercontent.com/kubernetes/kubernetes/master/api/openapi-spec/swagger.json' > api-ref-assets/api/swagger.json ``` 3. Trong `api-ref-assets/config/`, điều chỉnh các tệp `toc.yaml` và `fields.yaml` để phản ánh các thay đổi của phiên bản mới. 4. Tiếp theo, xây dựng các trang: ```bash make api-reference ``` Bạn có thể kiểm tra kết quả trên máy cục bộ bằng cách xây dựng và chạy trang web từ một container: ```bash make container-serve ``` </ins> <del> ## Chạy website cục bộ dùng Hugo </del> <ins> Trong trình duyệt web, truy cập vào <http://localhost:1313/docs/reference/kubernetes-api/> để xem tài liệu tham khảo API. </ins> <del> Hãy xem [tài liệu chính thức của Hugo](https://gohugo.io/getting-started/installing/) cho việc hướng dẫn cài đặt Hugo. Đảm bảo cài đặt phiên bản mở rộng của Hugo được xác định bởi biến môi trường `HUGO_VERSION` trong file [`netlify.toml`](netlify.toml#L9) </del> <ins> 5. Khi tất cả các thay đổi của hợp đồng mới được phản ánh vào các tệp cấu hình `toc.yaml` và `fields.yaml`, tạo một Pull Request với các trang tài liệu tham khảo API mới được tạo ra. </ins> <del> Để chạy website cục bộ khi Hugo được cài đặt: </del> <ins> ## Khắc phục sự cố ### Lỗi: failed to transform resource: TOCSS: failed to transform "scss/main.scss" (text/x-scss): tính năng này không khả dụng trong phiên bản Hugo hiện tại của bạn Hugo được cung cấp dưới dạng hai bộ công cụ nhị phân vì lý do kỹ thuật. Trang web hiện tại chạy dựa trên phiên bản **Hugo Extended** duy nhất. Trong [trang phát hành](https://github.com/gohugoio/hugo/releases), tìm kiếm các bản lưu trữ có chứa từ khóa `extended` trong tên. Để xác nhận, chạy `hugo version` và tìm từ khóa `extended`. ### Khắc phục sự cố trên macOS với quá nhiều tệp mở Nếu bạn chạy `make serve` trên macOS và nhận được lỗi sau đây: </ins> ```bash <del> make serve </del> <ins> ERROR 2020/08/01 19:09:18 Error: listen tcp 127.0.0.1:1313: socket: too many open files make: *** [serve] Error 1 ``` Hãy kiểm tra giới hạn hiện tại cho số tệp mở: `launchctl limit maxfiles` Sau đó, chạy các lệnh sau (được thích nghi từ <https://gist.github.com/tombigel/d503800a282fcadbee14b537735d202c>): ```shell #!/bin/sh # Đây là các liên kết gist gốc, liên kết đến các gist của tôi ngay bây giờ. # curl -O https://gist.githubusercontent.com/a2ikm/761c2ab02b7b3935679e55af5d81786a/raw/ab644cb92f216c019a2f032bbf25e258b01d87f9/limit.maxfiles.plist # curl -O https://gist.githubusercontent.com/a2ikm/761c2ab02b7b3935679e55af5d81786a/raw/ab644cb92f216c019a2f032bbf25e258b01d87f9/limit.maxproc.plist curl -O https://gist.githubusercontent.com/tombigel/d503800a282fcadbee14b537735d202c/raw/ed73cacf82906fdde59976a0c8248cce8b44f906/limit.maxfiles.plist curl -O https://gist.githubusercontent.com/tombigel/d503800a282fcadbee14b537735d202c/raw/ed73cacf82906fdde59976a0c8248cce8b44f906/limit.maxproc.plist sudo mv limit.maxfiles.plist /Library/LaunchDaemons sudo mv limit.maxproc.plist /Library/LaunchDaemons sudo chown root:wheel /Library/LaunchDaemons/limit.maxfiles.plist sudo chown root:wheel /Library/LaunchDaemons/limit.maxproc.plist sudo launchctl load -w /Library/LaunchDaemons/limit.maxfiles.plist </ins> ``` <del> Câu lệnh trên sẽ khởi động server Hugo cục bộ trên cổng 1313. Mở trình duyệt và đến địa chỉ http://localhost:1313 để xem website. Khi bạn thay đổi các file nguồn, Hugo cập nhật website và buộc làm mới trình duyệt. </del> <ins> Điều này hoạt động cho cả macOS Catalina và Mojave. </ins> <del> ## Cộng đồng, thảo luận, đóng góp và hỗ trợ </del> <ins> ## Tham gia với SIG Docs </ins> <del> Tìm hiểu cách tham gia với cộng đồng Kubernetes trên [trang cộng đồng](http://kubernetes.io/community/). </del> <ins> Tìm hiểu thêm về cộng đồng SIG Docs Kubernetes và cuộc họp trên [trang cộng đồng](https://github.com/kubernetes/community/tree/master/sig-docs#meetings). </ins> <del> Bạn có thể tiếp cận những maintainers của dự án này tại: </del> <ins> Bạn cũng có thể liên hệ với những người duy trì dự án này tại: </ins> - [Slack](https://kubernetes.slack.com/messages/sig-docs) <ins> - [Nhận lời mời tham gia Slack này](https://slack.k8s.io/) </ins> - [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs) <del> ### Quy tắc ứng xử </del> <ins> ## Đóng góp vào tài liệu Bạn có thể nhấp vào nút **Fork** ở phía trên bên phải của màn hình để tạo một bản sao của kho lưu trữ này trong tài khoản GitHub của bạn. Bản sao này được gọi là _fork_. Thực hiện bất kỳ thay đổi nào bạn muốn trong fork của bạn, và khi bạn sẵn sàng gửi những thay đổi đó cho chúng tôi, hãy vào fork của bạn và tạo một pull request mới để thông báo cho chúng tôi biết về nó. Sau khi pull request của bạn được tạo, một người xem Kubernetes sẽ chịu trách nhiệm cung cấp phản hồi rõ ràng, có thể thực hiện được. Là chủ sở hữu của pull request, **bạn có trách nhiệm sửa đổi pull request của mình để giải quyết phản hồi đã được cung cấp cho bạn bởi người xem Kubernetes.** Lưu ý rằng bạn có thể nhận được phản hồi từ nhiều người đánh giá Kubernetes hoặc bạn có thể nhận được phản hồi từ một người đánh giá Kubernetes khác với người được chỉ định ban đầu để cung cấp phản hồi. Hơn nữa, trong một số trường hợp, một trong những người đánh giá của bạn có thể yêu cầu một đánh giá kỹ thuật từ một người đánh giá kỹ thuật Kubernetes khi cần thiết. Người đánh giá sẽ cố gắng cung cấp phản hồi một cách kịp thời, nhưng thời gian phản hồi có thể thay đổi tùy thuộc vào các tình huống. Để biết thêm thông tin về việc đóng góp vào tài liệu Kubernetes, hãy xem: - [Đóng góp vào tài liệu Kubernetes](https://kubernetes.io/docs/contribute/) - [Loại nội dung trang](https://kubernetes.io/docs/contribute/style/page-content-types/) - [Hướng dẫn về phong cách tài liệu](https://kubernetes.io/docs/contribute/style/style-guide/) - [Dịch tài liệu Kubernetes](https://kubernetes.io/docs/contribute/localization/) - [Giới thiệu về tài liệu Kubernetes](https://www.youtube.com/watch?v=pprMgmNzDcw) ### Đại sứ đóng góp mới Nếu bạn cần trợ giúp bất kỳ lúc nào khi đóng góp, [Đại sứ đóng góp mới](https://kubernetes.io/docs/contribute/advanced/#serve-as-a-new-contributor-ambassador) là điểm liên lạc tốt. Đây là những người phê duyệt SIG Docs có trách nhiệm hướng dẫn các đóng góp viên mới và giúp họ qua những pull request đầu tiên. Nơi tốt nhất để liên hệ với Đại sứ đóng góp mới là trên [Kubernetes Slack](https://slack.k8s.io/). Đại sứ đóng góp mới hiện tại cho SIG Docs: | Name                       | Slack                      | GitHub                     | | -------------------------- | -------------------------- | -------------------------- | | Arsh Sharma                | @arsh                      | @RinkiyaKeDad              | ## Các tệp README đa ngôn ngữ | Language                   | Language                   | | -------------------------- | -------------------------- | | [Chinese](README-zh.md)    | [Korean](README-ko.md)     | | [French](README-fr.md)     | [Polish](README-pl.md)     | | [German](README-de.md)     | [Portuguese](README-pt.md) | | [Hindi](README-hi.md)      | [Russian](README-ru.md)    | | [Indonesian](README-id.md) | [Spanish](README-es.md)    | | [Italian](README-it.md)    | [Ukrainian](README-uk.md)  | | [Japanese](README-ja.md)   | [Vietnamese](README-vi.md) | ## Quy tắc ứng xử </ins> <del> Sự tham gia vào cộng đồng Kubernetes được điểu chỉnh bởi [Kubernetes Code of Conduct](code-of-conduct.md). </del> <ins> Sự tham gia vào cộng đồng Kubernetes được điều chỉnh bởi [Quy tắc ứng xử của CNCF](https://github.com/cncf/foundation/blob/main/code-of-conduct.md). </ins> <del> ## Cảm ơn! </del> <ins> ## Cảm ơn bạn </ins> <del> Kubernetes phát triển mạnh mẽ về sự tham gia của cộng đồng và chúng tôi đánh giá cao những đóng góp của bạn cho trang web và tài liệu của chúng tôi! </del> <ins> Kubernetes phát triển dựa trên sự tham gia của cộng đồng, và chúng tôi đánh giá cao những đóng góp của bạn cho trang web và tài liệu của chúng tôi! </ins>  No newline at end of file

Đề nghị thay thế "lạc thú" bằng "lỗi thời" !
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
Please raise the issue in english putting the language code before the issue in [] example [vi] Issue title here It will be good practice to write the description and title of the issue in English only.
Thank you! BTW i'd commited about this change, waiting for review.
Fixed in


Question: cid: home --- <del> {{< announcement >}} {{< deprecationwarning >}} </del> {{< blocks/section id="oceanNodes" >}} {{% blocks/feature image="flower" %}} <!--

Umbrella issue: Remove the following from L6-8:
/kind cleanup
/assign /language uk


Question: There are two special cases: <del> * An empty `key` with operator `Exists` matches all keys, values and effects which means this </del> <ins> An empty `key` with operator `Exists` matches all keys, values and effects which means this </ins> will tolerate everything. <del> ```yaml tolerations: - operator: "Exists" ``` * An empty `effect` matches all effects with key `key`. ```yaml tolerations: - key: "key" operator: "Exists" ``` </del> <ins> An empty `effect` matches all effects with key `key`. </ins> {{< /note >}}

This is a Bug Report Problem: The document is not rendered correctly: ! Proposed Solution: In-lining this special cases text by removing the call-out seems reasonable? Page to Update:
This is related to tracking issue . The long term fix is probably along the lines of For a work-around, how about rewording the note so that it remains called out but does not use a bulleted list? /kind bug /language en


Question: ## Support for ThirdPartyResources As of Kubernetes 1.5, ThirdPartyResources are not supported by `kubectl apply`. <del> The recommended approach for ThirdPartyResources is to use [imperative object configuration](/docs/concepts/tools/kubectl/object-management-using-imperative-config/). </del> <ins> The recommended approach for ThirdPartyResources is to use [imperative object configuration](/docs/tutorials/object-management-kubectl/imperative-object-management-configuration/). </ins> {% endcapture %} {% capture whatsnext %}

<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: 404 on Proposed Solution: Update location of Page to Update: