Question: <ins> --- title: フィーチャーゲート(Feature gate) id: feature-gate date: 2023-01-12 full_link: /ja/docs/reference/command-line-tools-reference/feature-gates/ short_description: > 特定のKubernetes機能を有効にするかどうかを制御する方法。 aka: tags: - fundamental - operation --- フィーチャーゲートはクラスター内でどのKubernetes機能を有効にするかを制御するために使用できるキー(不透明な文字列値)のセットです。 <!--more--> 各Kubernetesコンポーネントで`--feature-gates`コマンドラインフラグを使用して、これらの機能をオンまたはオフにすることができます。 各Kubernetesコンポーネントでは、そのコンポーネントに関連する一連のフィーチャーゲートを有効または無効にすることができます。 Kubernetesのドキュメントには、現在のすべての[フィーチャーゲート](/ja/docs/reference/command-line-tools-reference/feature-gates/)とその制御対象がリストされています。 </ins>

Note that this issue is for Japanese Speaker This is a Feature Request What would you like to be Translate into Japanese Why is this needed There is no Japanese translation for this page Comments File to translate: Original: Japanese Localization document: /area localization /language ja /good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : Note that this issue is for Japanese Speaker Original: /language ja /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/triage accepted
/assign
san, can you please review the PR


Question: message: | 4 days of incredible opportunities to collaborate, learn + share with the entire community!<br /> April 18 - April 21, 2023. - name: Redirecting k8s.gcr.io - After startTime: 2023-03-27T00:00:00 # This should run after the redirect begins endTime: 2023-05-31T00:00:00

This is a Feature Request What would you like to be Set a banner to announce KubeCon 2023 NA Why is this needed We usually turn on a banner for the upcoming KubeCon, and we're about ~3 weeks out. Logos are available from: (make sure to copy the logo into this repo) should help with text Also see the config for a previous year's NA KubeCon. Comments This change will need steering committee approval. I would set the banner to start on the Oct 20, 2023 and to end on the November 9, 2023 at 1800 CEST. /priority important-soon
/triage accepted
Banner is smaller than the usual size


Question: ## `coredns` (or `kube-dns`) is stuck in the `Pending` state This is **expected** and part of the design. kubeadm is network provider-agnostic, so the admin <del> should [install the pod network solution](/docs/concepts/cluster-administration/addons/) </del> <ins> should [install the pod network add-on](/docs/concepts/cluster-administration/addons/) </ins> of choice. You have to install a Pod Network before CoreDNS may be deployed fully. Hence the `Pending` state before the network is set up. ## `HostPort` services do not work The `HostPort` and `HostIP` functionality is available depending on your Pod Network <del> provider. Please contact the author of the Pod Network solution to find out whether </del> <ins> provider. Please contact the author of the Pod Network add-on to find out whether </ins> `HostPort` and `HostIP` functionality are available. Calico, Canal, and Flannel CNI providers are verified to support HostPort.

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: There are words should be unified in and . For the sake of clarity, the same words should be used for things that have the same meaning. Proposed Solution: We should use either the terms "network solution" or "network add-on". Page to Update: Troubleshooting kubeadm: Installing Addons: <!--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
modifying the kubeadm troubleshooting page to use "addon" instead of "solution" seems fine to me. PRs welcome! /help /sig cluster-lifecycle /kind cleanup /priority backlog
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : modifying the kubeadm troubleshooting page to use "addon" instead of "solution" seems fine to me. PRs welcome! /sig cluster-lifecycle /kind cleanup /priority backlog </details
/assign
/assign


Question: <del> --- reviewers: - johnbelamaric - imroc title: Topology-aware traffic routing with topology keys content_type: concept weight: 150 --- <!-- overview --> {{< feature-state for_k8s_version="v1.21" state="deprecated" >}} {{< note >}} This feature, specifically the alpha `topologyKeys` API, is deprecated since Kubernetes v1.21. [Topology Aware Routing](/docs/concepts/services-networking/topology-aware-routing/), introduced in Kubernetes v1.21, provides similar functionality. {{</ note >}} _Service Topology_ enables a service to route traffic based upon the Node topology of the cluster. For example, a service can specify that traffic be preferentially routed to endpoints that are on the same Node as the client, or in the same availability zone. <!-- body --> ## Topology-aware traffic routing By default, traffic sent to a `ClusterIP` or `NodePort` Service may be routed to any backend address for the Service. Kubernetes 1.7 made it possible to route "external" traffic to the Pods running on the same Node that received the traffic. For `ClusterIP` Services, the equivalent same-node preference for routing wasn't possible; nor could you configure your cluster to favor routing to endpoints within the same zone. By setting `topologyKeys` on a Service, you're able to define a policy for routing traffic based upon the Node labels for the originating and destination Nodes. The label matching between the source and destination lets you, as a cluster operator, designate sets of Nodes that are "closer" and "farther" from one another. You can define labels to represent whatever metric makes sense for your own requirements. In public clouds, for example, you might prefer to keep network traffic within the same zone, because interzonal traffic has a cost associated with it (and intrazonal traffic typically does not). Other common needs include being able to route traffic to a local Pod managed by a DaemonSet, or directing traffic to Nodes connected to the same top-of-rack switch for the lowest latency. ## Using Service Topology If your cluster has the `ServiceTopology` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) enabled, you can control Service traffic routing by specifying the `topologyKeys` field on the Service spec. This field is a preference-order list of Node labels which will be used to sort endpoints when accessing this Service. Traffic will be directed to a Node whose value for the first label matches the originating Node's value for that label. If there is no backend for the Service on a matching Node, then the second label will be considered, and so forth, until no labels remain. If no match is found, the traffic will be rejected, as if there were no backends for the Service at all. That is, endpoints are chosen based on the first topology key with available backends. If this field is specified and all entries have no backends that match the topology of the client, the service has no backends for that client and connections should fail. The special value `"*"` may be used to mean "any topology". This catch-all value, if used, only makes sense as the last value in the list. If `topologyKeys` is not specified or empty, no topology constraints will be applied. Consider a cluster with Nodes that are labeled with their hostname, zone name, and region name. Then you can set the `topologyKeys` values of a service to direct traffic as follows. * Only to endpoints on the same node, failing if no endpoint exists on the node: `["kubernetes.io/hostname"]`. * Preferentially to endpoints on the same node, falling back to endpoints in the same zone, followed by the same region, and failing otherwise: `["kubernetes.io/hostname", "topology.kubernetes.io/zone", "topology.kubernetes.io/region"]`. This may be useful, for example, in cases where data locality is critical. * Preferentially to the same zone, but fallback on any available endpoint if none are available within this zone: `["topology.kubernetes.io/zone", "*"]`. ## Constraints * Service topology is not compatible with `externalTrafficPolicy=Local`, and therefore a Service cannot use both of these features. It is possible to use both features in the same cluster on different Services, only not on the same Service. * Valid topology keys are currently limited to `kubernetes.io/hostname`, `topology.kubernetes.io/zone`, and `topology.kubernetes.io/region`, but will be generalized to other node labels in the future. * Topology keys must be valid label keys and at most 16 keys may be specified. * The catch-all value, `"*"`, must be the last value in the topology keys, if it is used. ## Examples The following are common examples of using the Service Topology feature. ### Only Node Local Endpoints A Service that only routes to node local endpoints. If no endpoints exist on the node, traffic is dropped: ```yaml apiVersion: v1 kind: Service metadata: name: my-service spec: selector: app: my-app ports: - protocol: TCP port: 80 targetPort: 9376 topologyKeys: - "kubernetes.io/hostname" ``` ### Prefer Node Local Endpoints A Service that prefers node local Endpoints but falls back to cluster wide endpoints if node local endpoints do not exist: ```yaml apiVersion: v1 kind: Service metadata: name: my-service spec: selector: app: my-app ports: - protocol: TCP port: 80 targetPort: 9376 topologyKeys: - "kubernetes.io/hostname" - "*" ``` ### Only Zonal or Regional Endpoints A Service that prefers zonal then regional endpoints. If no endpoints exist in either, traffic is dropped. ```yaml apiVersion: v1 kind: Service metadata: name: my-service spec: selector: app: my-app ports: - protocol: TCP port: 80 targetPort: 9376 topologyKeys: - "topology.kubernetes.io/zone" - "topology.kubernetes.io/region" ``` ### Prefer Node Local, Zonal, then Regional Endpoints A Service that prefers node local, zonal, then regional endpoints but falls back to cluster wide endpoints. ```yaml apiVersion: v1 kind: Service metadata: name: my-service spec: selector: app: my-app ports: - protocol: TCP port: 80 targetPort: 9376 topologyKeys: - "kubernetes.io/hostname" - "topology.kubernetes.io/zone" - "topology.kubernetes.io/region" - "*" ``` ## {{% heading "whatsnext" %}} * Read about [Topology Aware Hints](/docs/concepts/services-networking/topology-aware-hints/) * Read [Connecting Applications with Services](/docs/tutorials/services/connect-applications-service/) </del>

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Topology-aware traffic routing with topology keys is deprecated since 1.21 Confirm if it's removed and remove the related documentation if feature is removed Proposed Solution: Remove Service Topology page Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Deprecated since 1.21 <!--Additional Information:--
/kind cleanup /language en
I can look into this. /assign
/sign network /triage accepted /priority important-longterm
Thanks


Question: The kubelet acts as a client when connecting to the container runtime via gRPC. The runtime and image service endpoints have to be available in the container runtime, which can be configured separately within the kubelet by using the <del> `--image-service-endpoint` and `--container-runtime-endpoint` [command line flags](/docs/reference/command-line-tools-reference/kubelet) </del> <ins> `--image-service-endpoint` [command line flags](/docs/reference/command-line-tools-reference/kubelet). </ins> For Kubernetes v{{< skew currentVersion >}}, the kubelet prefers to use CRI `v1`. If a container runtime does not support `v1` of the CRI, then the kubelet tries to

