Question: title: Kubernetes Components content_type: concept description: > <del> A Kubernetes cluster consists of the components that represent the control plane and a set of machines called nodes. </del> <ins> A Kubernetes cluster consists of the components that are a part of the control plane and a set of machines called nodes. </ins> weight: 20 card: name: concepts

How about "consists of a control plane and a set of machines called nodes"? Learning k8s is hard enough without obfuscating verbosity. For non-managers it's best to say it as it is ;-). Apart from that: "consists of the components that represent the control plane" suggests that there are components that represent a control pane, not are a control pane, and a set of nodes. So where is the control pane? I'm probably a big introvert and a nerd, but this confuses me to the point where I actually have to think about what this means... "In what way do the components represent the control pane? Where is the control pane itself? Am I not getting this? Probably not. It probably means these components are the control pane. Stupid me, of course that's what it means." So, while I could have understood what was meant in a split second, it takes me a couple of seconds of contemplation and a few minutes to suggest an improvement.
We could update the source of to make that change. Nice suggestion. is automatically generated. For a bigger improvement, we could move to and configure a redirect. /language en
/triage accepted /help If someone is planning to move this forward: move to configure a redirect from the old URL to the new URL (see ) make sure that the updated ends how you'd expect. It's likely that setting in the will 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 move to configure a redirect from the old URL to the new URL (see ) make sure that the updated ends how you'd expect. It's likely that setting in the will 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
Feel free to reply with questions.
I would love to take this /assign
/good-first-issue For the first-timers, look
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue For the first-timers, look 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: with your new arguments. {{< note >}} <del> The `command` field corresponds to `entrypoint` in some container runtimes. Refer to the [Notes](#notes) below. </del> <ins> The `command` field corresponds to `entrypoint` in some container runtimes. </ins> {{< /note >}} In this exercise, you create a Pod that runs one container. The configuration

URL: File: /tasks/inject-data-application/define-command-argument- Remove the entire Notes section. Clean up the page so that there's no mention of a specific runtime. /sig docs /language en
I would remove the entire section. Docker is far from the only alternative to Kubernetes. If someone wanted to, we could accept a blog article that compares Docker, Kubernetes, Nomad, etc for how you specify these things. But it's fine if that blog is never submitted. /triage accepted
to me this is more about comparing Docker Swarm to Kubernetes. I think it's a good bit of tidying but I'm not sure it's needed for the dockershim removal work.


Question: <!-- overview --> ガベージコレクションは、Kubernetesがクラスターリソースをクリーンアップするために使用するさまざまなメカニズムの総称です。これにより、次のようなリソースのクリーンアップが可能になります: <del> * [失敗したPod](/ja/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection) </del> <ins> * [終了したPod](/ja/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection) </ins> * [完了したJob](/ja/docs/concepts/workloads/controllers/ttlafterfinished/) * [owner referenceのないオブジェクト](#owners-dependents) * [未使用のコンテナとコンテナイメージ](#containers-images)

This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/architecture/garbage- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/architecture/garbage- is outdated. A link text to this page from other pages have already been fixed. The current page is still "" and it should be fixed "". Comments /language ja /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: Generates keys and certificate signing requests (CSRs) for all the certificates required to run the control plane. This command also generates partial kubeconfig files with private key data in the  "users > user > client-key-data" field, and for each kubeconfig file an accompanying ".csr" file is created. <del> This command is designed for use in [Kubeadm External CA Mode](https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/#external-ca-mode). It generates CSRs which you can then submit to your external certificate authority for signing. </del> <ins> This command is designed for use in [Kubeadm External CA Mode](/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/#external-ca-mode). It generates CSRs which you can then submit to your external certificate authority for signing. </ins> The PEM encoded signed certificates should then be saved alongside the key files, using ".crt" as the file extension, or in the case of kubeconfig files, the PEM encoded signed certificate should be base64 encoded and added to the kubeconfig file in the "users > user > client-certificate-data" field.

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: * Verbs: `update`, group: `certificates.k8s.io`, resource: `certificatesigningrequests/status` * Verbs: `sign`, group: `certificates.k8s.io`, resource: `signers`, resourceName: `<signerNameDomain>/<signerNamePath>` or `<signerNameDomain>/*` <del> ```yaml apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: csr-signer rules: - apiGroups: - certificates.k8s.io resources: - certificatesigningrequests verbs: - get - list - watch - apiGroups: - certificates.k8s.io resources: - certificatesigningrequests/status verbs: - update - apiGroups: - certificates.k8s.io resources: - signers resourceName: - example.com/my-signer-name # example.com/* can be used to authorize for all signers in the 'example.com' domain verbs: - sign ``` </del> <ins> {{< codenew file="access/certificate-signing-request/clusterrole-sign.yaml" >}} </ins> ## Normal User

/language zh
/reopen This was incorrectly
Reopened this issue. <detailsIn response to : /reopen This was incorrectly Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign


Question: <!-- overview --> <del> This page explains how to enable a package repository for a new Kubernetes minor release </del> <ins> This page explains how to enable a package repository for the desired Kubernetes minor release upon upgrading a cluster. This is only needed </ins> for users of the community-owned package repositories hosted at `pkgs.k8s.io`. <del> Unlike the legacy package repositories, the community-owned package repositories are structured in a way that there's a dedicated package repository for each Kubernetes minor version. </del> <ins> Unlike the legacy package repositories, the community-owned package repositories are structured in a way that there's a dedicated package repository for each Kubernetes minor version. {{< note >}} This guide only covers a part of the Kubernetes upgrade process. Please see the [upgrade guide](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) for more information about upgrading Kubernetes clusters. {{</ note >}} {{< note >}} This step is only needed upon upgrading a cluster to another **minor** release. If you're upgrading to another patch release within the same minor release (e.g. v{{< skew currentVersion >}}.5 to v{{< skew currentVersion >}}.7), you don't need to follow this guide. However, if you're still using the legacy package repositories, you'll need to migrate to the new community-owned package repositories before upgrading (see the next section for more details on how to do this). {{</ note >}} </ins> ## {{% heading "prerequisites" %}}

The pull requests in question are essentially backports of documentation that already exists on the branch. We prefer to first resolve these issues in the branch and then proceed with backporting. Considering that the most recent releases have yet to be integrated into our legacy repositories, it's crucial that we expedite updating our documentation and instructions. We are going to merge these PRs and carry out any further backports as needed once we reach a consensus on the changes.
/sig docs /language en
/triage accepted
/priority important-soon I'd accept important-longterm instead.
/lifecycle frozen
All backport PRs merged. /close
Closing this issue. <detailsIn response to : All backport PRs merged. 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
This is about fixing remaining comments from the backport PRs, which is yet TBD /reopen
Reopened this issue. <detailsIn response to : This is about fixing remaining comments from the backport PRs, which is yet TBD /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
We still need to backport /reopen
Reopened this issue. <detailsIn response to : We still need to backport /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
Backports created:
Backports are merged /close
Closing this issue. <detailsIn response to : Backports are merged /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:
String	API Object

"pods"	Pod

"services	Service

"services"	Service

"replicationcontrollers"	ReplicationController

"resourcequotas"	ResourceQuota

"secrets"	Secret

This is a Bug Report Problem: missing double quote (") after the word services in the last table Proposed Solution: Add the missing double quote (") Page to Update:


Question: このツールの名前は、`kubectl` です。 <del> `kubectl`コマンドラインツールを使うと、Kubernetesクラスターを制御できます。環境設定のために、`kubectl`は、`$HOME/.kube`ディレクトリにある`config`という名前のファイルを探します。他の[kubeconfig](/ja/docs/concepts/configuration/organize-cluster-access-kubeconfig/)ファイルは、`KUBECONFIG`環境変数を設定するか、[`--kubeconfig`](/docs/concepts/configuration/organize-cluster-access-kubeconfig/)フラグを設定することで指定できます。 </del> <ins> `kubectl`コマンドラインツールを使うと、Kubernetesクラスターを制御できます。環境設定のために、`kubectl`は、`$HOME/.kube`ディレクトリにある`config`という名前のファイルを探します。他の[kubeconfig](/ja/docs/concepts/configuration/organize-cluster-access-kubeconfig/)ファイルは、`KUBECONFIG`環境変数を設定するか、[`--kubeconfig`](/ja/docs/concepts/configuration/organize-cluster-access-kubeconfig/)フラグを設定することで指定できます。 </ins> この概要では、`kubectl`の構文を扱い、コマンド操作を説明し、一般的な例を示します。サポートされているすべてのフラグやサブコマンドを含め、各コマンドの詳細については、[kubectl](/docs/reference/generated/kubectl/kubectl-commands/)リファレンスドキュメントを参照してください。 <del> インストール方法については、[kubectlのインストールおよびセットアップ](/ja/docs/tasks/tools/install-kubectl/)をご覧ください。クイックガイドは、[cheat sheet](/docs/reference/kubectl/cheatsheet/) をご覧ください。`docker`コマンドラインツールに慣れている方は、[`kubectl` for Docker Users](/docs/reference/kubectl/docker-cli-to-kubectl/) でKubernetesの同等のコマンドを説明しています。 </del> <ins> インストール方法については、[kubectlのインストールおよびセットアップ](/ja/docs/tasks/tools/install-kubectl/)をご覧ください。クイックガイドは、[チートシート](/ja/docs/reference/kubectl/cheatsheet/)をご覧ください。`docker`コマンドラインツールに慣れている方は、[`kubectl` for Docker Users](/docs/reference/kubectl/docker-cli-to-kubectl/)でKubernetesの同等のコマンドを説明しています。 </ins> <!-- body -->

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: In the Japanese website, two hyperlinks ( --kubeconfig and cheat sheet ) on the Command line tool (kubectl) page are not getting redirected to the Japanese version of the respective pages. Proposed Solution: The Japanese version of these two pages is already available, so I will simply make these two hyperlinks redirect to the respective Japanese page. Page to Update: https://deploy-preview---kubernetes-io-main- <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--! Comments I want to work on this issue. /assign
/language ja
/triage accepted Thanks for pointing this out You can start solving this issue by assigning yourself. However, it is always recommended to pick those issues of localization that is native to you.
Ok, thank you I'll keep this in my mind from now on .


Question:
| Network Driver | Description | Container Packet Modifications | Network Plugins | Network Plugin Characteristics | | -------------- | ----------- | ------------------------------ | --------------- | ------------------------------ |  | L2bridge       | Containers are attached to an external vSwitch. Containers are attached to the underlay network, although the physical network doesn't need to learn the container MACs because they are rewritten on ingress/egress. | MAC is rewritten to host MAC, IP may be rewritten to host IP using HNS OutboundNAT policy. | [win-bridge](https://github.com/containernetworking/plugins/tree/master/plugins/main/windows/win-bridge), [Azure-CNI](https://github.com/Azure/azure-container-networking/blob/master/docs/cni.md), Flannel host-gateway uses win-bridge | win-bridge uses L2bridge network mode, connects containers to the underlay of hosts, offering best performance. Requires user-defined routes (UDR) for inter-node connectivity. |   | L2bridge       | Containers are attached to an external vSwitch. Containers are attached to the underlay network, although the physical network doesn't need to learn the container MACs because they are rewritten on ingress/egress. | MAC is rewritten to host MAC, IP may be rewritten to host IP using HNS OutboundNAT policy. | [win-bridge](https://www.cni.dev/plugins/current/main/win-bridge/), [Azure-CNI](https://github.com/Azure/azure-container-networking/blob/master/docs/cni.md), [Flannel host-gateway](https://github.com/flannel-io/flannel/blob/master/Documentation/backends.md#host-gw) uses win-bridge | win-bridge uses L2bridge network mode, connects containers to the underlay of hosts, offering best performance. Requires user-defined routes (UDR) for inter-node connectivity. |  | L2Tunnel | This is a special case of l2bridge, but only used on Azure. All packets are sent to the virtualization host where SDN policy is applied. | MAC rewritten, IP visible on the underlay network | [Azure-CNI](https://github.com/Azure/azure-container-networking/blob/master/docs/cni.md) | Azure-CNI allows integration of containers with Azure vNET, and allows them to leverage the set of capabilities that [Azure Virtual Network provides](https://azure.microsoft.com/en-us/services/virtual-network/). For example, securely connect to Azure services or use Azure NSGs. See [azure-cni for some examples](https://docs.microsoft.com/azure/aks/concepts-network#azure-cni-advanced-networking) |  | Overlay | Containers are given a vNIC connected to an external vSwitch. Each overlay network gets its own IP subnet, defined by a custom IP prefix.The overlay network driver uses VXLAN encapsulation. | Encapsulated with an outer header. | [win-overlay](https://github.com/containernetworking/plugins/tree/master/plugins/main/windows/win-overlay), Flannel VXLAN (uses win-overlay) | win-overlay should be used when virtual container networks are desired to be isolated from underlay of hosts (e.g. for security reasons). Allows for IPs to be re-used for different overlay networks (which have different VNID tags)  if you are restricted on IPs in your datacenter.  This option requires [KB4489899](https://support.microsoft.com/help/4489899) on Windows Server 2019. |   | Overlay | Containers are given a vNIC connected to an external vSwitch. Each overlay network gets its own IP subnet, defined by a custom IP prefix.The overlay network driver uses VXLAN encapsulation. | Encapsulated with an outer header. | [win-overlay](https://www.cni.dev/plugins/current/main/win-overlay/), [Flannel VXLAN](https://github.com/flannel-io/flannel/blob/master/Documentation/backends.md#vxlan) (uses win-overlay) | win-overlay should be used when virtual container networks are desired to be isolated from underlay of hosts (e.g. for security reasons). Allows for IPs to be re-used for different overlay networks (which have different VNID tags)  if you are restricted on IPs in your datacenter.  This option requires [KB4489899](https://support.microsoft.com/help/4489899) on Windows Server 2019. |  | Transparent (special use case for [ovn-kubernetes](https://github.com/openvswitch/ovn-kubernetes)) | Requires an external vSwitch. Containers are attached to an external vSwitch which enables intra-pod communication via logical networks (logical switches and routers). | Packet is encapsulated either via [GENEVE](https://datatracker.ietf.org/doc/draft-gross-geneve/) or [STT](https://datatracker.ietf.org/doc/draft-davie-stt/) tunneling to reach pods which are not on the same host.
 Packets are forwarded or dropped via the tunnel metadata information supplied by the ovn network controller.
 NAT is done for north-south communication. | [ovn-kubernetes](https://github.com/openvswitch/ovn-kubernetes) | [Deploy via ansible](https://github.com/openvswitch/ovn-kubernetes/tree/master/contrib). Distributed ACLs can be applied via Kubernetes policies. IPAM support. Load-balancing can be achieved without kube-proxy. NATing is done without using iptables/netsh. | | NAT (*not used in Kubernetes*) | Containers are given a vNIC connected to an internal vSwitch. DNS/DHCP is provided using an internal component called [WinNAT](https://techcommunity.microsoft.com/t5/virtualization/windows-nat-winnat-capabilities-and-limitations/ba-p/382303) | MAC and IP is rewritten to host MAC/IP. | [nat](https://github.com/Microsoft/windows-container-networking/tree/master/plugins/nat) | Included here for completeness |

<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: In doc under : 1) redirects to which shows that the documentation has been moved. 2) Similarly, redirects to which again shows that the documentation is moved. 3) No hyperlink for 4) No hyperlink for Proposed Solution: 1) For replace with 2) For replace with 3) For add this hyperlink: 4) For add this hyperlink: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en /sig network /sig docs /assign
/triage accepted


Question: {{ define "main" }} <ins> {{ partial "handle-version-switch-404.html" . }} </ins> <div class="container-404"> <h4> Perhaps you were looking for:

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: Current page is lost when switching between documentation versions. Steps to reproduce to some page in the docs, for example the version selector at the top of the page to change to 1.17. that it it sends me to the instead of showing me the . Proposed Solution: Keep the relative path when switching versions Page to Update: All <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: Am I wrong that it used to preserve the page you are on when switching versions? I feel like it used to do that, but I'm not 100% sure.
Yes, at some point the site kept the same page when switching between versions.
/kind bug /priority backlog (I think this is a low-priority-backlog sort of issue; it's a frustration, but we have other places where it makes sense to focus effort first).
/area web-development


Question: `replace`        | `kubectl replace -f FILENAME` | Replace a resource from a file or stdin. `rollout`    | `kubectl rollout SUBCOMMAND [options]` | Manage the rollout of a resource. Valid resource types include: deployments, daemonsets and statefulsets. `run`        | kubectl run NAME --image=image [--env="key=value"] [--port=port] [--dry-run=server|client|none] [--overrides=inline-json] [flags] | Run a specified image on the cluster.  `scale`        | kubectl scale (-f FILENAME | TYPE NAME | TYPE/NAME) --replicas=COUNT [--resource-version=version] [--current-replicas=count] [flags] | Update the size of the specified replication controller. `set`    | `kubectl set SUBCOMMAND [options]` | Configure application resources. `taint`    | `kubectl taint NODE NAME KEY_1=VAL_1:TAINT_EFFECT_1 ... KEY_N=VAL_N:TAINT_EFFECT_N [options]` | Update the taints on one or more nodes. `top`    | `kubectl top [flags] [options]` | Display Resource (CPU/Memory/Storage) usage. `uncordon`    | `kubectl uncordon NODE [options]` | Mark node as schedulable. `version`        | `kubectl version [--client] [flags]` | Display the Kubernetes version running on the client and server. `wait`    | kubectl wait ([-f FILENAME] | resource.group/resource.name | resource.group [(-l label | --all)]) [--for=delete|--for condition=available] [options] | Experimental: Wait for a specific condition on one or many resources.  -->  操作             | 语法      |       描述 -------------------- | -------------------- | -------------------- `alpha`    | `kubectl alpha SUBCOMMAND [flags]` | 列出与 alpha 特性对应的可用命令，这些特性在 Kubernetes 集群中默认情况下是不启用的。 `annotate`    | kubectl annotate (-f FILENAME | TYPE NAME | TYPE/NAME) KEY_1=VAL_1 ... KEY_N=VAL_N [--overwrite] [--all] [--resource-version=version] [flags] | 添加或更新一个或多个资源的注解。 `api-resources`    | `kubectl api-resources [flags]` | 列出可用的 API 资源。 `api-versions`    | `kubectl api-versions [flags]` | 列出可用的 API 版本。 `apply`            | `kubectl apply -f FILENAME [flags]`| 从文件或 stdin 对资源应用配置更改。 `attach`        | `kubectl attach POD -c CONTAINER [-i] [-t] [flags]` | 挂接到正在运行的容器，查看输出流或与容器（stdin）交互。 `auth`    | `kubectl auth [flags] [options]` | 检查授权。 `autoscale`    | kubectl autoscale (-f FILENAME | TYPE NAME | TYPE/NAME) [--min=MINPODS] --max=MAXPODS [--cpu-percent=CPU] [flags] | 自动扩缩由副本控制器管理的一组 pod。 `certificate`    | `kubectl certificate SUBCOMMAND [options]` | 修改证书资源。 `cluster-info`    | `kubectl cluster-info [flags]` | 显示有关集群中主服务器和服务的端口信息。 `completion`    | `kubectl completion SHELL [options]` | 为指定的 Shell（Bash 或 Zsh）输出 Shell 补齐代码。 `config`        | `kubectl config SUBCOMMAND [flags]` | 修改 kubeconfig 文件。有关详细信息，请参阅各个子命令。 `convert`    | `kubectl convert -f FILENAME [options]` | 在不同的 API 版本之间转换配置文件。配置文件可以是 YAML 或 JSON 格式。注意 - 需要安装 `kubectl-convert` 插件。 `cordon`    | `kubectl cordon NODE [options]` | 将节点标记为不可调度。 `cp`    | `kubectl cp <file-spec-src> <file-spec-dest> [options]` | 从容器复制文件、目录或将文件、目录复制到容器。 `create`        | `kubectl create -f FILENAME [flags]` | 从文件或 stdin 创建一个或多个资源。 `delete`        |  kubectl delete (-f FILENAME | TYPE [NAME | /NAME | -l label | --all]) [flags] |  基于文件、标准输入或通过指定标签选择器、名称、资源选择器或资源本身，删除资源。 `describe`    | kubectl describe (-f FILENAME | TYPE [NAME_PREFIX | /NAME | -l label]) [flags] | 显示一个或多个资源的详细状态。 `diff`        | `kubectl diff -f FILENAME [flags]`| 在当前起作用的配置和文件或标准输之间作对比 (**BETA**) `drain`    | `kubectl drain NODE [options]` | 腾空节点以准备维护。 `edit`        | kubectl edit (-f FILENAME | TYPE NAME | TYPE/NAME) [flags] | 使用默认编辑器编辑和更新服务器上一个或多个资源的定义。 `exec`        | `kubectl exec POD [-c CONTAINER] [-i] [-t] [flags] [-- COMMAND [args...]]` | 对 Pod 中的容器执行命令。 `explain`    | `kubectl explain  [--recursive=false] [flags]` | 获取多种资源的文档。例如 Pod、Node、Service 等。 `expose`        | kubectl expose (-f FILENAME | TYPE NAME | TYPE/NAME) [--port=port] [--protocol=TCP|UDP] [--target-port=number-or-name] [--name=name] [--external-ip=external-ip-of-service] [--type=type] [flags] | 将副本控制器、服务或 Pod 作为新的 Kubernetes 服务暴露。 `get`        | kubectl get (-f FILENAME | TYPE [NAME | /NAME | -l label]) [--watch] [--sort-by=FIELD] [[-o | --output]=OUTPUT_FORMAT] [flags] | 列出一个或多个资源。 `kustomize`    | kubectl kustomize <dir> [flags] [options]` </code> | 列出从 kustomization.yaml 文件中的指令生成的一组 API 资源。参数必须是包含文件的目录的路径，或者是 git 存储库 URL，其路径后缀相对于存储库根目录指定了相同的路径。 </ins> `label`        | <code>kubectl label (-f FILENAME | TYPE NAME | TYPE/NAME) KEY_1=VAL_1 ... KEY_N=VAL_N [--overwrite] [--all] [--resource-version=version] [flags]</code> | 添加或更新一个或多个资源的标签。 `logs`        | `kubectl logs POD [-c CONTAINER] [--follow] [flags]` |  打印 Pod 中容器的日志。 `options`    | `kubectl options` | 全局命令行选项列表，这些选项适用于所有命令。

web
/retitle [zh-cn] Fix table formatting errors on the kubectl page
/triage accepted


Question: baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-$basearch enabled=1 gpgcheck=1 <del> gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg </del> <ins> gpgkey=https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg </ins> exclude=kubelet kubeadm kubectl EOF

I will submit the PR as well Problem: Steps to reproduce this will result in the following error: Proposed Solution: Remove the 1st key which was used for doing repogpgkey check however since the repogpgcheck option got removed so this 1st key is no longer used/needed. So this would be the fix: Page to Update:
/assign
/triage accepted


Question: --> Kubernetes 控制面会为所有名字空间设置一个不可变更的 {{< glossary_tooltip text="标签" term_id="label" >}} <del> `kubernetes.io/metadata.name`，只要 `NamespaceDefaultLabelName` 这一 [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/) 被启用。标签的值是名字空间的名称。 </del> <ins> `kubernetes.io/metadata.name`，只要 `NamespaceDefaultLabelName` 这一[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)被启用。 标签的值是名字空间的名称。 </ins> ## {{% heading "whatsnext" %}}

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


Question: requests: storage: 20Gi --- <del> apiVersion: apps/v1beta2 # for versions before 1.8.0 use apps/v1beta1 </del> <ins> apiVersion: apps/v1 # for versions before 1.9.0 use apps/v1beta2 </ins> kind: Deployment metadata: name: wordpress

<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x ] Bug Report Problem: Deployment yaml file: mysql- api version does not fit 1.9 version: apiVersion: apps/v1beta2 # for versions before 1.8.0 use apps/v1beta1 kind: Deployment Proposed Solution: change apiVersion to: apps/v1 Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: 9 ! <!--Additional Information:--


Question:
 --- title: 测试页面（中文版） main_menu: false ---   本页面服务于两个目的： - 展示 Kubernetes 中文版文档中应如何使用 Markdown - 提供一个测试用文档，用来测试可能影响所有文档的 HTML、CSS 和模板变更  ## 标题级别 上面的标题是 H2 级别。页面标题（Title）会渲染为 H1。以下各节分别展示 H3-H6 的渲染结果。 ### H3 此处为 H3 节内容。 #### H4 此处为 H4 节内容。 ##### H5 此处为 H5 节内容。 ###### H6 此处为 H6 节内容。  ## 内联元素（Inline elements） 内联元素显示在段落文字、列表条目、提醒信息或者块级别元素之内。 Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. ### 内联文本风格  - **粗体字** - _斜体字_ - ***粗斜体字*** - ~~删除线~~ - 下划线 - _带下划线的斜体_ - ***带下划线的粗斜体*** - `monospace text`  <- 等宽字体 - **`monospace bold`**    <- 粗等宽字体 ## 列表  Markdown 在如何处理列表方面没有严格的规则。在我们从 Jekyll 迁移到 Hugo 时， 我们遇到了一些问题。为了处理这些问题，请注意以下几点： - 确保你将子列表的条目缩进**四个空格**而不是你可能熟悉的两个空格。 有一点是不那么直观的，你需要将列表中的块级别内容多缩进四个空格。 - 要结束一个列表并开始一个新的列表，你需要在两个列表之间添加加一个 HTML 注释块， 并将其置于独立的一行，左边顶边对齐。否则前一个列表不会结束，无论你在它与 第二个列表之间放多少个空行。  ### 项目符号列表 - 此为列表条目 * 此为另一列表条目，位于同一列表中 - 你可以将 `-` 和 `*` 混合使用 - 要开始子列表，缩进两个 TAB （四个空格）。**Jekyll 和 Markdown 在这点上有所不同**。 - 这是另一个子子条目。进一步多缩进两个空格。 - 另一个子条目   - 这是一个新的列表。使用 Hugo 时，你需要用一行 HTML 注释将两个紧挨着的列表分开。 **这里的 HTML 注释需要按左侧顶边对齐。** - 项目符号列表可以中包含文字段落或块元素。 段落内容与第一行文字左侧对齐。 **此段文字和下面的代码段都与前一行中的“项”字对齐。** ```bash ls -l ``` - 在块级内容之后还可以有子列表内容。  - 项目符号列表条目中还可以包含编号列表。 1.  编号子列表条目一 1.  编号子列表条目二 - 项目符号列表条目中包含编号列表的另一种形式（推荐形式）。让子列表的编号数字 与项目符号列表文字左对齐。 1. 编号子列表条目一，左侧编号与前一行的“项”字左对齐。 1.  编号子列表条目二，条目文字与数字之间多了一个空格。  ### 编号列表 1.  此为列表条目 1.  此为列表中的第二个条目。在 Markdown 源码中所给的编号数字与最终输出的数字 可能不同。建议在紧凑列表中编号都使用 1。如果条目之间有其他内容（比如注释 掉的英文）存在，则需要显式给出编号。 2.  {{<note>}} 对于单个数字的编号列表，在句点（`.`）后面加两个空格。这样有助于将列表的 内容更好地对齐。 {{</note>}}   1.  这是一个新的列表。 使用 Hugo 时，你需要用 HTML 注释将两个紧挨着的列表分开。 **HTML 注释需要按左边顶边对齐。** 2.  编号列表条目中也可以包含额外的段落或者块元素。 后续段落应该按编号列表文字的第一行左侧对齐。 **此段落及下面的代码段都与本条目中的第一个字“编”对齐。** ```bash ls -l ``` - 编号列表条目中可以在块级内容之后有子列表。子列表的符号项要与上层列表条目 文字左侧对齐。 ### 中文译文的编号列表格式 1  1. 译文条目一  2. 译文条目二，由于前述原因，条目 2 与 1 之间存在注释行，如果此条目不显式给出 起始编号，会被 Hugo 当做两个独立的列表。 ### 中文译文的编号列表格式 2  1. 译文条目一  中文译文段落。  带注释的代码段（**注意以上英文注释 `<!--` 和 `-->` 的缩进空格数**）。 ```shell # 列举服务 kubectl get svc ```  2. 译文条目二，由于前述原因，条目 2 与 1 之间存在注释行，如果此条目不显式给出 起始编号，会被 Hugo 当做两个独立的列表。  ### 标签列表 标签列表可以用来有条件地显式内容，例如，当有多种选项可供选择时，每个选项 可能需要完全不同的指令或者上下文。  {{< tabs name="tab_lists_example" >}} {{% tab name="请选择..." %}} 请选择一个选项。 {{% /tab %}}  {{% tab name="在标签页中格式化列表" %}}  标签页中也可以包含嵌套的排版风格，其中的英文注释处理也同正文中 的处理基本一致。 1. 编号列表 1. （或者没有编号的） 1. 列表 ```bash echo '标签页里面也可以有代码段!' ``` {{% /tab %}}  {{% tab name="嵌套的子标题" %}}  ### 在标签页中的子标题 标签页中也可以包含嵌套的子标题。  {{< warning >}} 标签页中的子标题不会在目录中出现。 {{< /warning >}} {{% /tab %}} {{< /tabs >}}  ### 检查项列表  （Checklists） 检查项列表本质上也是一种项目符号列表，只是这里的项目符号部分被 CSS 压制了。 - [ ] 此为第一个检查项 - [x] 此为被选中的检查项  ## 代码段 你可以用两种方式来创建代码块。一种方式是将在代码块之前和之后分别加上包含三个 反引号的独立行。**反引号应该仅用于代码段。** 用这种方式标记代码段时，你还可以指定所包含的代码的编程语言，从而启用语法加亮。 这种方式也比使用空格缩进的方式可预测性更好。  ``` 这是用反引号创建的代码段 ```  反引号标记代码段的方式有以下优点： - 这种方式几乎总是能正确工作 - 在查看源代码时，内容相对紧凑 - 允许你指定代码块的编程语言，以便启用语法加亮 - 代码段的结束位置有明确标记。有时候，采用缩进空格的方式会使得一些对空格 很敏感的语言（如 Python、YAML）很难处理。  要为代码段指定编程语言，可以在第一组反引号之后加上编程语言名称： ```bash ls -l ```  Kubernetes 文档中代码块常用语言包括： - `bash` / `shell` （二者几乎完全相同） - `go` - `json` - `yaml` - `xml` - `none` （禁止对代码块执行语法加亮）  ### 包含 Hugo 短代码的代码块 如果要像上面的例子一样显示 Hugo 短代码（Shortcode），不希望 Hugo 将其当做短代码来处理， 可以在 `<` 和 `>` 之间使用 C 语言风格的注释。 下面的示例展示如何实现这点（查看本页的 Markdown 源码）： ```none {{</* codenew file="pods/storage/gce-volume.yaml" */>}} ```  ## 链接 要格式化链接，将链接显示文本放在方括号中，后接用圆括号括起来的链接目标。 [指向 Kubernetes.io 的连接](https://kubernetes.io/) 或 [到 Kubernetes.io 的相对链接](/)。 你也可以使用 HTML，但这种方式不是推荐的方式。 到 Kubernetes.io 的链接。 ### 中文链接 中文版本文档中的链接要注意以下两点： - 指向 Kubernetes 文档的站内链接，需要在英文链接之前添加前缀 `/zh`。 例如，原链接目标为 `/docs/foo/bar` 时，译文中的链接目标应为 `/zh/docs/foo/bar`。例如： - 英文版本链接 [Kubernetes Components](/docs/concepts/overview/components/) - 对应中文链接 [Kubernetes 组件](/zh/docs/concepts/overview/components/) - 英文页面子标题会生成对应锚点（Anchor），例如子标题 `## Using object` 会生成 对应标签 `#using-objects`。在翻译为中文之后，对应锚点可能会失效。对此，有 两种方法处理。假定译文中存在以下子标题： ``` <!-- ## Clean up You can do this ... --> ## 清理现场 你可以这样 ... ``` 并且在本页或其他页面有指向 `#clean-up` 的链接如下： ``` ..., please refer to the [clean up](#clean-up) section. ``` 第一种处理方法是将链接改为中文锚点，即将引用该子标题的文字全部改为中文锚点。 例如： ``` ..., 请参考[清理工作](#清理现场)一节。 ``` 第二种方式（也是推荐的方式）是将原来可能生成的锚点（尽管在英文原文中未明确 给出）显式标记在译文的子标题上。 ``` <!-- ## Clean up You can do this ... --> ## 清理现场  {#clean-up} 你可以这样 ... ``` 之所以优选第二种方式是因为可以避免文档站点中其他引用此子标题的链接失效。  ## 图片 要显示图片，可以使用与链接类似的语法（`[links](#links)`），不过要在整个链接 之前添加一个感叹号（`!`）。方括号中给出的是图片的替代文本。 请坚持为图片设定替代文本，这样使用屏幕阅读器的人也能够了解图片中包含的是什么。 ![pencil icon](/images/pencil.png)  要设置扩展的属性，例如 width、title、caption 等等，可以使用 figure 短代码，而不是使用 HTML 的 `<img>` 标签。 此外，如果你需要让图片本身变成超链接，可以使用短代码的 `link` 属性，而不是 将整个图片放到 Markdown 的链接语法之内。下面是一个例子：  {{
}}  即使你不想使用 figure 短代码，图片也可以展示为链接。这里，铅笔图标指向 Kubernetes 网站。外层的方括号将整个 image 标签封装起来，链接目标在 末尾的圆括号之间给出。 [![pencil icon](/images/pencil.png)](https://kubernetes.io) 你也可以使用 HTML 来嵌入图片，不过这种方式是不推荐的。   ## 表格 简单的表格可能每行只有一个独立的数据行，各个列之间用 `|` 隔开。 表格的标题行与表格内容之间用独立的一行隔开，在这一行中每个单元格的内容 只有 `-` 字符，且至少三个。出于方便维护考虑，请尝试将各个单元格间的 分割线对齐，尽管这样意味着你需要多输入几个空格。  | 标题单元格 1   | 标题单元格 2   | |----------------|----------------| | 内容单元格 1   | 内容单元格 2   |  标题行是可选的。所有用 `|` 隔开的内容都会被渲染成表格。  Markdown 表格在处理块级元素方面还很笨拙。例如在单元格中嵌入列表条目、代码段、 或者在其中划分多个段落方面的能力都比较差。对于复杂的或者很宽的表格，可以使用 HTML。

  标题单元格 1	  标题单元格 2

  内容单元格 1	  内容单元格 2

  ## 使用 Mermaid 来可视化 你可以使用 [Mermaid JS](https://mermaidjs.github.io) 来进行可视化展示。 Mermaid JS 版本在 [/layouts/partials/head.html](https://github.com/kubernetes/website/blob/master/layouts/partials/head.html) 中设置。  ``` {{</* mermaid */>}} graph TD; 甲-->乙; 甲-->丙; 乙-->丁; 丙-->丁; {{</*/ mermaid */>}} ```  会产生：  {{< mermaid >}} graph TD; 甲-->乙; 甲-->丙; 乙-->丁; 丙-->丁; {{</ mermaid >}}  ``` {{</* mermaid */>}} sequenceDiagram 张三 ->> 李四: 李四，锄禾日当午？ 李四-->>王五: 王五，锄禾日当午？ 李四--x 张三: 汗滴禾下土！ 李四-x 王五: 汗滴禾下土！ Note right of 王五: 李四想啊想啊<br/>一直想啊想，太阳<br/>都下山了，他还没想出来<br/>，文本框都放不下了。 李四-->张三: 跑去问王五... 张三->王五: 好吧... 王五，白日依山尽？ {{</*/ mermaid */>}} ```  产生：  {{< mermaid >}} sequenceDiagram 张三 ->> 李四: 李四，锄禾日当午？ 李四-->>王五: 王五，锄禾日当午？ 李四--x 张三: 汗滴禾下土！ 李四-x 王五: 汗滴禾下土！ Note right of 王五: 李四想啊想啊一直想，
想到太阳都下山了，
他还没想出来，
文本框都放不下了。 李四-->张三: 跑去问王五... 张三->王五: 好吧... 王五，白日依山尽？ {{</ mermaid >}}
在官方网站上有更多的[示例](https://mermaid-js.github.io/mermaid/#/examples)。  ## 侧边栏和提醒框 侧边栏和提醒框可以为文本提供直观的重要性强调效果，可以偶尔一用。  ### 侧边栏（Sidebar） 侧边栏可以将文字横向平移，只是其显示效果可能不像[提醒](#admonitions)那么明显。  > 此为侧边栏。 > > 你可以在侧边栏内排版段落和块级元素。 > > 你甚至可以在其中包含代码块。 > > ```bash > sudo dmesg > ```  ### 提醒框   {#admonitions} 提醒框（说明、警告等等）都是用 Hugo 短代码的形式展现。  {{< note >}} 说明信息用来引起读者的注意，但不过分强调其紧迫性。 你可以在提醒框内包含多个段落和块级元素。 | 甚至 | 包含 | 表格 | {{< /note >}}  {{< caution >}} 读者继续此操作时要格外小心。 {{< /caution >}}  {{< warning >}} 警告信息试图为读者指出一些不应忽略的、可能引发问题的事情。 {{< /warning >}} 注意，在较老的 Hugo 版本中，直接将 `note`、`warning` 或 `caution` 短代码 括入 HTML 注释当中是有问题的。这些短代码仍然会起作用。目前，在 0.70.0 以上版本中似乎已经修复了这一问题。  ## 包含其他页面 要包含其他页面，可使用短代码。 {{< note >}} {{< include "task-tutorial-prereqs.md" >}} {{< /note >}}  ## 嵌入的 Katacoda 环境 {{< kat-button >}}

The markdown file is for feature testing. We need to translate into Chinese based on our localization practices. The goal is to detect if some practices need improvement when either Hugo or Docsy code changes. /language zh /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 : The markdown file is for feature testing. We need to translate into Chinese based on our localization practices. The goal is to detect if some practices need improvement when either Hugo or Docsy code changes. /language zh /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/triage accepted
/assign


Question: {{< blocks/section id="oceanNodes" >}} {{% blocks/feature image="flower" %}} <del> [Kubernetes]({{< relref "/docs/concepts/overview/what-is-kubernetes" >}}), also known as K8s, is an open-source system for automating deployment, scaling, and management of containerized applications. </del> <ins> [Kubernetes]({{< relref "/docs/concepts/overview/" >}}), also known as K8s, is an open-source system for automating deployment, scaling, and management of containerized applications. </ins> It groups containers that make up an application into logical units for easy management and discovery. Kubernetes builds upon [15 years of experience of running production workloads at Google](http://queue.acm.org/detail.cfm?id=2898444), combined with best-of-breed ideas and practices from the community. {{% /blocks/feature %}}

How about "consists of a control plane and a set of machines called nodes"? Learning k8s is hard enough without obfuscating verbosity. For non-managers it's best to say it as it is ;-). Apart from that: "consists of the components that represent the control plane" suggests that there are components that represent a control pane, not are a control pane, and a set of nodes. So where is the control pane? I'm probably a big introvert and a nerd, but this confuses me to the point where I actually have to think about what this means... "In what way do the components represent the control pane? Where is the control pane itself? Am I not getting this? Probably not. It probably means these components are the control pane. Stupid me, of course that's what it means." So, while I could have understood what was meant in a split second, it takes me a couple of seconds of contemplation and a few minutes to suggest an improvement.
We could update the source of to make that change. Nice suggestion. is automatically generated. For a bigger improvement, we could move to and configure a redirect. /language en
/triage accepted /help If someone is planning to move this forward: move to configure a redirect from the old URL to the new URL (see ) make sure that the updated ends how you'd expect. It's likely that setting in the will 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 move to configure a redirect from the old URL to the new URL (see ) make sure that the updated ends how you'd expect. It's likely that setting in the will 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
Feel free to reply with questions.
I would love to take this /assign
/good-first-issue For the first-timers, look
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue For the first-timers, look 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: A kubelet restart will be required after changing `/var/lib/kubelet/config.conf` or `/var/lib/kubelet/kubeadm-flags.env`. <del> {{% heading "whatsnext" %}} </del> <ins> ## {{% heading "whatsnext" %}} </ins> - [Upgrading kubeadm clusters](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade) - [Customizing components with the kubeadm API](/docs/setup/production-environment/tools/kubeadm/control-plane-flags) - [Certificate management with kubeadm](/docs/tasks/administer-cluster/kubeadm/kubeadm-certs) <ins> - [Find more about kubeadm set-up](/docs/reference/setup-tools/kubeadm/) </ins>

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The document kubeadm- had a format error for section. you can find it More information regarding kubeadm can be . Proposed Solution: section should be in the right format like other documents for eg: Page to Update: /kind bug /language en /assign
/triage accepted /kind bug


Question:
{{ else }}
 {{ end }}
 {{ .Inner }}
 {{ .Inner | markdownify }}  {{ if .Get "author" }} — {{ .Get "author" }} {{ end }}

This is a clean up 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 Update the to use the  shortcode that is built in to Hugo. Why is this needed Using HTML and s directly is not as easy to maintain as Hugo shortcodes, which are explicitly designed to afford code reuse. Comments /kind cleanup /help /language en If you make this change, and check that the videos still render. Related to
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 : This is a clean up request <!-- See for guidance on writing an actionable issue description. --Update the to use the  shortcode that is built in to Hugo. Using HTML and s directly is not as easy to maintain as Hugo shortcodes, which are explicitly designed to afford code reuse. /kind cleanup /help /language en 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
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
Thanks


Question: <ins> --- title: "ネットワーク" description: クラスターのネットワークの設定方法を学びます。 weight: 160 --- </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
/triage accepted


Question: /docs/admin/kube-scheduler/     /docs/reference/generated/kube-scheduler/ 301 /docs/admin/kube-scheduler/     /docs/reference/generated/kube-scheduler/ 301 /docs/admin/kubeadm/     /docs/reference/generated/kubeadm/ 301 <ins> /docs/admin/kubelet/      /docs/reference/generated/kubelet/ 301 </ins> /docs/admin/federation-controller-manager/    /docs/reference/generated/federation-controller-manager/ 301 /docs/admin/federation-apiserver/      /docs/reference/generated/federation-apiserver/ 301 /docs/admin/kubefed/     /docs/reference/generated/kubefed/ 301

<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: The link of kubelet is broken. The directed page gives 404. doesn't redirect to Proposed Solution: It should redirect to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
I will have a look about it


Question: * Translate a Docker Compose file into Kubernetes objects * Go from local Docker development to managing your application via Kubernetes * Convert v1 or v2 Docker Compose `yaml` files or [Distributed Application Bundles](https://docs.docker.com/compose/bundles/) <ins> ## Kui [`Kui`](https://github.com/kubernetes-sigs/kui) is a GUI tool that takes your normal `kubectl` command line requests and responds with graphics. Kui takes the normal `kubectl` command line requests and responds with graphics. Instead of ASCII tables, Kui provides a GUI rendering with tables that you can sort. Kui lets you: * Directly click on long, auto-generated resource names instead of copying and pasting * Type in `kubectl` commands and see them execute, even sometimes faster than `kubectl` itself * Query a {{< glossary_tooltip text="Job" term_id="job">}} and see its execution rendered as a waterfall diagram * Click through resources in your cluster using a tabbed UI </ins>  No newline at end of file

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 Mention kui within Why is this needed We should make the tool more prominent. Comments Based on an idea from /kind feature /triage accepted /language en /priority backlog
I would make this change by editing and adding a new entry that describes kui. /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 : I would make this change by editing and adding a new entry that describes kui. /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
/sig cli
Hi , I would like to work on this issue. /assign
I have one question: While describing about about kui, should I also include some of its uses?


Question: ```yaml apiVersion: kubeadm.k8s.io/v1beta3 kind: JoinConfiguration <del> nodeRegistration: patches: directory: /home/user/somedir </del> <ins> patches: directory: /home/user/somedir </ins> ``` The directory must contain files named `target[suffix][+patchtype].extension`.

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 yaml for control-plane-flags patch section has an incorrect structure. Please see the InitConfiguration definition here: Proposed Solution: It should be like this: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--23 <!--Additional Information:--
I'd prepare a PR on this, but cloning the repo takes forever. Will do that tomorrow.
That is indeed a bug in the docs. Thanks for logging the ticket. /assign /sig cluster-lifecycle
i can send the PR, but if you'd like to contribute in the future you must also sign the CLA.
Sure thing. Will do! Thanks for the heads up!
PR is up /triage accepted


Question: app: win-webserver spec: ports: <del> # the port that this service should serve on </del> <ins> # このサービスが提供するポート </ins> - port: 80 targetPort: 80 selector:

This is a Feature Request What would you like to be Translate docs/setup/production-environment/windows/user-guide-windows-containers/ into Japanese Why is this needed This page has not been translated. Comments /language ja /assign


Question:
[input_placeholder_email_address] other = "endereço de e-mail"  [feedback_no] other = "Não"  [latest_version] other = "última versão."  [version_check_mustbe] other = "Seu servidor Kubernetes deve ser versão" [version_check_mustbeorlater] other = "O seu servidor Kubernetes deve estar em ou depois da versão " [version_check_tocheck] other = "Para verificar a versão, digite " [caution] other = "Cuidado:" [note] other = "Nota:"   [layouts_blog_pager_next] other = "Próximo >>"   [warning] other = "Aviso:"   [layouts_blog_pager_prev] other = "<< Anterior"   [main_read_about] other = "Ler sobre"   [layouts_case_studies_list_tell] other = "Conte seu caso"   [main_read_more] other = "Consulte Mais informação"   [layouts_docs_glossary_aka] other = "Também conhecido como"   [main_github_invite] other = "Interessado em mergulhar na base de código do Kubernetes?"   [layouts_docs_glossary_click_details_after] other = "indicadores abaixo para uma maior explicação sobre um termo em particular."   [main_github_view_on] other = "Veja no Github"   [layouts_docs_glossary_click_details_before] other = "Clique nos"   [main_github_create_an_issue] other = "Abra um bug"   [layouts_docs_glossary_description] other = "Este glossário pretende ser uma lista padronizada e abrangente da terminologia do Kubernetes. Inclui termos técnicos específicos dos K8s, além de termos mais gerais que fornecem um contexto útil."   [main_community_explore] other = "Explore a comunidade"   [layouts_docs_glossary_deselect_all] other = "Desmarcar tudo"   [main_kubernetes_features] other = "Recursos do Kubernetes"   [layouts_docs_glossary_filter] other = "Filtrar termos de acordo com suas tags"   [main_cncf_project] other = """Nós somos uma CNCF projeto graduado
"""   [layouts_docs_glossary_select_all] other = "Selecionar tudo"   [main_kubeweekly_baseline] other = "Interessado em receber as últimas novidades sobre Kubernetes? Inscreva-se no KubeWeekly."   [layouts_docs_partials_feedback_improvement] other = "sugerir uma melhoria"   [main_kubernetes_past_link] other = "Veja boletins passados"   [layouts_docs_partials_feedback_issue] other = "Abra um bug no repositório do GitHub se você deseja "   [main_kubeweekly_signup] other = "Se inscrever"   [layouts_docs_partials_feedback_or] other = "ou"   [main_contribute] other = "Contribuir"   [layouts_docs_partials_feedback_problem] other = "reportar um problema"   [main_edit_this_page] other = "Edite essa página"   [layouts_docs_partials_feedback_thanks] other = "Obrigado pelo feedback. Se você tiver uma pergunta específica sobre como utilizar o Kubernetes, faça em"   [main_page_history] other ="História da página"   [layouts_docs_search_fetching] other = "Buscando resultados.."   [main_page_last_modified_on] other = "Última modificação da página em"   # Main page localization  [main_by] other = "por"  [main_documentation_license] other = """Os autores do Kubernetes | Documentação Distribuída sob CC BY 4.0""" [main_copyright_notice] other = """A Fundação Linux ®. Todos os direitos reservados. A Linux Foundation tem marcas registradas e usa marcas registradas. Para uma lista de marcas registradas da The Linux Foundation, por favor, veja nossa Página de uso de marca registrada""" # Labels for the docs portal home page. [docs_label_browse] other = "Procurar documentos" [docs_label_contributors] other = "Colaboradores"   [main_cncf_project] other = """Nós somos uma CNCF projeto graduado
"""   [docs_label_users] other = "Usuários"   [main_community_explore] other = "Explore a comunidade"   [docs_label_i_am] other = "Eu sou..."   [main_contribute] other = "Contribuir"   # layouts > blog > pager   [main_copyright_notice] other = """A Fundação Linux ®. Todos os direitos reservados. A Linux Foundation tem marcas registradas e usa marcas registradas. Para uma lista de marcas registradas da The Linux Foundation, por favor, veja nossa Página de uso de marca registrada"""   [layouts_blog_pager_prev] other = "<< Anterior"   [main_documentation_license] other = """Os autores do Kubernetes | Documentação Distribuída sob CC BY 4.0"""   [layouts_blog_pager_next] other = "Próximo >>"   [main_edit_this_page] other = "Edite essa página"   # layouts > blog > list   [main_github_create_an_issue] other = "Abra um bug"   [layouts_case_studies_list_tell] other = "Conte seu caso"   [main_github_invite] other = "Interessado em mergulhar na base de código do Kubernetes?"   # layouts > docs > glossary   [main_github_view_on] other = "Veja no Github"   [layouts_docs_glossary_description] other = "Este glossário pretende ser uma lista padronizada e abrangente da terminologia do Kubernetes. Inclui termos técnicos específicos dos K8s, além de termos mais gerais que fornecem um contexto útil."   [main_kubernetes_features] other = "Recursos do Kubernetes"   [layouts_docs_glossary_filter] other = "Filtrar termos de acordo com suas tags"   [main_kubernetes_past_link] other = "Veja boletins passados"   [layouts_docs_glossary_select_all] other = "Selecionar tudo"   [main_kubeweekly_baseline] other = "Interessado em receber as últimas novidades sobre Kubernetes? Inscreva-se no KubeWeekly."   [layouts_docs_glossary_deselect_all] other = "Desmarcar tudo"   [main_kubeweekly_signup] other = "Se inscrever"   [layouts_docs_glossary_aka] other = "Também conhecido como"   [main_page_history] other ="História da página"   [layouts_docs_glossary_click_details_before] other = "Clique nos"   [main_page_last_modified_on] other = "Última modificação da página em"   [layouts_docs_glossary_click_details_after] other = "indicadores abaixo para uma maior explicação sobre um termo em particular."   [main_read_about] other = "Ler sobre"   # layouts > docs > search   [main_read_more] other = "Consulte Mais informação"   [layouts_docs_search_fetching] other = "Buscando resultados.."   # Miscellaneous   # layouts > partial > feedback   [note] other = "Nota:"   [layouts_docs_partials_feedback_thanks] other = "Obrigado pelo feedback. Se você tiver uma pergunta específica sobre como utilizar o Kubernetes, faça em"   [objectives_heading] other = "Objetivos"   [layouts_docs_partials_feedback_issue] other = "Abra um bug no repositório do GitHub se você deseja "   [prerequisites_heading] other = "Antes de você começar"   [layouts_docs_partials_feedback_problem] other = "reportar um problema"   [ui_search_placeholder] other = "Procurar"   [layouts_docs_partials_feedback_or] other = "ou"   [version_check_mustbeorlater] other = "O seu servidor Kubernetes deve estar em ou depois da versão "   [layouts_docs_partials_feedback_improvement] other = "sugerir uma melhoria"   [version_check_mustbe] other = "Seu servidor Kubernetes deve ser versão"   # Community links [community_twitter_name] other = "Twitter" [community_github_name] other = "GitHub" [community_slack_name] other = "Slack" [community_stack_overflow_name] other = "Stack Overflow" [community_forum_name] other = "Fórum" [community_events_calendar] other = "Calendário de Eventos"   [version_check_tocheck] other = "Para verificar a versão, digite "   # UI elements [ui_search_placeholder] other = "Procurar"   [warning] other = "Aviso:"   [input_placeholder_email_address] other = "endereço de e-mail"   No newline at end of file  [whatsnext_heading] other = "Qual é o próximo"

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: After PR was merged, the website does not build. This is because the Portuguese localization includes a duplicate translation for a string. Proposed Solution: Remove the duplication Additional Information: /priority critical-urgent /kind bug


Question: [input_placeholder_email_address] other = "adresse email" <ins> [latest_release] other = "Dernière version:" [end_of_life] other = "Fin du support:" [previous_patches] other = "Correctifs publiés:" [release_date_before] other = "(publiée: " </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 blank for the main page content. Proposed Solution: Delete (fall back to English) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language fr
/triage accepted
It have to be deleted and what do you mean by fall back to english? Could you please elaborate?
I guess falling back means the menu link of the French website should lead to (i.e. its English version) instead of since there is no content in the French version. However, I don't understand where this URL () originates from. The partial seems to be incorrect as it always links to the page (despite the website's language currently in use), doesn't it? E.g., there is the content for the locale, but the navigation menu on still leads to the page, not .
/assign
There are 2 issues here: I took a look and indeed, introduced the issue since it a new page under the subfolder. Moreover, is correct, you can get to these translation by going on the page and clicking the language dropdown, and selecting Français but the always redirect to the English version.
/area localization
Both issues were resolved and merged!


Question: Here's a configuration file for a Deployment. The file does not specify `strategy` or `selector`: <del> {% include code.html language="yaml" file="simple_deployment.yaml" ghlink="/docs/concepts/tools/simple_deployment.yaml" %} </del> <ins> {% include code.html language="yaml" file="simple_deployment.yaml" ghlink="/docs/tutorials/object-management-kubectl/simple_deployment.yaml" %} </ins> Create the object using `kubectl apply`: ```shell <del> kubectl apply -f http://k8s.io/docs/concepts/tools/kubectl/simple_deployment.yaml </del> <ins> kubectl apply -f http://k8s.io/docs/tutorials/object-management-kubectl/simple_deployment.yaml </ins> ``` Print the live configuration using `kubectl get`: ```shell <del> kubectl get -f http://k8s.io/docs/concepts/tools/kubectl/simple_deployment.yaml -o yaml </del> <ins> kubectl get -f http://k8s.io/docs/tutorials/object-management-kubectl/simple_deployment.yaml -o yaml </ins> ``` The output shows that the API server set several fields to default values in the live

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


Question: Example: `app.kubernetes.io/instance: "mysql-abcxzy"` <del> Used on: All Objects </del> <ins> Used on: All Objects (typically used on [workload resources](/docs/reference/kubernetes-api/workload-resources/)). </ins> <del> A unique name identifying the instance of an application. </del> <ins> A unique name identifying the instance of an application. To assign a non-unique name, use [app.kubernetes.io/name](#app-kubernetes-io-name). </ins> One of the [recommended labels](/docs/concepts/overview/working-with-objects/common-labels/#labels).

Page: The labels' fields by could be clearer - they typically apply to as pointed out by in - I'll address this in a PR shortly, opening this issue to link.
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
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]:
The Kubernetes project currently lacks enough active 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 Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:
The Kubernetes project currently lacks enough active 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: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:
Closing this issue.

<detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. 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 closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] 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
/reopen
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details


Question: <ins> --- title: ノードのトポロジー管理ポリシーを制御する reviewers: - ConnorDoyle - klueska - lmdaly - nolancon - bg-chun content_template: templates/task min-kubernetes-server-version: v1.18 --- {{% capture overview %}} {{< feature-state state="beta" for_k8s_version="v1.18" >}} 近年、CPUやハードウェア・アクセラレーターの組み合わせによって、レイテンシーが致命的となる実行や高いスループットを求められる並列計算をサポートするシステムが増えています。このようなシステムには、通信、科学技術計算、機械学習、金融サービス、データ分析などの分野のワークロードが含まれます。このようなハイブリッドシステムは、高い性能の環境で構成されます。 最高のパフォーマンスを引き出すために、CPUの分離やメモリーおよびデバイスの位置に関する最適化が求められます。しかしながら、Kubernetesでは、このような最適化とは分断されたコンポーネントのセットして扱われます。 _トポロジーマネージャー_ はKubeletコンポーネントの1つで最適化の役割を担い、コンポーネント群を調和して機能させます。 {{% /capture %}} {{% capture prerequisites %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} {{% /capture %}} {{% capture steps %}} ## トポロジーマネージャーはどのように機能するか トポロジーマネージャー導入前は、KubernetesにおいてCPUマネージャーやデバイスマネージャーはそれぞれ独立してリソースの割り当てを決定します。 これは、マルチソケットのシステムでは望ましくない割り当てとなり、パフォーマンスやレイテンシーが求められるアプリケーションは、この望ましくない割り当てに悩まされます。 この場合の望ましくない例として、CPUやデバイスが異なるNUMAノードに割り当てられ、それによりレイテンシー悪化を招くことが挙げられます。 トポロジーマネージャーはKubeletコンポーネントであり、信頼できる情報源として振舞います。それによって、他のKubeletコンポーネントはトポロジーに沿ったリソース割り当ての選択を行うことができます。 トポロジーマネージャーは *Hint Providers* と呼ばれるコンポーネントのインターフェースを提供し、トポロジー情報を送受信します。トポロジーマネージャーは、ノード単位のポリシー群を保持します。ポリシーについて以下で説明します。 トポロジーマネージャーは *Hint Providers* からトポロジー情報を受け取ります。トポロジー情報は、利用可能なNUMAノードと優先割り当て表示を示すビットマスクです。トポロジーマネージャーのポリシーは、提供されたヒントに対して一連の操作を行い、ポリシーに沿ってヒントをまとめて最適な結果を得ます。もし、望ましくないヒントが保存された場合、ヒントの優先フィールドがfalseに設定されます。現在のポリシーでは、最も狭い優先マスクが優先されます。 選択されたヒントはトポロジーマネージャーの一部として保存されます。設定されたポリシーにしたがい、選択されたヒントに基づいてノードがPodを許可したり、拒否することができます。 トポロジーマネージャーに保存されたヒントは、*Hint Providers* が使用しリソース割り当てを決定します。 ### トポロジーマネージャーの機能を有効にする トポロジーマネージャーをサポートするには、`TopologyManager` [フィーチャーゲート](/ja/docs/reference/command-line-tools-reference/feature-gates/)を有効にする必要があります。Kubernetes 1.18ではデフォルトで有効です。 ## トポロジーマネージャーのスコープとポリシー トポロジーマネージャは現在: - 全てのQoAクラスのPodを調整する - Hint Providerによって提供されたトポロジーヒントから、要求されたリソースを調整する これらの条件が合致した場合、トポロジーマネージャーは要求されたリソースを調整します。 この調整をどのように実行するかカスタマイズするために、トポロジーマネージャーは2つのノブを提供します: `スコープ` と`ポリシー`です。 `スコープ`はリソースの配置を行う粒度を定義します(例:`pod`や`container`)。そして、`ポリシー`は調整を実行するための実戦略を定義します(`best-effort`, `restricted`, `single-numa-node`等)。 現在利用可能な`スコープ`と`ポリシー`の値について詳細は以下の通りです。 {{< note >}} PodのSpecにある他の要求リソースとCPUリソースを調整するために、CPUマネージャーを有効にし、適切なCPUマネージャーのポリシーがノードに設定されるべきです。[CPU管理ポリシー](/docs/tasks/administer-cluster/cpu-management-policies/)を参照してください。 {{< /note >}} {{< note >}} PodのSpecにある他の要求リソースとメモリー（およびhugepage）リソースを調整するために、メモリーマネージャーを有効にし、適切なメモリーマネージャーポリシーがノードに設定されるべきです。[メモリーマネージャー](/docs/tasks/administer-cluster/memory-manager/) のドキュメントを確認してください。 {{< /note >}} ### トポロジーマネージャーのスコープ トポロジーマネージャーは、以下の複数の異なるスコープでリソースの調整を行う事が可能です: * `container` (デフォルト) * `pod` いずれのオプションも、`--topology-manager-scope`フラグによって、kubelet起動時に選択できます。 ### containerスコープ `container`スコープはデフォルトで使用されます。 このスコープでは、トポロジーマネージャーは連続した複数のリソース調整を実行します。つまり、Pod内の各コンテナは、分離された配置計算がされます。言い換えると、このスコープでは、コンテナを特定のNUMAノードのセットにグループ化するという概念はありません。実際には、トポロジーマネージャーは各コンテナのNUMAノードへの配置を任意に実行します。 コンテナをグループ化するという概念は、以下のスコープで設定・実行されます。例えば、`pod`スコープが挙げられます。 ### podスコープ `pod`スコープを選択するには、コマンドラインで`--topology-manager-scope=pod`オプションを指定してkubeletを起動します。 このスコープでは、Pod内全てのコンテナを共通のNUMAノードのセットにグループ化することができます。トポロジーマネージャーはPodをまとめて1つとして扱い、ポッド全体（全てのコンテナ）を単一のNUMAノードまたはNUMAノードの共通セットのいずれかに割り当てようとします。以下の例は、さまざまな場面でトポロジーマネージャーが実行する調整を示します: * 全てのコンテナは、単一のNUMAノードに割り当てられます。 * 全てのコンテナは、共有されたNUMAノードのセットに割り当てられます。 Pod全体に要求される特定のリソースの総量は[有効なリクエスト／リミット](/ja/docs/concepts/workloads/pods/init-containers/#resources)の式に従って計算されるため、この総量の値は以下の最大値となります。 * 全てのアプリケーションコンテナのリクエストの合計。 * initコンテナのリクエストの最大値。 `pod`スコープと`single-numa-node`トポロジーマネージャーポリシーを併用することは、レイテンシーが重要なワークロードやIPCを行う高スループットのアプリケーションに対して特に有効です。両方のオプションを組み合わせることで、Pod内の全てのコンテナを単一のNUMAノードに配置できます。そのため、PodのNUMA間通信によるオーバーヘッドを排除することができます。 `single-numa-node`ポリシーの場合、可能な割り当ての中に適切なNUMAノードのセットが存在する場合にのみ、Podが許可されます。上の例をもう一度考えてみましょう: * 1つのNUMAノードのみを含むセット - Podが許可されます。 * 2つ以上のNUMAノードを含むセット - Podが拒否されます(1つのNUMAノードの代わりに、割り当てを満たすために2つ以上のNUMAノードが必要となるため)。 要約すると、トポロジーマネージャーはまずNUMAノードのセットを計算し、それをトポロジーマネージャーのポリシーと照合し、Podの拒否または許可を検証します。 ### トポロジーマネージャーのポリシー トポロジーマネージャーは4つの調整ポリシーをサポートします。`--topology-manager-policy`というKubeletフラグを通してポリシーを設定できます。 4つのサポートされるポリシーがあります: * `none` (デフォルト) * `best-effort` * `restricted` * `single-numa-node` {{< note >}} トポロジーマネージャーが **pod** スコープで設定された場合、コンテナはポリシーによって、Pod全体の要求として反映します。 したがって、Podの各コンテナは **同じ** トポロジー調整と同じ結果となります。 {{< /note >}} ### none ポリシー {#policy-none} これはデフォルトのポリシーで、トポロジーの調整を実行しません。 ### best-effort ポリシー {#policy-best-effort} Pod内の各コンテナに対して、`best-effort` トポロジー管理ポリシーが設定されたkubeletは、各Hint Providerを呼び出してそれらのリソースの可用性を検出します。 トポロジーマネージャーはこの情報を使用し、そのコンテナの推奨されるNUMAノードのアフィニティーを保存します。アフィニティーが優先されない場合、トポロジーマネージャーはこれを保存し、Podをノードに許可します。 *Hint Providers* はこの情報を使ってリソースの割り当てを決定します。 ### restricted ポリシー {#policy-restricted} Pod内の各コンテナに対して、`restricted` トポロジー管理ポリシーが設定されたkubeletは各Hint Providerを呼び出してそれらのリソースの可用性を検出します。 トポロジーマネージャーはこの情報を使用し、そのコンテナの推奨されるNUMAノードのアフィニティーを保存します。アフィニティーが優先されない場合、トポロジーマネージャーはPodをそのノードに割り当てることを拒否します。この結果、PodはPodの受付失敗となり`Terminated` 状態になります。 Podが一度`Terminated`状態になると、KubernetesスケジューラーはPodの再スケジューリングを試み **ません** 。Podの再デプロイをするためには、ReplicasetかDeploymenを使用してください。`Topology Affinity`エラーとなったpodを再デプロイするために、外部のコントロールループを実行することも可能です。 Podが許可されれば、 *Hint Providers* はこの情報を使ってリソースの割り当てを決定します。 ### single-numa-node ポリシー {#policy-single-numa-node} Pod内の各コンテナに対して、`single-numa-node`トポロジー管理ポリシーが設定されたkubeletは各Hint Prociderを呼び出してそれらのリソースの可用性を検出します。 トポロジーマネージャーはこの情報を使用し、単一のNUMAノードアフィニティが可能かどうか決定します。 可能な場合、トポロジーマネージャーは、この情報を保存し、*Hint Providers* はこの情報を使ってリソースの割り当てを決定します。 不可能な場合、トポロジーマネージャーは、Podをそのノードに割り当てることを拒否します。この結果、Pod は Pod の受付失敗となり`Terminated`状態になります。 Podが一度`Terminated`状態になると、KubernetesスケジューラーはPodの再スケジューリングを試み**ません**。Podの再デプロイをするためには、ReplicasetかDeploymentを使用してください。`Topology Affinity`エラーとなったpodを再デプロイするために、外部のコントロールループを実行することも可能です。 ### Podとトポロジー管理ポリシーの関係 以下のようなpodのSpecで定義されるコンテナを考えます: ```yaml spec: containers: - name: nginx image: nginx ``` `requests`も`limits`も定義されていないため、このPodは`BestEffort`QoSクラスで実行します。 ```yaml spec: containers: - name: nginx image: nginx resources: limits: memory: "200Mi" requests: memory: "100Mi" ``` requestsがlimitsより小さい値のため、このPodは`Burstable`QoSクラスで実行します。 選択されたポリシーが`none`以外の場合、トポロジーマネージャーは、これらのPodのSpecを考慮します。トポロジーマネージャーは、Hint Providersからトポロジーヒントを取得します。CPUマネージャーポリシーが`static`の場合、デフォルトのトポロジーヒントを返却します。これらのPodは明示的にCPUリソースを要求していないからです。 ```yaml spec: containers: - name: nginx image: nginx resources: limits: memory: "200Mi" cpu: "2" example.com/device: "1" requests: memory: "200Mi" cpu: "2" example.com/device: "1" ``` 整数値でCPUリクエストを指定されたこのPodは、`requests`が`limits`が同じ値のため、`Guaranteed`QoSクラスで実行します。 ```yaml spec: containers: - name: nginx image: nginx resources: limits: memory: "200Mi" cpu: "300m" example.com/device: "1" requests: memory: "200Mi" cpu: "300m" example.com/device: "1" ``` CPUの一部をリクエストで指定されたこのPodは、`requests`が`limits`が同じ値のため、`Guaranteed`QoSクラスで実行します。 ```yaml spec: containers: - name: nginx image: nginx resources: limits: example.com/deviceA: "1" example.com/deviceB: "1" requests: example.com/deviceA: "1" example.com/deviceB: "1" ``` CPUもメモリもリクエスト値がないため、このPodは `BestEffort` QoSクラスで実行します。 トポロジーマネージャーは、上記Podを考慮します。トポロジーマネージャーは、Hint ProvidersとなるCPUマネージャーとデバイスマネージャーに問い合わせ、トポロジーヒントを取得します。 整数値でCPU要求を指定された`Guaranteed`QoSクラスのPodの場合、`static`が設定されたCPUマネージャーポリシーは、排他的なCPUに関するトポロジーヒントを返却し、デバイスマネージャーは要求されたデバイスのヒントを返します。 CPUの一部を要求を指定された`Guaranteed`QoSクラスのPodの場合、排他的ではないCPU要求のため`static`が設定されたCPUマネージャーポリシーはデフォルトのトポロジーヒントを返却します。デバイスマネージャーは要求されたデバイスのヒントを返します。 上記の`Guaranteed`QoSクラスのPodに関する2ケースでは、`none`で設定されたCPUマネージャーポリシーは、デフォルトのトポロジーヒントを返却します。 `BestEffort`QoSクラスのPodの場合、`static`が設定されたCPUマネージャーポリシーは、CPUの要求がないためデフォルトのトポロジーヒントを返却します。デバイスマネージャーは要求されたデバイスごとのヒントを返します。 トポロジーマネージャーはこの情報を使用してPodに最適なヒントを計算し保存します。保存されたヒントは Hint Providersが使用しリソースを割り当てます。 ### 既知の制限 1. トポロジーマネージャーが許容するNUMAノードの最大値は8です。8より多いNUMAノードでは、可能なNUMAアフィニティを列挙しヒントを生成する際に、生成する状態数が爆発的に増加します。 2. スケジューラーはトポロジーを意識しません。そのため、ノードにスケジュールされた後に実行に失敗する可能性があります。 </ins>

This is a Feature Request What would you like to be Translate tasks/administer-cluster/topology-manager/ into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign
/triage accepted
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle rotten
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /close
Closing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details


Question: - [create Secret from config file](/docs/tasks/configmap-secret/managing-secret-using-config-file/) - [create Secret using kustomize](/docs/tasks/configmap-secret/managing-secret-using-kustomize/) <del> ### Editing a Secret </del> <ins> ## Editing a Secret </ins> An existing Secret may be edited with the following command:

This is a Feature Request What would you like to be More detailed documentation about Secret, in addition to the current lengthy Secret concept. Why is this needed We have many secrets about Secret which should be documented. For example, the securet type can be one of: - - - - Some secret types needs special annotation or data keys. For example, for service account tokens, the following two annotations are required: - AND, the following key is required in the data property: Comments In addition to the new contents to be , we should consider moving some of the task-alike content out of the concept introduction at
/priority important-longterm
Can you please point me where can I read more about , Also which could help in add & improving the following? Thanks
This information is in the upstream source code. There is no convenient way for dumping them as swagger/openapi specs which are used for generating the API reference documentation. I would even suspect there could be one in future given the complexity of the semantics and nesting of struct definitions in Go lang. You have to read the source code to understand the many constraints for resources like this. For the resource type, the validation logic is here:
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale
+1 Especially, is the token inside a secret periodically roated? Expiration of seems to be set to 5 years. Is it going to be renewed automatically, or do you have to renew manually (and how)? What's the impact to already running workloads that hit the expiration?
+1 Additionally: Document that secrets whose keys are removed from secrets files remain in the deployed secrets as empty strings, meaning the secrets resource must be deleted to remove that key and rebuilt on next deploy.
Immutable Secrets are also relevant ( has some 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
Given the mentioned gap from the issue description and the various comments received, I'd like to propose a freeze of lifecycle for this issue. /lifecycle frozen
Put this on my TODO list. /assign


Question: ``` [kubernetes] name=Kubernetes <del> baseurl=https://pkgs.k8s.io/core:/stable:/v{{< param "version" >}}/rpm/ </del> <ins> baseurl=https://pkgs.k8s.io/core:/stable:/{{< param "version" >}}/rpm/ </ins> enabled=1 gpgcheck=1 <del> gpgkey=https://pkgs.k8s.io/core:/stable:/v{{< param "version" >}}/rpm/repodata/repomd.xml.key </del> <ins> gpgkey=https://pkgs.k8s.io/core:/stable:/{{< param "version" >}}/rpm/repodata/repomd.xml.key </ins> exclude=kubelet kubeadm kubectl cri-tools kubernetes-cni ```

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: In section , under tab, there is an extra "v" in the and URLs corresponding to the latest kubernetes version.  Proposed Solution: Correct to . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
I can contribute the fix - easy one.
/triage accepted Thanks


Question: mymap-child    0      13m8s mymap-parent   0      13m8s <del> kubectl delete --cascade=false configmap/mymap-parent </del> <ins> kubectl delete --cascade=orphan configmap/mymap-parent </ins> configmap "mymap-parent" deleted kubectl get configmap

According to the can get a parameter with a value of "background", "orphan", or "foreground". proposes to use .
Hello Related PRs/issues: So, the page should be updated. /kind bug /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 : Hello is now deprecated in favor of warning: is deprecated (boolean value) and can be replaced with Cascade=false is deprecated in kubectl 1.21, according to Bug /language en /help </details
/triage accepted
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue </details
/assign
/assign
To : has already assigned himself/herself, and posted a PR ().


Question: type: LoadBalancer ``` <del> ## Garbage Collecting Load Balancers </del> <ins> ### Caveats and limitations when preserving source IPs Load balancing services from some cloud providers do not let you configure different weights for each target. With each target weighted equally in terms of sending traffic to Nodes, external traffic is not equally load balanced across different Pods. The external load balancer is unaware of the number of Pods on each node that are used as a target. Where `NumServicePods <<  _NumNodes` or `NumServicePods >> NumNodes`, a fairly close-to-equal distribution will be seen, even without weights. Internal pod to pod traffic should behave similar to ClusterIP services, with equal probability across all pods. ## Garbage collecting load balancers </ins> {{< feature-state for_k8s_version="v1.17" state="stable" >}}

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: (see ) Weights aren't built in to Service / Endpoints / EndpointSlice / Ingress but you can indicate weighting with annotations and similar mechanisms. For example: https://kubernetes- Proposed Solution: Remove the text: Revise to explain that each implementation uses its own mechanisms for weighting and that these are not standardized. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.19 Additional Information: /language en /sig network
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
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle rotten
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /close
Closing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/reopen /remove-lifecycle rotten
Reopened this issue.

<detailsIn response to : /reopen /remove-lifecycle rotten Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle stale
The Kubernetes project currently lacks enough active 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 Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:


Question: and bare metal workloads. * [Flannel](https://github.com/flannel-io/flannel#deploying-flannel-manually) is an overlay network provider that can be used with Kubernetes. <ins> * [Gateway API](/docs/concepts/services-networking/gateway/) is an open source project managed by the [SIG Network](https://github.com/kubernetes/community/tree/master/sig-network) community and provides an expressive, extensible, and role-oriented API for modeling service networking. </ins> * [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

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. Laden Sie die neueste Version herunter: ``` <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/darwin/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/$(curl -LS https://dl.k8s.io/release/stable.txt)/bin/darwin/amd64/kubectl </ins> ``` <del> Um eine bestimmte Version herunterzuladen, ersetzen Sie den Befehlsteil `$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)` mit der jeweiligen Version. </del> <ins> Um eine bestimmte Version herunterzuladen, ersetzen Sie den Befehlsteil `$(curl -LS https://dl.k8s.io/release/stable.txt)` mit der jeweiligen Version. </ins> Um beispielsweise die Version {{< param "fullversion" >}} auf macOS herunterzuladen, verwenden Sie den folgenden Befehl: ``` <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/{{< param "fullversion" >}}/bin/darwin/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/darwin/amd64/kubectl </ins> ``` 2. Machen Sie die kubectl-Binärdatei ausführbar.

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 still references to instead of is the correct advertised download host and will eventually move to be fastly shielding a fully community-owned bucket ref: Proposed Solution: Replace with Also replace any references with using if applicable. Page to Update: Assorted e.g. , <!--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
/assign
hi Not a problem, didn't see anyone assigned to this issue. I am unassigning myself and assigning it to you. /unassign
/assign
Hi, I found a small issue with your proposed changes regarding one of the URLs, which is mentioned twice in the file. While returns as expected, I am getting an nginx-rendered HTML page saying for the new command () instead. As I understand, it happens due to the redirect configured on the new web server. Thus, works fine for me (it returns as expected).
i see Let me update it, thanks your work
Just done, please review all of PRs
Thanks!
And yes: These will need to follow redirects, in the future the tentative plan is it will redirect to a CDN in front of a different bucket created in a fully project / SIG-K8s-Infra controlled GCP or AWS account. I would recommend for downloading with curl more generally, even in docs / usage for other hosts.


Question: `Failed`    | Pod内のすべてのコンテナが終了し、少なくとも1つのコンテナが異常終了しました。つまり、コンテナはゼロ以外のステータスで終了したか、システムによって終了されました。 `Unknown`   | 何らかの理由によりPodの状態を取得できませんでした。このフェーズは通常はPodのホストとの通信エラーにより発生します。 <ins> {{< note >}} Podの削除中に、kubectlコマンドには`Terminating`が出力されることがあります。この`Terminating`ステータスは、Podのフェーズではありません。Podには、正常に終了するための期間を与えられており、デフォルトは30秒です。`--force`フラグを使用して、[Podを強制的に削除する](/ja/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination-forced)ことができます。 {{< /note >}} </ins> Nodeが停止するか、クラスタの残りの部分から切断された場合、Kubernetesは失われたNode上のすべてのPodの`Phase`をFailedに設定するためのポリシーを適用します。 ## コンテナのステータス {#container-states}

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:
 Esta tela é muito estreita para interagir com o Terminal, use um desktop / tablet.

 Continue para o Módulo 2›

 Conteúdo indisponível

 O tutorial interativo de como criar um cluster não está disponível. Para mais informações, veja o  anúncio de encerramento do Katacoda.

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


Question: <ins> --- title: 端口和协议 content_type: reference weight: 50 --- <!-- --- title: Ports and Protocols content_type: reference weight: 50 --- --> <!-- When running Kubernetes in an environment with strict network boundaries, such as on-premises datacenter with physical network firewalls or Virtual Networks in Public Cloud, it is useful to be aware of the ports and protocols used by Kubernetes components --> 当你在一个有严格网络边界的环境里运行 Kubernetes，例如拥有物理网络防火墙或者拥有公有云中虚拟网络的自有数据中心，了解 Kubernetes 组件使用了哪些端口和协议是非常有用的。 <!-- ## Control plane | Protocol | Direction | Port Range | Purpose                 | Used By                   | |----------|-----------|------------|-------------------------|---------------------------| | TCP      | Inbound   | 6443       | Kubernetes API server   | All                       | | TCP      | Inbound   | 2379-2380  | etcd server client API  | kube-apiserver, etcd      | | TCP      | Inbound   | 10250      | Kubelet API             | Self, Control plane       | | TCP      | Inbound   | 10259      | kube-scheduler          | Self                      | | TCP      | Inbound   | 10257      | kube-controller-manager | Self                      | Although etcd ports are included in control plane section, you can also host your own etcd cluster externally or on custom ports. --> ## 控制面  {#control-plane} | 协议     | 方向      | 端口范围     | 目的                     | 使用者                     | |----------|-----------|------------|-------------------------|---------------------------| | TCP      | 入站       | 6443       | Kubernetes API server   | 所有                       | | TCP      | 入站       | 2379-2380  | etcd server client API  | kube-apiserver, etcd      | | TCP      | 入站       | 10250      | Kubelet API             | 自身, 控制面                | | TCP      | 入站       | 10259      | kube-scheduler          | 自身                       | | TCP      | 入站       | 10257      | kube-controller-manager | 自身                       | 尽管 etcd 的端口也列举在控制面的部分，但你也可以在外部自己托管 etcd 集群或者自定义端口。 <!-- ## Worker node(s) {#node} | Protocol | Direction | Port Range  | Purpose               | Used By                 | |----------|-----------|-------------|-----------------------|-------------------------| | TCP      | Inbound   | 10250       | Kubelet API           | Self, Control plane     | | TCP      | Inbound   | 30000-32767 | NodePort Services†    | All                     | † Default port range for [NodePort Services](/docs/concepts/services-networking/service/). All default port numbers can be overridden. When custom ports are used those ports need to be open instead of defaults mentioned here. One common example is API server port that is sometimes switched to 443. Alternatively, the default port is kept as is and API server is put behind a load balancer that listens on 443 and routes the requests to API server on the default port. --> ## 工作节点  {#node} | 协议     | 方向      | 端口范围     | 目的                     | 使用者                  | |----------|-----------|-------------|-----------------------|-------------------------| | TCP      | 入站       | 10250       | Kubelet API           | 自身, 控制面             | | TCP      | 入站       | 30000-32767 | NodePort Services†    | 所有                    | † [NodePort Services](/zh/docs/concepts/services-networking/service/)的默认端口范围。 所有默认端口都可以重新配置。当使用自定义的端口时，你需要打开这些端口来代替这里提到的默认端口。 一个常见的例子是 API 服务器的端口有时会配置为443。或者你也可以使用默认端口，把 API 服务器放到一个监听443 端口的负载均衡器后面，并且路由所有请求到 API 服务器的默认端口。 </ins>

Hi, I'm interested to translate the "Reference/Ports and Protocols" page. This is a Feature Request: translate en/docs/reference/ports-and- into Chinese. What would you like to be : zh/docs/reference/ports-and- /language zh /kind feature
/assign
/triage accepted


Question:
{{ $shouldDelayActive := ge (len .Site.Pages) 2000 }}
  <form class="td-sidebar__search d-flex align-items-center"> {{ partial "search-input.html" . }} <button class="btn btn-link td-sidebar__toggle d-md-none p-0 ml-3 fas fa-bars" type="button" data-toggle="collapse" data-target="#td-section-nav" aria-controls="td-docs-nav" aria-expanded="false" aria-label="Toggle section navigation"> </button> </form>

This is a Feature Request I'd like to start a search on the blogs from the blog page. What would you like to be Add a link to the docs default search engine. Why is this needed Blog content is listed only by the year published. Comments It may be nice to develop categories to tag the blog content and provide different ways to display the blog entries (not just by year).
/area blog
/language en
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /close
Closing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/remove-lifecycle rotten
Hello is this PR still valid? If so, could you reopen it since fejta-bot has closed it?
/reopen
You can't reopen an issue/PR unless you authored it or you are a collaborator. <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
/reopen
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
. I reopened the issue. You could propose a PR with changes and reach out to the blog sub-project team or add your ideas for the blog search component in this issue. Should the blog pages have a search bar? Where could you add this component? Thanks for looking into this. /triage accepted
Thanks for reopening! I think it's nice to add a search component just like the documentation page. It enables readers to find the related articles when they meet unfamiliar topics in the blog post. Current search box in docs <img width="546" alt="Screen Shot 2021-03-22 at 0 05 52" src="https://user-"Proposed search box in blog page <img width="556" alt="Screen Shot 2021-03-22 at 0 05 34" src="https://user-"I think it's important to placing the search box in the same place with documentation like the above because it would give the consistent user experience to search and has less confusion. I'd like to make a PR which extract search input element as a hugo partial and place the partial in both places like the above screenshots.
Good. Have you created a PR?
No, I haven't yet. I hope to create a PR this week.
/assign