Documentation for external etcd cluster for kubernetes 1.27 is not up to date That the documentation doesn't take into consideration the fact that was removed in version 1.27 of kubelet: Restart=always Just try to install kubernetes with an external etcd cluster (which right now doesn't work anyway also for other reasons related to this ) with version 1.27.2 and you'll get: No response <details27.2 </details<detailsself-hosted </details<details</details<detailskubeadm </details<detailscontainerd </details<detailscalico </details
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands: - Please see the for a listing of the SIGs, working groups, and committees available. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/transfer website /assign
removed the comment in v1.27. is not re-generated. I opened to fix it.
/retitle flag still in the documentation for external etcd in version 1.27 despite removal /language en /triage accepted


Question: - ianychoi - seokho-son - ysyukr <del> sig-docs-maintainers: # Website maintainers </del> <ins> sig-docs-leads: # Website chairs and tech leads </ins> - jimangel - kbarnard10 <del> - pwittrock - steveperry-53 </del> <ins> - kbhawkey - onlydole - sftim </ins> - zacharysarah <del> - zparnold </del> sig-docs-zh-owners: # Admins for Chinese content - chenopis - chenrui333

The  group in OWNERSALIASES is a historical artifact with no permissions associated with it. Remove the team from OWNERS_ALIASES. I'm also proposing to update the description of from "Website admins" to "Website chairs and tech leads" and add and to the group. For more information, see We need to update the to replace with I propose continuing to limit repo admin access to current chairs. /assign


Question: Podのコンテナは準備完了ですが、少なくとも1つのカスタムのConditionが欠落しているか「False」の場合、kubeletはPodの[Condition](#pod-condition)を`ContainersReady`に設定します。 <ins> ### PodのネットワークのReadiness {#pod-has-network} {{< feature-state for_k8s_version="v1.25" state="alpha" >}} Podがノードにスケジュールされた後、kubeletによって承認され、任意のボリュームがマウントされる必要があります。これらのフェーズが完了すると、kubeletはコンテナランタイム({{< glossary_tooltip term_id="cri" >}}を使用)と連携して、ランタイムサンドボックスのセットアップとPodのネットワークを構成します。もし`PodHasNetworkCondition`[フィーチャーゲート](/ja/docs/reference/command-line-tools-reference/feature-gates/)が有効になっている場合、kubeletは、Podがこの初期化の節目に到達したかどうかをPodの`status.conditions`フィールドにある`PodHasNetwork`状態を使用して報告します。 ネットワークが設定されたランタイムサンドボックスがPodにないことを検出すると、`PodHasNetwork`状態は、kubelet によって`False`に設定されます。これは、以下のシナリオで発生します: * Podのライフサイクルの初期で、kubeletがコンテナランタイムを使用してPodのサンドボックスのセットアップをまだ開始していないとき * Podのライフサイクルの後期で、Podのサンドボックスが以下のどちらかの原因で破壊された場合: * Podを退去させず、ノードが再起動する * コンテナランタイムの隔離に仮想マシンを使用している場合、Podサンドボックスの仮想マシンが再起動し、新しいサンドボックスと新しいコンテナネットワーク設定を作成する必要があります ランタイムプラグインによるサンドボックスの作成とPodのネットワーク設定が正常に完了すると、kubeletによって`PodHasNetwork`状態が`True`に設定されます。`PodHasNetwork`状態が`True`に設定された後、kubeletはコンテナイメージの取得とコンテナの作成を開始することができます。 initコンテナを持つPodの場合、initコンテナが正常に完了すると(ランタイムプラグインによるサンドボックスの作成とネットワーク設定が正常に行われた後に発生)、kubeletは`Initialized`状態を`True`に設定します。initコンテナがないPodの場合、サンドボックスの作成およびネットワーク設定が開始する前にkubeletは`Initialized`状態を`True`に設定します。 </ins> ## コンテナのProbe {#container-probes} <del> [Probe](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#probe-v1-core) は [kubelet](/docs/reference/command-line-tools-reference/kubelet/) により定期的に実行されるコンテナの診断です。診断を行うために、kubeletはコンテナに実装された [Handler](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#handler-v1-core)を呼びます。Handlerには次の3つの種類があります: </del> <ins> *Probe*は[kubelet](/docs/reference/command-line-tools-reference/kubelet/) により定期的に実行されるコンテナの診断です。診断を行うために、kubeletはコンテナ内でコードを実行するか、ネットワークリクエストします。 </ins> <del> * [ExecAction](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#execaction-v1-core): コンテナ内で特定のコマンドを実行します。コマンドがステータス0で終了した場合に診断を成功と見まします。 </del> <ins> ### チェックのメカニズム {#probe-check-methods} </ins> <del> * [TCPSocketAction](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#tcpsocketaction-v1-core): PodのIPの特定のポートにTCPチェックを行います。 そのポートが空いていれば診断を成功とみなします。 </del> <ins> probeを使ってコンテナをチェックする4つの異なる方法があります。 各probeは、この4つの仕組みのうち1つを正確に定義する必要があります: `exec` : コンテナ内で特定のコマンドを実行します。コマンドがステータス0で終了した場合に診断を成功と見なします。 `grpc` : [gRPC](https://grpc.io/)を使ってリモートプロシージャコールを実行します。 ターゲットは、[gRPC health checks](https://grpc.io/grpc/core/md_doc_health-checking.html)を実装する必要があります。 レスポンスの`status`が`SERVING`の場合に診断を成功と見なします。 gRPCはアルファ版の機能のため、`GRPCContainerProbe`[フィーチャーゲート](/ja/docs/reference/command-line-tools-reference/feature-gates/)が 有効の場合のみ利用可能です。 </ins> <del> * [HTTPGetAction](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#httpgetaction-v1-core): PodのIPの特定のポートとパスに対して、HTTP GETのリクエストを送信します。 </del> <ins> `httpGet` : PodのIPアドレスに対して、指定されたポートとパスでHTTP `GET`のリクエストを送信します。 </ins> レスポンスのステータスコードが200以上400未満の際に診断を成功とみなします。 <ins> `tcpSocket` : PodのIPアドレスに対して、指定されたポートでTCPチェックを行います。 そのポートが空いていれば診断を成功とみなします。 オープンしてすぐにリモートシステム(コンテナ)が接続を切断した場合、健全な状態としてカウントします。 ### Probeの結果 {#probe-outcome} </ins> 各Probe 次の3つのうちの一つの結果を持ちます: <del> * `Success`: コンテナの診断が成功しました。 * `Failure`: コンテナの診断が失敗しました。 * `Unknown`: コンテナの診断が失敗し、取れるアクションがありません。 </del> <ins> `Success` : コンテナの診断が成功しました。 `Failure` : コンテナの診断が失敗しました。 `Unknown` : コンテナの診断が失敗しました(何も実行する必要はなく、kubeletはさらにチェックを行います)。 ### Probeの種類 {#types-of-probe} </ins> <del> Kubeletは3種類のProbeを実行中のコンテナで行い、また反応することができます: </del> <ins> kubeletは3種類のProbeを実行中のコンテナで行い、また反応することができます: </ins> <del> * `livenessProbe`: コンテナが動いているかを示します。 livenessProbe に失敗すると、kubeletはコンテナを殺します、そしてコンテナは[restart policy](#restart-policy)に従います。 コンテナにlivenessProbeが設定されていない場合、デフォルトの状態は`Success`です。 </del> <ins> `livenessProbe` : コンテナが動いているかを示します。 livenessProbeに失敗すると、kubeletはコンテナを殺します、そしてコンテナは[restart policy](#restart-policy)に従います。 コンテナにlivenessProbeが設定されていない場合、デフォルトの状態は`Success`です。 </ins> <del> * `readinessProbe`: コンテナがリクエスト応答する準備ができているかを示します。 readinessProbeに失敗すると、エンドポイントコントローラーにより、ServiceからそのPodのIPアドレスが削除されます。 initial delay前のデフォルトのreadinessProbeの初期値は`Failure`です。 コンテナにreadinessProbeが設定されていない場合、デフォルトの状態は`Success`です。 </del> <ins> `readinessProbe` : コンテナがリクエスト応答する準備ができているかを示します。 readinessProbeに失敗すると、エンドポイントコントローラーにより、ServiceからそのPodのIPアドレスが削除されます。 initial delay前のデフォルトのreadinessProbeの初期値は`Failure`です。 コンテナにreadinessProbeが設定されていない場合、デフォルトの状態は`Success`です。 </ins> <del> * `startupProbe`: コンテナ内のアプリケーションが起動したかどうかを示します。 startupProbeが設定された場合、完了するまでその他のすべてのProbeは無効になります。 startupProbeに失敗すると、kubeletはコンテナを殺します、そしてコンテナは[restart policy](#restart-policy)に従います。 コンテナにstartupProbeが設定されていない場合、デフォルトの状態は`Success`です。 </del> <ins> `startupProbe` : コンテナ内のアプリケーションが起動したかどうかを示します。 startupProbeが設定された場合、完了するまでその他のすべてのProbeは無効になります。 startupProbeに失敗すると、kubeletはコンテナを殺します、そしてコンテナは[restart policy](#restart-policy)に従います。 コンテナにstartupProbeが設定されていない場合、デフォルトの状態は`Success`です。 </ins> livenessProbe、readinessProbeまたはstartupProbeを設定する方法の詳細については、[Liveness Probe、Readiness ProbeおよびStartup Probeを使用する](/ja/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/)を参照してください。 <del> ### livenessProbeをいつ使うべきか? {#when-should-you-use-a-liveness-probe} </del> <ins> #### livenessProbeをいつ使うべきか? {#when-should-you-use-a-liveness-probe} </ins> {{< feature-state for_k8s_version="v1.0" state="stable" >}} <del> コンテナ自体に問題が発生した場合や状態が悪くなった際にクラッシュすることができればlivenessProbeは不要です. </del> <ins> コンテナ自体に問題が発生した場合や状態が悪くなった際にクラッシュすることができればlivenessProbeは不要です。 </ins> この場合kubeletが自動でPodの`restartPolicy`に基づいたアクションを実行します。 Probeに失敗したときにコンテナを殺したり再起動させたりするには、livenessProbeを設定し`restartPolicy`をAlwaysまたはOnFailureにします。 <del> ### readinessProbeをいつ使うべきか? {#when-should-you-use-a-readiness-probe} </del> <ins> #### readinessProbeをいつ使うべきか? {#when-should-you-use-a-readiness-probe} </ins> {{< feature-state for_k8s_version="v1.0" state="stable" >}} Probeが成功したときにのみPodにトラフィックを送信したい場合は、readinessProbeを指定します。 <del> この場合readinessProbeはlivenessProbeと同じになる可能性がありますが、readinessProbeが存在するということは、Podがトラフィックを受けずに開始され、Probe成功が開始した後でトラフィックを受け始めることになります。コンテナが起動時に大きなデータ、構成ファイル、またはマイグレーションを読み込む必要がある場合は、readinessProbeを指定します。 </del> <ins> この場合readinessProbeはlivenessProbeと同じになる可能性がありますが、readinessProbeが存在するということは、Podがトラフィックを受けずに開始され、Probe成功が開始した後でトラフィックを受け始めることになります。 </ins> コンテナがメンテナンスのために停止できるようにするには、livenessProbeとは異なる、特定のエンドポイントを確認するreadinessProbeを指定することができます。 <ins> アプリがバックエンドサービスと厳密な依存関係にある場合、livenessProbeとreadinessProbeの両方を実装することができます。アプリ自体が健全であればlivenessProbeはパスしますが、readinessProbeはさらに、必要なバックエンドサービスが利用可能であるかどうかをチェックします。これにより、エラーメッセージでしか応答できないPodへのトラフィックの転送を避けることができます。 コンテナの起動中に大きなデータ、構成ファイル、またはマイグレーションを読み込む必要がある場合は、[startupProbe](#when-should-you-use-a-startup-probe)を使用できます。ただし、失敗したアプリと起動データを処理中のアプリの違いを検出したい場合は、readinessProbeを使用した方が良いかもしれません。 </ins> {{< note >}} Podが削除されたときにリクエストを来ないようにするためには必ずしもreadinessProbeが必要というわけではありません。Podの削除時にはreadinessProbeが存在するかどうかに関係なくPodは自動的に自身をunreadyにします。Pod内のコンテナが停止するのを待つ間Podはunreadyのままです。 {{< /note >}} <del> ### startupProbeをいつ使うべきか? {#when-should-you-use-a-startup-probe} </del> <ins> #### startupProbeをいつ使うべきか? {#when-should-you-use-a-startup-probe} </ins> <del> {{< feature-state for_k8s_version="v1.18" state="beta" >}} </del> <ins> {{< feature-state for_k8s_version="v1.20" state="stable" >}} </ins> startupProbeは、サービスの開始に時間がかかるコンテナを持つPodに役立ちます。livenessProbeの間隔を長く設定するのではなく、コンテナの起動時に別のProbeを構成して、livenessProbeの間隔よりも長い時間を許可できます。 <del> コンテナの起動時間が、`initialDelaySeconds + failureThreshold x periodSeconds`よりも長い場合は、livenessProbeと同じエンドポイントをチェックするためにstartupProbeを指定します。`periodSeconds`のデフォルトは30秒です。次に、`failureThreshold`をlivenessProbeのデフォルト値を変更せずにコンテナが起動できるように、十分に高い値を設定します。これによりデッドロックを防ぐことができます。 </del> <ins> コンテナの起動時間が、`initialDelaySeconds + failureThreshold x periodSeconds`よりも長い場合は、livenessProbeと同じエンドポイントをチェックするためにstartupProbeを指定します。`periodSeconds`のデフォルトは10秒です。次に、`failureThreshold`をlivenessProbeのデフォルト値を変更せずにコンテナが起動できるように、十分に高い値を設定します。これによりデッドロックを防ぐことができます。 </ins> ## Podの終了 {#pod-termination}

This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/workloads/pods/pod- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/workloads/pods/pod- is outdated. For example, there is no description of PodHasNetwork(alpha feature). Comments /language ja /assign
/triage accepted


Question: Để tải về phiên bản cụ thể, hãy thay thế phần `$(curl -LS https://dl.k8s.io/release/stable.txt)` trong câu lệnh với một phiên bản cụ thể. <del> Ví dụ như, để tải về phiên bản {{< param "fullversion" >}} trên Linux, hãy nhập như sau: </del> <ins> Ví dụ như, để tải về phiên bản {{< skew currentPatchVersion >}} trên Linux, hãy nhập như sau: </ins> ``` <del> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/linux/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/linux/amd64/kubectl </ins> ``` 2. Tạo kubectl binary thực thi.

Problem: Based on , I have created this issue/task to help update the [vi] language documentation. Proposed Solution: Page to Update: In the branch, I found: Results for "fullversion" in "k8s-website/content/vi" /home/rdlugyhe/kubernetes/k8s-website/content/vi/docs/tasks/tools/install- 36: Ví dụ như, để tải về phiên bản {{< param "fullversion" }} trên Linux, hãy nhập như sau: 39: curl -LO {{< param "fullversion" }}/bin/linux/amd64/kubectl 111: Ví dụ, để tải về phiên bản {{< param "fullversion" }} trên macOS, gõ: 114: curl -LO {{< param "fullversion" }}/bin/darwin/amd64/kubectl 176: 1. Tải về phiên bản mới nhất {{< param "fullversion" }} từ đường dẫn nàyg


Question: ## {{% heading "whatsnext" %}} <del> * Read about the [Kubernetes control plane](/docs/concepts/#kubernetes-control-plane) * Discover some of the basic [Kubernetes objects](/docs/concepts/#kubernetes-objects) </del> <ins> * Read about the [Kubernetes control plane](/docs/concepts/overview/components/) * Discover some of the basic [Kubernetes objects](/docs/concepts/overview/working-with-objects) </ins> * Learn more about the [Kubernetes API](/docs/concepts/overview/kubernetes-api/) * If you want to write your own controller, see [Extension Patterns](/docs/concepts/extend-kubernetes/extend-cluster/#extension-patterns) in Extending Kubernetes.

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--Hyperlinks don't work Hyperlinks to topics <bKubernetes control plane</band <bKubernetes objects</btakes to back to <bConcepts</bpage rather than respective topics. Proposed Solution: Update linkw to point to correct content. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Hi If related documents are not missing, then Perhaps Kubernetes control plane should point to I noticed that the corresponding file , later than the link on page . And Kubernetes objects perhaps should point to . Seems a little bit weird. These documents should be in the same hierarchy I think. Let me create a PR to solve this issue. /assign
/kind bug
I think the link for Kubernetes control-plane should be to and I agree above that the link for Kubernetes objects should be to /assign
Hi Thanks for your PR! I submitted a PR (ref: ) to fix this issue about half a month ago, and just got approved 3 days ago. Since the CLA checking was missing after I migrated to a new github account, this PR was not merged until a few minutes ago after I let the robot recheck my CLA.


Question: --> * [Katacoda](https://www.katacoda.com/courses/kubernetes/playground) <del> * [Play with Kubernetes](http://labs.play-with-k8s.com/) </del> <ins> * [玩转 Kubernetes](http://labs.play-with-k8s.com/) </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 missing in Chinese version. See for more info. Proposed Solution: Add /docs/tasks/configmap-secret/ to zh version with three articles to be translated. [x] /zh/docs/tasks/configmap-secret/managing-secret-using-config-[x] /zh/docs/tasks/configmap-secret/managing-secret-using-[x] /zh/docs/tasks/configmap-secret/managing-secret-using- Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--
/language zh /assign


Question:
 <svg id="graph-div" width="100%" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" height="130" style="max-width: 465.6875px;" viewBox="0 0 465.6875 130"><g><g class="output"><g class="clusters"><g class="cluster" id="flowchart-cluster-721" transform="translate(232.84375,65)" style="opacity: 1;"><rect width="449.6875" height="114" x="-224.84375" y="-57"></rect><g class="label" transform="translate(0, -43)" id="graph-divText"><g transform="translate(-24.578125,-12)"><foreignObject width="49.15625" height="24">
cluster
</foreignObject></g></g></g></g><g class="edgePaths"><g class="edgePath LS-gateway LE-gatewayclass" id="L-gateway-gatewayclass" style="opacity: 1;"><path class="path" d="M264.53125,65L268.6979166666667,65C272.8645833333333,65,281.1979166666667,65,289.53125,65C297.8645833333333,65,306.1979166666667,65,310.3645833333333,65L314.53125,65" marker-end="url(#arrowhead1117)" style="fill:none"></path><defs><marker id="arrowhead1117" viewBox="0 0 10 10" refX="9" refY="5" markerUnits="strokeWidth" markerWidth="8" markerHeight="6" orient="auto"><path d="M 0 0 L 10 5 L 0 10 z" class="arrowheadPath" style="stroke-width: 1; stroke-dasharray: 1, 0;"></path></marker></defs></g><g class="edgePath LS-httproute1 LE-gateway" id="L-httproute1-gateway" style="opacity: 1;"><path class="path" d="M132.03125,65L136.19791666666666,65C140.36458333333334,65,148.69791666666666,65,157.03125,65C165.36458333333334,65,173.69791666666666,65,177.86458333333334,65L182.03125,65" marker-end="url(#arrowhead1118)" style="fill:none"></path><defs><marker id="arrowhead1118" viewBox="0 0 10 10" refX="9" refY="5" markerUnits="strokeWidth" markerWidth="8" markerHeight="6" orient="auto"><path d="M 0 0 L 10 5 L 0 10 z" class="arrowheadPath" style="stroke-width: 1; stroke-dasharray: 1, 0;"></path></marker></defs></g></g><g class="edgeLabels"><g class="edgeLabel" transform="" style="opacity: 1;"><g transform="translate(0,0)" class="label"><rect rx="0" ry="0" width="0" height="0"></rect><foreignObject width="0" height="0">

</foreignObject></g></g><g class="edgeLabel" transform="" style="opacity: 1;"><g transform="translate(0,0)" class="label"><rect rx="0" ry="0" width="0" height="0"></rect><foreignObject width="0" height="0">

</foreignObject></g></g></g><g class="nodes"><g class="node k8s" id="flowchart-gatewayclass-717" transform="translate(373.609375,65)" style="opacity: 1;"><rect rx="0" ry="0" x="-59.078125" y="-22" width="118.15625" height="44" class="label-container"></rect><g class="label" transform="translate(0,0)"><g transform="translate(-49.078125,-12)"><foreignObject width="98.15625" height="24">
GatewayClass
</foreignObject></g></g></g><g class="node k8s" id="flowchart-gateway-715" transform="translate(223.28125,65)" style="opacity: 1;"><rect rx="0" ry="0" x="-41.25" y="-22" width="82.5" height="44" class="label-container"></rect><g class="label" transform="translate(0,0)"><g transform="translate(-31.25,-12)"><foreignObject width="62.5" height="24">
Gateway
</foreignObject></g></g></g><g class="node k8s" id="flowchart-httproute1-719" transform="translate(82.515625,65)" style="opacity: 1;"><rect rx="0" ry="0" x="-49.515625" y="-22" width="99.03125" height="44" class="label-container"></rect><g class="label" transform="translate(0,0)"><g transform="translate(-39.515625,-12)"><foreignObject width="79.03125" height="24">
HTTPRoute
</foreignObject></g></g></g></g></g></g></svg>   No newline at end of file

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: 1. Install the `containerd.io` package from the official Docker repositories. Instructions for setting up the Docker repository for your respective Linux distribution and installing the `containerd.io` package can be found at <del> [Install Docker Engine](https://docs.docker.com/engine/install/#server). </del> <ins> [Getting started with containerd](https://github.com/containerd/containerd/blob/main/docs/getting-started.md). </ins> 1. Configure containerd:

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 page uses Docker as the source to install containerd Proposed Solution: Use as the source to install containerd Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--24 <!--Additional Information:--
/assign
/triage accepted
I assume that the motivation here is twofold: we're suggesting installing containerd from an unofficial source (albeit Docker, Inc did donate containerd) to avoid readers feeling confused when they come to replace Docker Engine as part of a cluster upgrade
The intent is to get folks into the habit of installing containerd using containerd's resources as opposed to installing from Docker to replace Docker. That's confusing in my view and also going to have the potential for flakier instructions than the project itself.


Question:
memoryManagerPolicy
 string 	  MemoryManagerPolicy is the name of the policy to use by memory manager. Requires the MemoryManager feature gate to be enabled. Dynamic Kubelet Config (beta): This field should not be updated without a full node reboot. It is safest to keep this value the same as the local config. Default: "none"

topologyManagerPolicy
 string

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: Visiting provides inaccurate default values for shutdownGracePeriod (30s rather than 0s) and shutdownGracePeriodCriticalPods (10s rather than 0s). Proposed Solution: Correct the documentation to match the actual default values. Page to Update:
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 would like to take up this ticket.


Question: other = "उद्देश्य" [options_heading] <del> other = "विकल्प" </del> <ins> other = "विकल्प" [outdated_blog__message] other = "यह लेख एक वर्ष से अधिक पुराना है। पुराने लेखों में पुरानी सामग्री हो सकती है। जाँच करें कि प्रकाशन के बाद से पृष्ठ पर दी गई जानकारी गलत तो नहीं है।" </ins> [post_create_issue] other = "issue बनाएं"

Updated with new strings from Didn't remove any strings from , even if they're missing from
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
/language hi
Completed.


Question: ### Submitting Documentation Pull Requests If you're fixing an issue in the existing documentation, you should submit a PR against the master branch.  Follow [these instructions to create a documentation pull request against the kubernetes.io repository](http://kubernetes.io/docs/home/contribute/create-pull-request/). <ins> For more information, see [contributing to Kubernetes docs](https://kubernetes.io/docs/contribute/). </ins>

This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Revise to signpost new contributors to Why is this needed If someone arrives at (possible from ) and has not already contributed to the website, then it's good to let them know that there is a whole section of documentation aimed at exactly that target audience. Comments /language en /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. --Revise to signpost new contributors to If someone arrives at (possible from ) and has not already contributed to the website, then it's good to let them know that there is a whole section of documentation aimed at exactly that target audience. /language en /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
/assign


Question: <ins> --- title: ドキュメントスタイルの概要 main_menu: true weight: 80 --- このセクション内のトピックでは、文章のスタイル、コンテンツの形式や構成、特にKubernetesのドキュメント特有のHugoカスタマイズの使用方法に関するガイダンスを提供します。 </ins>

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


Question: <ins> --- layout: blog title: 'Kubernetes 1.24: 防止未经授权的卷模式转换' date: 2022-05-18 slug: prevent-unauthorised-volume-mode-conversion-alpha --- <!-- layout: blog title: 'Kubernetes 1.24: Prevent unauthorised volume mode conversion' date: 2022-05-18 slug: prevent-unauthorised-volume-mode-conversion-alpha --> <!-- **Author:** Raunak Pradip Shah (Mirantis) --> **作者：** Raunak Pradip Shah (Mirantis) <!-- Kubernetes v1.24 introduces a new alpha-level feature that prevents unauthorised users from modifying the volume mode of a [`PersistentVolumeClaim`](/docs/concepts/storage/persistent-volumes/) created from an existing [`VolumeSnapshot`](/docs/concepts/storage/volume-snapshots/) in the Kubernetes cluster. --> Kubernetes v1.24 引入了一个新的 alpha 级特性，可以防止未经授权的用户修改基于 Kubernetes 集群中已有的 [`VolumeSnapshot`](/zh/docs/concepts/storage/volume-snapshots/) 创建的 [`PersistentVolumeClaim`](/zh/docs/concepts/storage/persistent-volumes/) 的卷模式。 <!-- ### The problem --> ### 问题 <!-- The [Volume Mode](/docs/concepts/storage/persistent-volumes/#volume-mode) determines whether a volume is formatted into a filesystem or presented as a raw block device. --> [卷模式](/zh/docs/concepts/storage/persistent-volumes/#volume-mode)确定卷是格式化为文件系统还是显示为原始块设备。 <!-- Users can leverage the `VolumeSnapshot` feature, which has been stable since Kubernetes v1.20, to create a `PersistentVolumeClaim` (shortened as PVC) from an existing `VolumeSnapshot` in the Kubernetes cluster. The PVC spec includes a `dataSource` field, which can point to an existing `VolumeSnapshot` instance. Visit [Create a PersistentVolumeClaim from a Volume Snapshot](/docs/concepts/storage/persistent-volumes/#create-persistent-volume-claim-from-volume-snapshot) for more details. --> 用户可以使用自 Kubernetes v1.20 以来就稳定的 `VolumeSnapshot` 功能， 基于 Kubernetes 集群中的已有的 `VolumeSnapshot` 创建一个 `PersistentVolumeClaim` (简称 PVC )。 PVC 规约包括一个 `dataSource` 字段，它可以指向一个已有的 `VolumeSnapshot` 实例。 查阅[基于卷快照创建 PVC](/zh/docs/concepts/storage/persistent-volumes/#create-persistent-volume-claim-from-volume-snapshot) 获取更多详细信息。 <!-- When leveraging the above capability, there is no logic that validates whether the mode of the original volume, whose snapshot was taken, matches the mode of the newly created volume. --> 当使用上述功能时，没有逻辑来验证快照所在的原始卷的模式是否与新创建的卷的模式匹配。 <!-- This presents a security gap that allows malicious users to potentially exploit an as-yet-unknown vulnerability in the host operating system. --> 这引起了一个安全漏洞，允许恶意用户潜在地利用主机操作系统中的未知漏洞。 <!-- Many popular storage backup vendors convert the volume mode during the course of a backup operation, for efficiency purposes, which prevents Kubernetes from blocking the operation completely and presents a challenge in distinguishing trusted users from malicious ones. --> 为了提高效率，许多流行的存储备份供应商在备份操作过程中转换卷模式， 这使得 Kubernetes 无法完全阻止该操作，并在区分受信任用户和恶意用户方面带来挑战。 <!-- ### Preventing unauthorised users from converting the volume mode --> ### 防止未经授权的用户转换卷模式 <!-- In this context, an authorised user is one who has access rights to perform `Update` or `Patch` operations on `VolumeSnapshotContents`, which is a cluster-level resource. It is upto the cluster administrator to provide these rights only to trusted users or applications, like backup vendors. --> 在这种情况下，授权用户是指有权对 `VolumeSnapshotContents`（集群级资源）执行 `Update` 或 `Patch` 操作的用户。集群管理员只能向受信任的用户或应用程序（如备份供应商）提供这些权限。 <!-- If the alpha feature is [enabled](https://kubernetes-csi.github.io/docs/) in `snapshot-controller`, `snapshot-validation-webhook` and `external-provisioner`, then unauthorised users will not be allowed to modify the volume mode of a PVC when it is being created from a `VolumeSnapshot`. --> 如果在 `snapshot-controller`、`snapshot-validation-webhook` 和 `external-provisioner` 中[启用](https://kubernetes-csi.github.io/docs/)了这个 alpha 特性，则基于 `VolumeSnapshot` 创建 PVC 时，将不允许未经授权的用户修改其卷模式。 <!-- To convert the volume mode, an authorised user must do the following: --> 如要转换卷模式，授权用户必须执行以下操作： <!-- 1. Identify the `VolumeSnapshot` that is to be used as the data source for a newly created PVC in the given namespace. 2. Identify the `VolumeSnapshotContent` bound to the above `VolumeSnapshot`. --> 1. 确定要用作给定命名空间中新创建 PVC 的数据源的 `VolumeSnapshot`。 2. 确定绑定到上面 `VolumeSnapshot` 的 `VolumeSnapshotContent`。 ``` kubectl get volumesnapshot -n <namespace> ``` <!-- 3. Add the annotation [`snapshot.storage.kubernetes.io/allowVolumeModeChange`](/docs/reference/labels-annotations-taints/#snapshot-storage-kubernetes-io-allowvolumemodechange) to the `VolumeSnapshotContent`. --> 3. 给 `VolumeSnapshotContent` 添加 [`snapshot.storage.kubernetes.io/allowVolumeModeChange`](/zh/docs/reference/labels-annotations-taints/#snapshot-storage-kubernetes-io-allowvolumemodechange) 注解。 <!-- 4.This annotation can be added either via software or manually by the authorised user. The `VolumeSnapshotContent` annotation must look like following manifest fragment: --> 4. 此注解可通过软件添加或由授权用户手动添加。`VolumeSnapshotContent` 注解必须类似于以下清单片段： ```yaml kind: VolumeSnapshotContent metadata: annotations: - snapshot.storage.kubernetes.io/allowVolumeModeChange: "true" ... ``` <!-- **Note**: For pre-provisioned `VolumeSnapshotContents`, you must take an extra step of setting `spec.sourceVolumeMode` field to either `Filesystem` or `Block`, depending on the mode of the volume from which this snapshot was taken. --> **注意**：对于预先制备的 `VolumeSnapshotContents`，你必须采取额外的步骤设置 `spec.sourceVolumeMode` 字段为 `Filesystem` 或 `Block`，这取决于快照所在卷的模式。 <!-- An example is shown below: --> 如下为一个示例： ```yaml apiVersion: snapshot.storage.k8s.io/v1 kind: VolumeSnapshotContent metadata: annotations: - snapshot.storage.kubernetes.io/allowVolumeModeChange: "true" name: new-snapshot-content-test spec: deletionPolicy: Delete driver: hostpath.csi.k8s.io source: snapshotHandle: 7bdd0de3-aaeb-11e8-9aae-0242ac110002 sourceVolumeMode: Filesystem volumeSnapshotRef: name: new-snapshot-test namespace: default ``` <!-- Repeat steps 1 to 3 for all `VolumeSnapshotContents` whose volume mode needs to be converted during a backup or restore operation. --> 对于在备份或恢复操作期间需要转换卷模式的所有 `VolumeSnapshotContents`，重复步骤 1 到 3。 <!-- If the annotation shown in step 4 above is present on a `VolumeSnapshotContent` object, Kubernetes will not prevent the volume mode from being converted. Users should keep this in mind before they attempt to add the annotation to any `VolumeSnapshotContent`. --> 如果 `VolumeSnapshotContent` 对象上存在上面步骤 4 中显示的注解，Kubernetes 将不会阻止转换卷模式。 用户在尝试将注解添加到任何 `VolumeSnapshotContent` 之前，应该记住这一点。 <!-- ### What's next --> ### 接下来 <!-- [Enable this feature](https://kubernetes-csi.github.io/docs/) and let us know what you think! --> [启用此特性](https://kubernetes-csi.github.io/docs/)并让我们知道你的想法! <!-- We hope this feature causes no disruption to existing workflows while preventing malicious users from exploiting security vulnerabilities in their clusters. --> 我们希望此功能不会中断现有工作流程，同时防止恶意用户利用集群中的安全漏洞。 <!-- For any issues, create a thread in the #sig-storage slack channel or an issue in the CSI external-snapshotter [repository](https://github.com/kubernetes-csi/external-snapshotter). --> 若有任何问题，请在 #sig-storage slack 频道中创建一个会话， 或在 CSI 外部快照存储[仓库](https://github.com/kubernetes-csi/external-snapshotter)中报告一个 issue。 </ins>  No newline at end of file

This is a Feature Request This page 2022-05-18-prevent-unauthorised-volume-mode- has no Chinese version <!-- 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. --Translate Chinese version for blog/_posts/2022-05-18-prevent-unauthorised-volume-mode- Why is this needed This page 2022-05-18-prevent-unauthorised-volume-mode- has no Chinese version Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language zh /assign
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details


Question: そして、集約されたPodリソース使用統計情報を、metrics-server Resource Metrics APIを通じて公開します。 このAPIは、kubeletの認証済みおよび読み取り専用ポート上の `/metrics/resource/v1beta1` で提供されます。 <del> ## フルメトリクスパイプライン </del> <ins> ## フルメトリクスパイプライン {#full-metrics-pipeline} </ins> フルメトリクスパイプラインは、より豊富なメトリクスにアクセスすることができます。 Kubernetesは、Horizontal Pod Autoscalerなどのメカニズムを使用して、現在の状態に基づいてクラスターを自動的にスケールまたは適応させることによって、これらのメトリクスに対応することができます。

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. -- page has some problems. -page link isn't working. resource metrics pipeline full metrics pipeline the Japanese page exists, some links jump to the English page. Pod Service Why is this needed it is inconvenient for the user. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/triage accepted


Question: <ins> --- reviewers: - michmike - patricklang title: Windowsノードの追加 min-kubernetes-server-version: 1.17 content_type: tutorial weight: 30 --- <!-- overview --> {{< feature-state for_k8s_version="v1.18" state="beta" >}} Kubernetesを使用してLinuxノードとWindowsノードを混在させて実行できるため、Linuxで実行するPodとWindowsで実行するPodを混在させることができます。このページでは、Windowsノードをクラスターに登録する方法を示します。 ## {{% heading "prerequisites" %}} {{< version-check >}} * WindowsコンテナをホストするWindowsノードを構成するには、[Windows Server 2019ライセンス](https://www.microsoft.com/en-us/cloud-platform/windows-server-pricing)(またはそれ以上)を取得します。 VXLAN/オーバーレイネットワークを使用している場合は、[KB4489899](https://support.microsoft.com/help/4489899)もインストールされている必要があります。 * コントロールプレーンにアクセスできるLinuxベースのKubernetes kubeadmクラスター([kubeadmを使用した単一のコントロールプレーンクラスターの作成](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/)を参照) ## {{% heading "objectives" %}} * Windowsノードをクラスターに登録する * LinuxとWindowsのPodとServiceが相互に通信できるようにネットワークを構成する <!-- lessoncontent --> ## はじめに: クラスタへのWindowsノードの追加 ### ネットワーク構成 LinuxベースのKubernetesコントロールプレーンノードを取得したら、ネットワーキングソリューションを選択できます。このガイドでは、簡単にするためにVXLANモードでのFlannelの使用について説明します。 #### Flannel構成 1. FlannelのためにKubernetesコントロールプレーンを準備する クラスター内のKubernetesコントロールプレーンでは、多少の準備が推奨されます。Flannelを使用する場合は、iptablesチェーンへのブリッジIPv4トラフィックを有効にすることをお勧めします。すべてのLinuxノードで次のコマンドを実行する必要があります: ```bash sudo sysctl net.bridge.bridge-nf-call-iptables=1 ``` 1. Linux用のFlannelをダウンロードして構成する 最新のFlannelマニフェストをダウンロード: ```bash wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml ``` VNIを4096、ポートを4789に設定するために、flannelマニフェストの`net-conf.json`セクションを変更します。次のようになります。: ```json net-conf.json: | { "Network": "10.244.0.0/16", "Backend": { "Type": "vxlan", "VNI" : 4096, "Port": 4789 } } ``` {{< note >}}Linux上のFlannelがWindows上のFlannelと相互運用するには、VNIを4096およびポート4789に設定する必要があります。これらのフィールドの説明については、[VXLANドキュメント](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#vxlan)を参照してください。{{< /note >}} {{< note >}}L2Bridge/Host-gatewayモードを使用するには、代わりに`Type`の値を`"host-gw"`に変更し、`VNI`と`Port`を省略します。{{< /note >}} 1. Flannelマニフェストを適用して検証する Flannelの構成を適用しましょう: ```bash kubectl apply -f kube-flannel.yml ``` 数分後、Flannel Podネットワークがデプロイされていれば、すべてのPodが実行されていることがわかります。 ```bash kubectl get pods -n kube-system ``` 出力結果には、実行中のLinux flannel DaemonSetが含まれているはずです: ``` NAMESPACE     NAME                                      READY        STATUS    RESTARTS   AGE ... kube-system   kube-flannel-ds-54954                     1/1          Running   0          1m ``` 1. Windows Flannelとkube-proxy DaemonSetを追加する これで、Windows互換バージョンのFlannelおよびkube-proxyを追加できます。 順番に互換性のあるバージョンのkube-proxyを確実に入手するには、イメージのタグを代用する必要があります。 次の例は、Kubernetes{{< param "fullversion" >}}の使用方法を示していますが、 独自のdeploymentに合わせてバージョンを調整する必要があります。 ```bash curl -L https://github.com/kubernetes-sigs/sig-windows-tools/releases/latest/download/kube-proxy.yml | sed 's/VERSION/{{< param "fullversion" >}}/g' | kubectl apply -f - kubectl apply -f https://github.com/kubernetes-sigs/sig-windows-tools/releases/latest/download/flannel-overlay.yml ``` {{< note >}} ホストゲートウェイを使用している場合は、代わりにhttps://github.com/kubernetes-sigs/sig-windows-tools/releases/latest/download/flannel-host-gw.ymlを使用してください。 {{< /note >}} {{< note >}} Windowsノードでイーサネット(「Ethernet0 2」など)ではなく別のインターフェースを使用している場合は、次の行を変更する必要があります。: ```powershell wins cli process run --path /k/flannel/setup.exe --args "--mode=overlay --interface=Ethernet" ``` `flannel-host-gw.yml`または`flannel-overlay.yml`ファイルで、それに応じてインターフェースを指定します。 ```bash # 例 curl -L https://github.com/kubernetes-sigs/sig-windows-tools/releases/latest/download/flannel-overlay.yml | sed 's/Ethernet/Ethernet0 2/g' | kubectl apply -f - ``` {{< /note >}} ### Windowsワーカーノードの参加 {{< note >}} `Containers`機能をインストールし、Dockerをインストールする必要があります。 行うための指示としては、[Dockerエンジンのインストール - Windowsサーバー上のエンタープライズ](https://docs.mirantis.com/docker-enterprise/v3.1/dockeree-products/docker-engine-enterprise/dee-windows.html)を利用できます。 {{< /note >}} {{< note >}} Windowsセクションのすべてのコードスニペットは、 Windowsワーカーノードの(管理者)権限を持つPowerShell環境で実行されます。 {{< /note >}} 1. wins、kubelet、kubeadmをインストールします。 ```PowerShell curl.exe -LO https://github.com/kubernetes-sigs/sig-windows-tools/releases/latest/download/PrepareNode.ps1 .PrepareNode.ps1 -KubernetesVersion {{< param "fullversion" >}} ``` 1. `kubeadm`を実行してノードに参加します コントロールプレーンホストで`kubeadm init`を実行したときに提供されたコマンドを使用します。 このコマンドがなくなった場合、またはトークンの有効期限が切れている場合は、`kubeadm token create --print-join-command` (コントロールプレーンホスト上で)を実行して新しいトークンを生成します。 #### インストールの確認 次のコマンドを実行して、クラスター内のWindowsノードを表示できるようになります: ```bash kubectl get nodes -o wide ``` 新しいノードが`NotReady`状態の場合は、flannelイメージがまだダウンロードされている可能性があります。 `kube-system`名前空間のflannel Podを確認することで、以前と同様に進行状況を確認できます: ```shell kubectl -n kube-system get pods -l app=flannel ``` flannel Podが実行されると、ノードは`Ready`状態になり、ワークロードを処理できるようになります。 ## {{% heading "whatsnext" %}} - [Windows kubeadmノードのアップグレード](/docs/tasks/administer-cluster/kubeadm/upgrading-windows-nodes) </ins>

This is a Feature Request What would you like to be Translate docs/tasks/administer-cluster/kubeadm/adding-windows-nodes/ into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign


Question: name: qos-demo-4-ctr-2 resources: {} ... <ins> status: </ins> qosClass: Burstable ```

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 location of qosClass is not correct in the last example, which is a result of the following command: Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/kind bug /language en /priority backlog /sig scheduling
/help
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /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
/assign


Question: `ContainerDevices` do expose the topology information declaring to which NUMA cells the device is affine. The NUMA cells are identified using a opaque integer ID, which value is consistent to what device <del> plugins report [when they register themselves to the kubelet](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#device-plugin-integration-with-the-topology-manager). </del> <ins> plugins report [when they register themselves to the kubelet](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#device-plugin-integration-with-the-topology-manager). </ins> The gRPC service is served over a unix socket at `/var/lib/kubelet/pod-resources/kubelet.sock`.

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 href of contains unwanted . A slash () is missing in the href of . Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en /assign
/triage accepted


Question: <!-- **Container deployment era:** Containers are similar to VMs, but they have relaxed isolation properties to share the Operating System (OS) among the applications. Therefore, containers are considered lightweight. Similar to a VM, a container has its own filesystem, CPU, memory, process space, and more. As they are decoupled from the underlying infrastructure, they are portable across clouds and OS distributions. --> <del> **Ера розгортання контейнерів:** Контейнери схожі на VM, але мають спрощений варіант ізоляції і використовують спільну операційну систему для усіх застосунків. Саму тому контейнери вважаються легковісними. Подібно до VM, контейнер має власну файлову систему, ЦПУ, пам'ять, простір процесів тощо. Оскільки контейнери вивільнені від підпорядкованої інфраструктури, їх можна легко переміщати між хмарними провайдерами чи дистрибутивами операційних систем. </del> <ins> **Ера розгортання контейнерів:** Контейнери схожі на VM, але мають спрощений варіант ізоляції і використовують спільну операційну систему для усіх застосунків. Саме тому контейнери вважаються "легкими", в порівнянні з віртуалками. Подібно до VM, контейнер має власну файлову систему, ЦПУ, пам'ять, простір процесів тощо. Оскільки контейнери вивільнені від підпорядкованої інфраструктури, їх можна легко переміщати між хмарними провайдерами чи дистрибутивами операційних систем. </ins> <!-- Containers have become popular because they provide extra benefits, such as: -->

Саму тому контейнери вважаються легковісними - wrong Саме тому контейнери вважаються легковаговими - right
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 uk
/retitle [uk] Incorrect localization for What Is Kubernetes
Thanks
/assign


Question: A `Dockerfile` is pretty self explanatory, and this one is dead simple. <del> First, it uses the official Node.js image as the base image. </del> <ins> First, it uses the official Node.js LTS image as the base image. </ins> Then, it creates a folder to store the code, `cd`s into that directory, copies the code in, and installs the dependencies with npm.

NodeJS 0.10 is going into security-only release mode very soon. The first version of 0.10 was released in March 2013, so it's over 3 years old. It would be great if we could update the tutorial/dockerfile to list the latest (or at least a newer) nodejs version.
Resolved by, thanks to


Question: webhooks or other validating admission controllers will permit the request to finish. If you disable the ValidatingAdmissionWebhook, you must also disable the <del> `ValidatingWebhookConfiguration` object in the `admissionregistration.k8s.io/v1beta1` </del> <ins> `ValidatingWebhookConfiguration` object in the `admissionregistration.k8s.io/v1` </ins> group/version via the `--runtime-config` flag (both are on by default in versions 1.9 and later).

This is a Bug Report It's not a bug, just an outdated doc thing. Problem: The MutatingWebhookConfiguration and ValidatingWebhookConfiguration APIs have been promoted to in . But the docs still show that they are in beta state at and . Proposed Solution: the description from the two plug-ins. the descriptions of the two plug-ins if they need an update too. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
I'm investigating this issue, hope I can send a PR for this after someone triaged/confirmed it. /assign
/triage accepted


Question: can use any number of volume types simultaneously. Ephemeral volume types have a lifetime of a pod, but persistent volumes exist beyond the lifetime of a pod. Consequently, a volume outlives any containers <del> that run within the pod, and data is preserved across container restarts. When a pod ceases to exist, the volume is destroyed. </del> <ins> that run within the pod, and data is preserved across container restarts. When a pod ceases to exist, Kubernetes destroys ephemeral volumes; however, Kubernetes does not destroy persistent volumes. </ins> At its core, a volume is just a directory, possibly with some data in it, which is accessible to the containers in a pod. How that directory comes to be, the

Under the Backgrounds section, there's this paragraph: I'm wondering about the last sentence: 'When a pod ceases to exist, the volume is destroyed.' Is that correct? An ephemeral volume may be destroyed, but a persistent volume should exist beyond the lifetime of a pod by definition.
/triage accepted The description is inconsistent.
/kind bug /priority backlog /language en
/assign
Thanks for fixing this!


Question: <del> --- title: コンテナの概要 content_type: concept weight: 1 --- <!-- overview --> コンテナは、アプリケーションの(コンパイルされた)コードと、実行時に必要な依存関係をパッケージ化するための技術です。実行する各コンテナは再現性があります。依存関係を含めることによる標準化は、どこで実行しても同じ動作が得られることを意味します。 コンテナは、基礎となるホストインフラストラクチャからアプリケーションを切り離します。これにより、さまざまなクラウド環境やOS環境でのデプロイが容易になります。 <!-- body --> ## コンテナイメージ {#container-images} [コンテナイメージ](/docs/concepts/containers/images/)は、アプリケーションを実行するために必要なすべてのものを含んだ、すぐに実行可能なソフトウェアパッケージです。コードとそれが必要とする任意のランタイム、アプリケーションとシステムのライブラリ、および必須の設定のデフォルト値が含まれています。 設計上、コンテナは不変であるため、すでに実行中のコンテナのコードを変更することはできません。コンテナ化されたアプリケーションがあり、変更を加えたい場合は、変更を含む新しいコンテナをビルドし、コンテナを再作成して更新されたイメージから起動する必要があります。 ## コンテナランタイム {#container-runtimes} {{< glossary_definition term_id="container-runtime" length="all" >}} ## {{% heading "whatsnext" %}} * [コンテナイメージ](/docs/concepts/containers/images/)についてお読みください。 * [Pod](/ja/docs/concepts/workloads/pods/)についてお読みください。 </del>

This is a Feature Request What would you like to be should be removed. Why is this needed The reasons are following. In English site, the contents of was to and was deleted. The diff is . () In Japanese site, has been translated. The diff is . () So I think that the page can be removed. Comments /language ja
/triage accepted I can see that the page already contains the contents from . For information: it seems that the page is slightly outdated, compared to the version ( ).
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale
/assign


Question: Note the [PodIndexLabel](/docs/reference/command-line-tools-reference/feature-gates/) feature gate must be enabled for this label to be added to pods. <ins> ### resource.kubernetes.io/pod-claim-name Type: Annotation Example: `resource.kubernetes.io/pod-claim-name: "my-pod-claim"` Used on: ResourceClaim This annotation is assigned to generated ResourceClaims. Its value corresponds to the name of the resource claim in the `.spec` of any Pod(s) for which the ResourceClaim was created. This annotation is an internal implementation detail of [dynamic resource allocation](/docs/concepts/scheduling-eviction/dynamic-resource-allocation/). You should not need to read or modify the value of this annotation. </ins> ### cluster-autoscaler.kubernetes.io/safe-to-evict Type: Annotation

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The annotation is unregistered, but used in Kubernetes code. The says: However, we don't have a mechanism to register annotations that are not also documented. So, it needs registering. Proposed Solution: Register the annotation, by mentioning it in . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig node Required for
/assign
/priority backlog /triage accepted
/lifecycle frozen
/assign
/unassign Unassigning my self as PR is already raised by PR raised for this issue


Question: ``` {{% /tab %}} {{% tab name="Windows" %}} <del> 1. Laden Sie das aktuellste Release {{< param "fullversion" >}} von [diesem link](https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe) herunter. </del> <ins> 1. Laden Sie das aktuellste Release {{< skew currentPatchVersion >}} von [diesem link](https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/windows/amd64/kubectl.exe) herunter. </ins> Oder, sofern Sie `curl` installiert haven, verwenden Sie den folgenden Befehl: ``` <del> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe </del> <ins> curl -LO https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/windows/amd64/kubectl.exe </ins> ``` Informationen zur aktuellen stabilen Version (z. B. für scripting) finden Sie unter [https://dl.k8s.io/release/stable.txt](https://dl.k8s.io/release/stable.txt).

[de] Replace deprecated shortcode Problem: Based on , I have created this issue/task to help update the [de] language documentation. Proposed Solution: Page to Update: In the branch, I found: Results for "fullversion" in "k8s-website" /home/rdlugyhe/kubernetes/k8s-website/content/de/docs/tasks/tools/install-kubectl- 42: Um zum Beispiel Version {{< param "fullversion" }} auf Linux herunterzuladen: 45: curl -LO {{< param "fullversion" }}/bin/linux/amd64/kubectl /home/rdlugyhe/kubernetes/k8s-website/content/de/docs/tasks/tools/install-kubectl- 47: Um zum Beispiel Version {{< param "fullversion" }} auf Intel macOS herunterzuladen: 50: curl -LO "{{< param "fullversion" }}/bin/darwin/amd64/kubectl" 56: curl -LO "{{< param "fullversion" }}/bin/darwin/arm64/kubectl" /home/rdlugyhe/kubernetes/k8s-website/content/de/docs/tasks/tools/install- 200: Um beispielsweise die Version {{< param "fullversion" }} auf macOS herunterzuladen, verwenden Sie 203: curl -LO {{< param "fullversion" }}/bin/darwin/amd64/kubectl 228: Um beispielsweise die Version {{< param "fullversion" }} auf Linux herunterzuladen, verwenden Sie 231: curl -LO {{< param "fullversion" }}/bin/linux/amd64/kubectl 247: Laden Sie das aktuellste Release {{< param "fullversion" }} von diesem linkg


Question: <ins> apiVersion: audit.k8s.io/v1 # 필수사항임. kind: Policy # Request Received 단계의 모든 요청에 대해 감사 이벤트를 생성하지 않음. omitStages: - "RequestReceived" rules: # RequestResponse 수준에서 파드 변경 사항 기록 - level: RequestResponse resources: - group: "" # 리소스 "파드" 가 RBAC 정책과 부합하는 파드의 하위 리소스에 대한 # 요청과 일치하지 않음. resources: ["pods"] # 메타데이터 수준에서 "pods/log", "pods/status"를 기록함. - level: Metadata resources: - group: "" resources: ["pods/log", "pods/status"] # "controller-leader" 라는 컨피그맵에 요청을 기록하지 않음." - level: None resources: - group: "" resources: ["configmaps"] resourceNames: ["controller-leader"] # 엔드포인트 또는 서비스의 "system:kube-proxy"에 의한 감시 요청 기록하지 않음. - level: None users: ["system:kube-proxy"] verbs: ["watch"] resources: - group: "" # 핵심 API 그룹 resources: ["endpoints", "services"] # 인증된 요청을 특정 리소스가 아닌 URL 경로에 기록하지 않음. - level: None userGroups: ["system:authenticated"] nonResourceURLs: - "/api*" # 와일드카드 매칭(wildcard matching). - "/version" # kube-system에 컨피그맵 변경 사항의 요청 본문을 기록함. - level: Request resources: - group: "" # 핵심 API 그룹 resources: ["configmaps"] # 이 정책은 "kube-system" 네임스페이스의 리소스에만 적용됨. # 빈 문자열 "" 은 네임스페이스가 없는 리소스를 선택하는데 사용할 수 있음. namespaces: ["kube-system"] # 메타데이터 수준에서 다른 모든 네임스페이스의 컨피그맵과 시크릿 변경 사항을 기록함. - level: Metadata resources: - group: "" # 핵심 API 그룹 resources: ["secrets", "configmaps"] # 요청 수준에서 코어 및 확장에 있는 다른 모든 리소스를 기록함. - level: Request resources: - group: "" # 핵심 API 그룹 - group: "extensions" # 그룹의 버전을 기재하면 안 된다. # 메타데이터 수준에서 다른 모든 요청을 기록하기 위한 모든 수집 정책. - level: Metadata # 이 정책에 해당하는 감시자와 같은 장기 실행 요청은 # RequestReceived에서 감사 이벤트를 생성하지 않음. omitStages: - "RequestReceived" </ins>

This is a Feature Request Korean Localization for branch. What would you like to be Any localization contributions for Korean. Comments This issue is to notify the schedule of Korean localization to contributors. is the current work branch for Korean localization. Important dates A Korean localization work branch is merged to main branch after we complete around 3~4 weeks job. PR Freeze: 10/03 (PR opened after freeze will be requested to rebase to next work branch) Branch Merge: 10/06 (merge to main branch) 3~4 , main . PR : 10/03 ( PR , PR ) : 10/06 (main , k8s.io ) /language ko /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 : ## In English This is a Feature Request is the current work branch for Korean localization.PR Freeze: 10/03 (PR opened after freeze will be requested to rebase to next work branch) Branch Merge: 10/06 (merge to main branch) PR : 10/03 ( PR , PR ) : 10/06 (main , k8s.io ) /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
Thanks :) /triage accepted
/milestone dev-1.25-ko.1


Question: * [Knitter](https://github.com/ZTE/Knitter/) is a plugin to support multiple network interfaces in a Kubernetes pod. * [Multus](https://github.com/k8snetworkplumbingwg/multus-cni) is a Multi plugin for multiple network support in Kubernetes to support all CNI plugins (e.g. Calico, Cilium, Contiv, Flannel), in addition to SRIOV, DPDK, OVS-DPDK and VPP based workloads in Kubernetes. * [OVN-Kubernetes](https://github.com/ovn-org/ovn-kubernetes/) is a networking provider for Kubernetes based on [OVN (Open Virtual Network)](https://github.com/ovn-org/ovn/), a virtual networking implementation that came out of the Open vSwitch (OVS) project. OVN-Kubernetes provides an overlay based networking implementation for Kubernetes, including an OVS based implementation of load balancing and network policy. <del> * [OVN4NFV-K8S-Plugin](https://github.com/opnfv/ovn4nfv-k8s-plugin) is OVN based CNI controller plugin to provide cloud native based Service function chaining(SFC), Multiple OVN overlay networking, dynamic subnet creation, dynamic creation of virtual networks, VLAN Provider network, Direct provider network and pluggable with other Multi-network plugins, ideal for edge based cloud native workloads in Multi-cluster networking. </del> <ins> * [Nodus](https://github.com/akraino-edge-stack/icn-nodus) is an OVN based CNI controller plugin to provide cloud native based Service function chaining(SFC). </ins> * [NSX-T](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/index.html) Container Plug-in (NCP) provides integration between VMware NSX-T and container orchestrators such as Kubernetes, as well as integration between NSX-T and container-based CaaS/PaaS platforms such as Pivotal Container Service (PKS) and OpenShift. * [Nuage](https://github.com/nuagenetworks/nuage-kubernetes/blob/v5.1.1-1/docs/kubernetes-1-installation.rst) is an SDN platform that provides policy-based networking between Kubernetes Pods and non-Kubernetes environments with visibility and security monitoring. * [Romana](https://github.com/romana) is a Layer 3 networking solution for pod networks that also supports the [NetworkPolicy](/docs/concepts/services-networking/network-policies/) API.

This is a Feature Request Update to either remove all vendor specific information or link to 3rd party documentation. Related: Why is this needed Update the docs to match our . /sig docs /good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Feature Request /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/triage accepted Everyone: If you have questions about how to work on this, or you're not sure whether a piece of text does or doesn't comply with the policy on 3rd party content: go ahead and reply here to ask for that help. SIG Docs reviewers are here to offer you that kind of advice.
Should I remove all links which aren't pointing to a page in For eg. should I remove all links in paragraph and just remain normal texts ?
/assign
I would like work on this but can you help with the information regarding projects that are necessary for kubernetes to function. I get the idea of removing unnecessary links but dont know which project to act on, so i will be looking forward to your reply :)
Here's my attempt to solve this issue. Please guide me if there's something more to do or if I have removed something very important :)
/assign
Hey I'm interested in contributing to this repo, but I have no idea on how to go about it, please can someone help by putting me through?
I'll highlight your request to the documentation special interest group
did you have any specific questions about how to get started?
Hey , I'd be happy to work on this. Please guide me on how to get started here.
/ assign
hey can you please elaborate what exactly is vendor specific information so that i can edit it out of the documentation?


Question: --> 要删除正在运行 Hello World 应用程序的 Deployment，ReplicaSet 和 Pod，请输入以下命令： <del> kubectl delete deployment hello-world </del> <ins> ```shell kubectl delete deployment hello-world ``` </ins> ## {{% heading "whatsnext" %}} <!-- Learn more about [connecting applications with services](/docs/concepts/services-networking/connect-applications-service/). --> <del> 了解更多关于[将应用程序与服务连接](/zh/docs/concepts/services-networking/connect-applications-service/)。 </del> <ins> 进一步了解[将应用程序与服务连接](/zh/docs/concepts/services-networking/connect-applications-service/)。 </ins>

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


Question: [upgrade/kubelet] Now that your control plane is upgraded, please proceed with upgrading your kubelets if you haven't already done so. ``` <del> 1.  Manually upgrade your CNI provider plugin. </del> <ins> -  Manually upgrade your CNI provider plugin. </ins> Your Container Network Interface (CNI) provider may have its own upgrade instructions to follow. Check the [addons](/docs/concepts/cluster-administration/addons/) page to

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: Storage Policy Based Management (SPBM) profile name. <del> ### Beta level {#Beta level} </del> <ins> ### Beta level {#Beta-level} </ins> - **csi** (CSIVolumeSource)

This is a Bug Report The issue is outlined in:
/triage accepted
/kind cleanup
Hi Thanks for opening a PR to fix this issue! /assign


Question: <!-- overview --> This page shows how to configure a Key Management Service (KMS) provider and plugin to enable secret data encryption. ## {{% heading "prerequisites" %}} * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} * Kubernetes version 1.10.0 or later is required

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: There are indentation errors in the yaml files of EncryptionConfiguration. For example in the following yaml, lines after "- secrets" should indent two to the right. ! Proposed Solution: Correct the indentation errors. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Is it right to have in the fixed page?
I checked the preview page, and it's still wrong. I've close my PR.
It should looks like this or "secrets" is the subcontent of the second "resources", and "providers" is with the same level of the second "resources". Although I modified the markdown, the rendered webpage is still wrong.
/priority backlog /language en /help
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /priority backlog /language en /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
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
/remove-lifecycle rotten /assign


Question: spec: containers: - name: nginx <del> image: registry.k8s.io/nginx-slim:0.8 </del> <ins> image: registry.k8s.io/nginx-slim:0.7 </ins> ports: - containerPort: 80 name: web

I wish /docs/getting-started-guides/ listed both Ubuntu guides in the Bare Metal section, noting the networking for each (the listed one uses Flannel, the omitted one (but it is in the navigation panel on the left) uses Calico).
Ubuntu is getting a big rewrite as well.


Question: * [Scheduler Performance Tuning](/docs/concepts/scheduling-eviction/scheduler-perf-tuning/) * [Resource Bin Packing for Extended Resources](/docs/concepts/scheduling-eviction/resource-bin-packing/) * [Pod Scheduling Readiness](/docs/concepts/scheduling-eviction/pod-scheduling-readiness/) <ins> * [Descheduler](https://github.com/kubernetes-sigs/descheduler#descheduler-for-kubernetes) </ins> ## Pod Disruption

This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Change to mention the Why is this needed The Kubernetes project provides the descheduler - as an add-on - but our overview of scheduling makes no mention of it. Comments /language en /kind feature /sig scheduling
/priority backlog /triage accepted /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 : /priority backlog /triage accepted /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign RakshitKumar04
Hii, Can you please elaborate, do I just need to add a heading under Scheduling and connect a link to it? !
Contributors are welcome to propose their own way to include the new concept (the descheduler) into the existing page. if you are not sure about how to the new detail, you could consider looking for a different issue. Maybe there is some other work to do that you'd understand better.
IMO, we can make a new heading for descheduler and add a paragraph(some content) for descheduler under it, and link it to the for more information.
Hi, your thoughts on the above opinion?
The approach I recommend is to open a PR and ask for feedback there. I don't see this as being a complicated change.
Thanks for your opinion.


Question: You can read about [`downwardAPI` volumes](/docs/concepts/storage/volumes/#downwardapi). You can try using the downward API to expose container- or Pod-level information: <del> * as [environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/#the-downward-api) </del> <ins> * as [environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/) </ins> * as [files in `downwardAPI` volume](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/)

This is a Bug Report <!--Required Information--Problem: The link is dead. The content from the section seems moved into top of the document and glossary in . Proposed Solution: remove fragment from the link change link to or Page to Update: /docs/concepts/workloads/pods/downward-api /docs/tasks/inject-data-application/downward-api-volume-expose-pod-information /docs/tasks/job/indexed-parallel-processing-static
/assign
/language en /triage accepted /help We should find existing hyperlinks to and replace those with links to
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 /triage accepted /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/unassign As has already opened a PR
/assign
GitHub didn't allow me to assign the following users: hs0210. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign


Question: <ins> The files in this directory have been imported from other sources. Do not edit them directly, except by replacing them with new versions. For Japanese translation, cncf-code-of-conduct.md is copied from the following CNCF repository: https://github.com/cncf/foundation/blob/master/code-of-conduct-languages/jp.md </ins>

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


Question: nodes. If you do not already have a cluster, you can create one by using [minikube](https://minikube.sigs.k8s.io/docs/tutorials/multi_node/). <ins> ### Understanding etcdctl and etcdutl `etcdctl` and `etcdutl` are command-line tools used to interact with etcd clusters, but they serve different purposes: - `etcdctl`: This is the primary command-line client for interacting with etcd over a network. It is used for day-to-day operations such as managing keys and values, administering the cluster, checking health, and more. - `etcdutl`: This is an administration utility designed to operate directly on etcd data files, including migrating data between etcd versions, defragmenting the database, restoring snapshots, and validating data consistency. For network operations, `etcdctl` should be used. For more information on `etcdutl`, you can refer to the [etcd recovery documentation](https://etcd.io/docs/v3.5/op-guide/recovery/). </ins> <!-- steps --> ## Prerequisites

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: mentions ~(which is deprecated)~ quite a lot before the first mention of . Proposed Solution: Mention early on that there are two tools Where a use of is deprecated in favor of , repeat the equivalent change from Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig etcd
/triage accepted /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 : /triage accepted /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
I'd love to take this one if no one else has started already
/assign
Help is very welcome. Would you like any advice ?
Thank you Any general advice would be greatly appreciated. I have a Minikube multi-node cluster up and running, and I am executing the etcdutl commands within the first container. Hopefully, this setup will suffice for validation. Regarding documentation, I'll follow the provided related issues/documentation, which seem comprehensive enough to get started. However, I'll ensure to ask in the Slack group or on this issue if I encounter any difficulties. As I understand it, only the snapshot commands are deprecated and need updating to their etcdutl counterparts. If there's any inaccuracy in my understanding, please feel free to correct me. Thanks again! :)
I think you're right. General guidance: I'll edit the issue description.

Thank you for the guidance, I have opened a pull request to add a section clarifying the difference between etcdctl and etcdutl. Please feel free to review it and suggest any changes.


Question: <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no"> {{ hugo.Generator }} <del> {{ if eq (getenv "HUGO_ENV") "production" }} <META NAME="ROBOTS" CONTENT="INDEX, FOLLOW"> {{ else }} <META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW"> {{ end }} </del> {{ range .AlternativeOutputFormats -}} <link rel="{{ .Rel }}" type="{{ .MediaType.Type }}" href="{{ .Permalink | safeURL }}"> {{ end -}}

Problem: Google search for "kubernetes secrets v2" returns: ! (notice the URL subdomains) Proposed Solution: I need to do some more research but a few things come to mind: is in and set in the couple repos I checked. is set in . I believe this is for non-prod sites that are running, however I believe even the old released sites are considered "production" That is assuming robots tag is the culprit. What's also strange is that the above robot config is set in but doesn't appear in the search results I also think looking at might help. It's possible this problem has been solved and phased out with future releases. /priority important-soon /triage accepted /help /cc
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : Problem: is in and set in the couple repos I checked. is set in . I believe this is for non-prod sites that are running, however I believe even the old released sites are considered "production" /triage accepted /help /cc </details
https://v1- does look wrong. We could override this file explicitly for the older releases (perhaps just as an interim measure?)
In the v1.19 docs, appears in the page head. That's wrong.
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle rotten
/lifecycle frozen
/retitle Search engines indexing old releases Also, the upcoming release is also being indexed and we don't actually want that. Same cause I think.
Hi and I would like to work on this issue. I can see the proposed solution has already been implemented.

May I know, what new things we need to work on for this issue? Now, Google search for "kubernetes secrets v2" returns: ! /assign
I've proposed a PR to fix this. :crossed_fingers:
/reopen We also need to merge 4 backport PRs.
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
[Backport PRs]
It's fixed. I checked. /close
Closing this issue. <detailsIn response to : It's fixed. I checked. /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: and the API server does verify if the required keys are provided in a Secret configuration. <ins> {{< caution >}} SSH private keys do not establish trusted communication between an SSH client and host server on their own. A secondary means of establishing trust is needed to mitigate "man in the middle" attacks, such as a `known_hosts` file added to a ConfigMap. {{< /caution >}} </ins> ### TLS secrets Kubernetes provides a builtin Secret type `kubernetes.io/tls` for to storing

This is a Feature Request What would you like to be Add a caution note to the Concepts document article for Secrets, warning that SSH private keys do not establish fully trusted communication between clients and host servers. Why is this needed SSH key pairs provide a means of establishing authenticated communication between two parties, but not trusted communication between two parties. Trust can only be established via a secondary means, like a file. Without establishing trust, applications which utilize SSH keys by themselves for authentication are susceptible to "man in the middle" attacks. Comments This item was discussed during the first SIG Docs Security subproject meeting.
/sig security /triage accepted
/priority important-longterm Thanks