[zh]Update tasks pages(part-1) for links with '/zh/' prefix, using new prefix '/zh-cn/'
howieyuen
parent
e0d6f94bf6
commit
03cb15203a
|
|
@ -26,5 +26,5 @@ If you would like to write a task page, see
|
|||
[Creating a Documentation Pull Request](/docs/contribute/new-content/open-a-pr/).
|
||||
-->
|
||||
如果你希望编写一个任务页面，参考
|
||||
[创建一个文档拉取请求](/zh/docs/contribute/new-content/open-a-pr/)。
|
||||
[创建一个文档拉取请求](/zh-cn/docs/contribute/new-content/open-a-pr/)。
|
||||
|
||||
|
|
|
|||
|
|
@ -27,9 +27,9 @@ such as your desktop machine.
|
|||
-->
|
||||
## 访问集群上运行的服务
|
||||
|
||||
在 Kubernetes 里，[节点](/zh/docs/concepts/architecture/nodes/)、
|
||||
[Pod](/zh/docs/concepts/workloads/pods/) 和
|
||||
[服务](/zh/docs/concepts/services-networking/service/) 都有自己的 IP。
|
||||
在 Kubernetes 里，[节点](/zh-cn/docs/concepts/architecture/nodes/)、
|
||||
[Pod](/zh-cn/docs/concepts/workloads/pods/) 和
|
||||
[服务](/zh-cn/docs/concepts/services-networking/service/) 都有自己的 IP。
|
||||
许多情况下，集群上的节点 IP、Pod IP 和某些服务 IP 是路由不可达的，
|
||||
所以不能从集群之外访问它们，例如从你自己的台式机。
|
||||
|
||||
|
|
@ -57,7 +57,7 @@ You have several options for connecting to nodes, pods and services from outside
|
|||
-->
|
||||
- 通过公网 IP 访问服务
|
||||
- 使用类型为 `NodePort` 或 `LoadBalancer` 的服务，可以从外部访问它们。
|
||||
请查阅[服务](/zh/docs/concepts/services-networking/service/) 和
|
||||
请查阅[服务](/zh-cn/docs/concepts/services-networking/service/) 和
|
||||
[kubectl expose](/docs/reference/generated/kubectl/kubectl-commands/#expose) 文档。
|
||||
- 取决于你的集群环境，你可以仅把服务暴露在你的企业网络环境中，也可以将其暴露在
|
||||
因特网上。需要考虑暴露的服务是否安全，它是否有自己的用户认证？
|
||||
|
|
@ -142,7 +142,7 @@ at `https://192.0.2.1/api/v1/namespaces/kube-system/services/elasticsearch-loggi
|
|||
See [Access Clusters Using the Kubernetes API](/docs/tasks/administer-cluster/access-cluster-api/#accessing-the-cluster-api) for how to pass credentials or use kubectl proxy.
|
||||
-->
|
||||
{{< note >}}
|
||||
请参阅[使用 Kubernetes API 访问集群](/zh/docs/tasks/administer-cluster/access-cluster-api/#accessing-the-cluster-api)
|
||||
请参阅[使用 Kubernetes API 访问集群](/zh-cn/docs/tasks/administer-cluster/access-cluster-api/#accessing-the-cluster-api)
|
||||
了解如何传递凭据或如何使用 `kubectl proxy`。
|
||||
{{< /note >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@ Check the location and credentials that kubectl knows about with this command:
|
|||
当你第一次访问 Kubernetes API 的时候，我们建议你使用 Kubernetes CLI 工具 `kubectl`。
|
||||
|
||||
访问集群时，你需要知道集群的地址并且拥有访问的凭证。通常，这些在你通过
|
||||
[启动安装](/zh/docs/setup/)安装集群时都是自动安装好的，或者其他人安装时
|
||||
[启动安装](/zh-cn/docs/setup/)安装集群时都是自动安装好的，或者其他人安装时
|
||||
也应该提供了凭证和集群地址。
|
||||
|
||||
通过以下命令检查 kubectl 是否知道集群地址及凭证：
|
||||
|
|
@ -53,8 +53,8 @@ Many of the [examples](/docs/reference/kubectl/cheatsheet/) provide an introduct
|
|||
`kubectl`, and complete documentation is found in the
|
||||
[kubectl reference](/docs/reference/kubectl/).
|
||||
-->
|
||||
有许多[例子](/zh/docs/reference/kubectl/cheatsheet/)介绍了如何使用 kubectl，
|
||||
可以在 [kubectl 参考](/zh/docs/reference/kubectl/)中找到更完整的文档。
|
||||
有许多[例子](/zh-cn/docs/reference/kubectl/cheatsheet/)介绍了如何使用 kubectl，
|
||||
可以在 [kubectl 参考](/zh-cn/docs/reference/kubectl/)中找到更完整的文档。
|
||||
|
||||
<!--
|
||||
## Directly accessing the REST API
|
||||
|
|
@ -264,7 +264,7 @@ describes how a cluster admin can configure this.
|
|||
|
||||
在一些集群中，apiserver 不需要身份验证；它可能只服务于 localhost，或者被防火墙保护，
|
||||
这个没有一定的标准。
|
||||
[配置对 API 的访问](/zh/docs/concepts/security/controlling-access/)
|
||||
[配置对 API 的访问](/zh-cn/docs/concepts/security/controlling-access/)
|
||||
描述了集群管理员如何进行配置。此类方法可能与未来的高可用性支持相冲突。
|
||||
|
||||
<!--
|
||||
|
|
@ -297,7 +297,7 @@ Kubernetes 官方提供对 [Go](#go-client) 和 [Python](#python-client) 的客
|
|||
导入 API 定义，例如，`import "k8s.io/client-go/kubernetes"` 才是对的。
|
||||
|
||||
Go 客户端可以像 kubectl CLI 一样使用相同的
|
||||
[kubeconfig 文件](/zh/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
[kubeconfig 文件](/zh-cn/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
来定位和验证 apiserver。可参阅
|
||||
[示例](https://git.k8s.io/client-go/examples/out-of-cluster-client-configuration/main.go)。
|
||||
|
||||
|
|
@ -325,13 +325,13 @@ See documentation for other libraries for how they authenticate.
|
|||
以获得更详细的安装参数。
|
||||
|
||||
Python 客户端可以像 kubectl CLI 一样使用相同的
|
||||
[kubeconfig 文件](/zh/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
[kubeconfig 文件](/zh-cn/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
来定位和验证 apiserver，可参阅
|
||||
[示例](https://github.com/kubernetes-client/python/tree/master/examples)。
|
||||
|
||||
### 其它语言 {#other-languages}
|
||||
|
||||
目前有多个[客户端库](/zh/docs/reference/using-api/client-libraries/)
|
||||
目前有多个[客户端库](/zh-cn/docs/reference/using-api/client-libraries/)
|
||||
为其它语言提供访问 API 的方法。
|
||||
参阅其它库的相关文档以获取他们是如何验证的。
|
||||
|
||||
|
|
@ -349,7 +349,7 @@ to the API server are somewhat different.
|
|||
Please check [Accessing the API from within a Pod](/docs/tasks/run-application/access-api-from-pod/)
|
||||
for more details.
|
||||
-->
|
||||
请参阅[从 Pod 中访问 API](/zh/docs/tasks/run-application/access-api-from-pod/)
|
||||
请参阅[从 Pod 中访问 API](/zh-cn/docs/tasks/run-application/access-api-from-pod/)
|
||||
了解更多详情。
|
||||
|
||||
<!--
|
||||
|
|
@ -364,7 +364,7 @@ For information about connecting to other services running on a Kubernetes clust
|
|||
|
||||
上一节介绍了如何连接到 Kubernetes API 服务器。
|
||||
有关连接到 Kubernetes 集群上运行的其他服务的信息，请参阅
|
||||
[访问集群服务](/zh/docs/tasks/access-application-cluster/access-cluster-services/)。
|
||||
[访问集群服务](/zh-cn/docs/tasks/access-application-cluster/access-cluster-services/)。
|
||||
|
||||
<!--
|
||||
## Requesting redirects
|
||||
|
|
@ -414,7 +414,7 @@ There are several different proxies you may encounter when using Kubernetes:
|
|||
- can be used to reach a Node, Pod, or Service
|
||||
- does load balancing when used to reach a Service
|
||||
-->
|
||||
2. [apiserver 代理](/zh/docs/tasks/access-application-cluster/access-cluster-services/#discovering-builtin-services)：
|
||||
2. [apiserver 代理](/zh-cn/docs/tasks/access-application-cluster/access-cluster-services/#discovering-builtin-services)：
|
||||
|
||||
- 内置于 apiserver 中
|
||||
- 将集群外部的用户连接到集群 IP，否则这些 IP 可能无法访问
|
||||
|
|
@ -433,7 +433,7 @@ There are several different proxies you may encounter when using Kubernetes:
|
|||
- provides load balancing
|
||||
- is only used to reach services
|
||||
-->
|
||||
3. [kube proxy](/zh/docs/concepts/services-networking/service/#ips-and-vips)：
|
||||
3. [kube proxy](/zh-cn/docs/concepts/services-networking/service/#ips-and-vips)：
|
||||
|
||||
- 运行在每个节点上
|
||||
- 代理 UDP 和 TCP
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ between containers.
|
|||
-->
|
||||
本文旨在说明如何让一个 Pod 内的两个容器使用一个卷（Volume）进行通信。
|
||||
参阅如何让两个进程跨容器通过
|
||||
[共享进程名字空间](/zh/docs/tasks/configure-pod-container/share-process-namespace/)。
|
||||
[共享进程名字空间](/zh-cn/docs/tasks/configure-pod-container/share-process-namespace/)。
|
||||
|
||||
## {{% heading "prerequisites" %}}
|
||||
|
||||
|
|
@ -205,8 +205,8 @@ the shared Volume is lost.
|
|||
-->
|
||||
* 进一步了解[复合容器的模式](https://kubernetes.io/blog/2015/06/the-distributed-system-toolkit-patterns.html)
|
||||
* 学习[模块化架构中的复合容器](https://www.slideshare.net/Docker/slideshare-burns)
|
||||
* 参见[配置 Pod 使用卷来存储数据](/zh/docs/tasks/configure-pod-container/configure-volume-storage/)
|
||||
* 参考[在 Pod 中的容器之间共享进程命名空间](/zh/docs/tasks/configure-pod-container/share-process-namespace/)
|
||||
* 参见[配置 Pod 使用卷来存储数据](/zh-cn/docs/tasks/configure-pod-container/configure-volume-storage/)
|
||||
* 参考[在 Pod 中的容器之间共享进程命名空间](/zh-cn/docs/tasks/configure-pod-container/share-process-namespace/)
|
||||
* 参考 [Volume](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#volume-v1-core)
|
||||
* 参考 [Pod](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#pod-v1-core)
|
||||
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ cluster's API server.
|
|||
要检查 {{< glossary_tooltip text="kubectl" term_id="kubectl" >}} 是否安装，
|
||||
执行 `kubectl version --client` 命令。
|
||||
kubectl 的版本应该与集群的 API 服务器
|
||||
[使用同一次版本号](/zh/releases/version-skew-policy/#kubectl)。
|
||||
[使用同一次版本号](/zh-cn/releases/version-skew-policy/#kubectl)。
|
||||
|
||||
<!-- steps -->
|
||||
|
||||
|
|
@ -480,7 +480,7 @@ For more information about how kubeconfig files are merged, see
|
|||
[Organizing Cluster Access Using kubeconfig Files](/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
-->
|
||||
关于 kubeconfig 文件如何合并的更多信息，请参考
|
||||
[使用 kubeconfig 文件组织集群访问](/zh/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
[使用 kubeconfig 文件组织集群访问](/zh-cn/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
|
||||
<!--
|
||||
## Explore the $HOME/.kube directory
|
||||
|
|
@ -564,6 +564,6 @@ $Env:KUBECONFIG=$ENV:KUBECONFIG_SAVED
|
|||
* [kubectl config](/docs/reference/generated/kubectl/kubectl-commands#config)
|
||||
-->
|
||||
|
||||
* [使用 kubeconfig 文件组织集群访问](/zh/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
* [使用 kubeconfig 文件组织集群访问](/zh-cn/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
* [kubectl config](/docs/reference/generated/kubectl/kubectl-commands#config)
|
||||
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ kubeadm 默认会安装 CoreDNS。
|
|||
For more information on how to configure CoreDNS for a Kubernetes cluster, see the [Customizing DNS Service](/docs/tasks/administer-cluster/dns-custom-nameservers/). An example demonstrating how to use Kubernetes DNS with kube-dns, see the [Kubernetes DNS sample plugin](https://github.com/kubernetes/examples/tree/master/staging/cluster-dns)
|
||||
-->
|
||||
要了解关于如何为 Kubernetes 集群配置 CoreDNS 的更多信息，参阅
|
||||
[定制 DNS 服务](/zh/docs/tasks/administer-cluster/dns-custom-nameservers/)。
|
||||
[定制 DNS 服务](/zh-cn/docs/tasks/administer-cluster/dns-custom-nameservers/)。
|
||||
关于如何利用 kube-dns 配置 kubernetes DNS 的演示例子，参阅
|
||||
[Kubernetes DNS 插件示例](https://github.com/kubernetes/examples/tree/master/staging/cluster-dns)。
|
||||
|
||||
|
|
|
|||
|
|
@ -48,9 +48,9 @@ This task uses
|
|||
require a supported environment. If your environment does not support this, you can use a Service of type
|
||||
[NodePort](/docs/concepts/services-networking/service/#type-nodeport) instead.
|
||||
-->
|
||||
本任务使用[外部负载均衡服务](/zh/docs/tasks/access-application-cluster/create-external-load-balancer/)，
|
||||
本任务使用[外部负载均衡服务](/zh-cn/docs/tasks/access-application-cluster/create-external-load-balancer/)，
|
||||
所以需要对应的可支持此功能的环境。如果你的环境不能支持，你可以使用
|
||||
[NodePort](/zh/docs/concepts/services-networking/service/#type-nodeport)
|
||||
[NodePort](/zh-cn/docs/concepts/services-networking/service/#type-nodeport)
|
||||
类型的服务代替。
|
||||
|
||||
<!-- lessoncontent -->
|
||||
|
|
@ -246,7 +246,7 @@ so that you can change the configuration more easily.
|
|||
这个 nginx 配置文件是被打包在
|
||||
[容器镜像](/examples/service/access/Dockerfile) 里的。
|
||||
更好的方法是使用
|
||||
[ConfigMap](/zh/docs/tasks/configure-pod-container/configure-pod-configmap/)，
|
||||
[ConfigMap](/zh-cn/docs/tasks/configure-pod-container/configure-pod-configmap/)，
|
||||
这样的话你可以更轻易地更改配置。
|
||||
{{< /note >}}
|
||||
|
||||
|
|
@ -343,7 +343,7 @@ kubectl delete deployment frontend backend
|
|||
* Learn more about [ConfigMaps](/docs/tasks/configure-pod-container/configure-pod-configmap/)
|
||||
* Learn more about [DNS for Service and Pods](/docs/concepts/services-networking/dns-pod-service/)
|
||||
-->
|
||||
* 进一步了解 [Service](/zh/docs/concepts/services-networking/service/)
|
||||
* 进一步了解 [ConfigMap](/zh/docs/tasks/configure-pod-container/configure-pod-configmap/)
|
||||
* 进一步了解 [Service 和 Pods 的 DNS](/zh/docs/concepts/services-networking/dns-pod-service/)
|
||||
* 进一步了解 [Service](/zh-cn/docs/concepts/services-networking/service/)
|
||||
* 进一步了解 [ConfigMap](/zh-cn/docs/tasks/configure-pod-container/configure-pod-configmap/)
|
||||
* 进一步了解 [Service 和 Pods 的 DNS](/zh-cn/docs/concepts/services-networking/dns-pod-service/)
|
||||
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ For more information, check the [Ingress](/docs/concepts/services-networking/ing
|
|||
documentation.
|
||||
-->
|
||||
你还可以使用 {{< glossary_tooltip text="Ingress" term_id="ingress" >}} 代替 Service。
|
||||
更多信息，请参阅 [Ingress](/zh/docs/concepts/services-networking/ingress/) 文档。
|
||||
更多信息，请参阅 [Ingress](/zh-cn/docs/concepts/services-networking/ingress/) 文档。
|
||||
|
||||
## {{% heading "prerequisites" %}}
|
||||
|
||||
|
|
@ -325,7 +325,7 @@ Kubernetes 控制平面自动创建外部负载均衡器、健康检查（如果
|
|||
* Read about [Ingress](/docs/concepts/services-networking/ingress/)
|
||||
* Read [Connecting Applications with Services](/docs/concepts/services-networking/connect-applications-service/)
|
||||
-->
|
||||
* 阅读[服务](/zh/docs/concepts/services-networking/service/)
|
||||
* 阅读 [Ingress](/zh/docs/concepts/services-networking/ingress/)
|
||||
* 阅读[使用 Service 连接到应用](/zh/docs/concepts/services-networking/connect-applications-service/)
|
||||
* 阅读[服务](/zh-cn/docs/concepts/services-networking/service/)
|
||||
* 阅读 [Ingress](/zh-cn/docs/concepts/services-networking/ingress/)
|
||||
* 阅读[使用 Service 连接到应用](/zh-cn/docs/concepts/services-networking/connect-applications-service/)
|
||||
|
||||
|
|
|
|||
|
|
@ -19,9 +19,9 @@ to services in a cluster. An [Ingress controller](/docs/concepts/services-networ
|
|||
|
||||
This page shows you how to set up a simple Ingress which routes requests to Service web or web2 depending on the HTTP URI.
|
||||
-->
|
||||
[Ingress](/zh/docs/concepts/services-networking/ingress/)是一种 API 对象，其中定义了一些规则使得集群中的
|
||||
[Ingress](/zh-cn/docs/concepts/services-networking/ingress/)是一种 API 对象，其中定义了一些规则使得集群中的
|
||||
服务可以从集群外访问。
|
||||
[Ingress 控制器](/zh/docs/concepts/services-networking/ingress-controllers/)
|
||||
[Ingress 控制器](/zh-cn/docs/concepts/services-networking/ingress-controllers/)
|
||||
负责满足 Ingress 中所设置的规则。
|
||||
|
||||
本节为你展示如何配置一个简单的 Ingress，根据 HTTP URI 将服务请求路由到
|
||||
|
|
@ -45,7 +45,7 @@ This page shows you how to set up a simple Ingress which routes requests to Serv
|
|||
: {{< kat-button >}}
|
||||
|
||||
本地
|
||||
: 如果已经在本地[安装Minikube](/zh/docs/tasks/tools/#minikube)，
|
||||
: 如果已经在本地[安装Minikube](/zh-cn/docs/tasks/tools/#minikube)，
|
||||
请运行 `minikube start` 创建一个集群。
|
||||
|
||||
<!--
|
||||
|
|
@ -438,6 +438,6 @@ The following manifest defines an Ingress that sends traffic to your Service via
|
|||
* Read more about [Services](/docs/concepts/services-networking/service/)
|
||||
-->
|
||||
|
||||
* 进一步了解 [Ingress](/zh/docs/concepts/services-networking/ingress/)。
|
||||
* 进一步了解 [Ingress 控制器](/zh/docs/concepts/services-networking/ingress-controllers/)
|
||||
* 进一步了解 [服务](/zh/docs/concepts/services-networking/service/)
|
||||
* 进一步了解 [Ingress](/zh-cn/docs/concepts/services-networking/ingress/)。
|
||||
* 进一步了解 [Ingress 控制器](/zh-cn/docs/concepts/services-networking/ingress-controllers/)
|
||||
* 进一步了解 [服务](/zh-cn/docs/concepts/services-networking/service/)
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@ of Containers for each.
|
|||
- 使用 `kubectl get pods --all-namespaces` 获取所有命名空间下的所有 Pod
|
||||
- 使用 `-o jsonpath={.items[*].spec.containers[*].image}` 来格式化输出，以仅包含容器镜像名称。
|
||||
这将以递归方式从返回的 json 中解析出 `image` 字段。
|
||||
- 参阅 [jsonpath 说明](/zh/docs/reference/kubectl/jsonpath/)
|
||||
- 参阅 [jsonpath 说明](/zh-cn/docs/reference/kubectl/jsonpath/)
|
||||
获取更多关于如何使用 jsonpath 的信息。
|
||||
- 使用标准化工具来格式化输出：`tr`, `sort`, `uniq`
|
||||
- 使用 `tr` 以用换行符替换空格
|
||||
|
|
@ -173,6 +173,6 @@ kubectl get pods --all-namespaces -o go-template --template="{{range .items}}{{r
|
|||
-->
|
||||
### 参考
|
||||
|
||||
* [Jsonpath](/zh/docs/reference/kubectl/jsonpath/) 参考指南
|
||||
* [Jsonpath](/zh-cn/docs/reference/kubectl/jsonpath/) 参考指南
|
||||
* [Go template](https://golang.org/pkg/text/template/) 参考指南
|
||||
|
||||
|
|
|
|||
|
|
@ -70,9 +70,9 @@ Here is the configuration file for the application Deployment:
|
|||
kubectl apply -f https://k8s.io/examples/service/access/hello-application.yaml
|
||||
```
|
||||
|
||||
上面的命令创建一个 [Deployment](/zh/docs/concepts/workloads/controllers/deployment/) 对象
|
||||
和一个关联的 [ReplicaSet](/zh/docs/concepts/workloads/controllers/replicaset/) 对象。
|
||||
这个 ReplicaSet 有两个 [Pod](/zh/docs/concepts/workloads/pods/)，
|
||||
上面的命令创建一个 [Deployment](/zh-cn/docs/concepts/workloads/controllers/deployment/) 对象
|
||||
和一个关联的 [ReplicaSet](/zh-cn/docs/concepts/workloads/controllers/replicaset/) 对象。
|
||||
这个 ReplicaSet 有两个 [Pod](/zh-cn/docs/concepts/workloads/pods/)，
|
||||
每个 Pod 都运行着 Hello World 应用。
|
||||
|
||||
<!--
|
||||
|
|
@ -211,7 +211,7 @@ to create a Service.
|
|||
## 使用服务配置文件
|
||||
|
||||
作为 `kubectl expose` 的替代方法，你可以使用
|
||||
[服务配置文件](/zh/docs/concepts/services-networking/service/) 来创建服务。
|
||||
[服务配置文件](/zh-cn/docs/concepts/services-networking/service/) 来创建服务。
|
||||
|
||||
## {{% heading "cleanup" %}}
|
||||
|
||||
|
|
@ -240,5 +240,5 @@ kubectl delete deployment hello-world
|
|||
Learn more about
|
||||
[connecting applications with services](/docs/concepts/services-networking/connect-applications-service/).
|
||||
-->
|
||||
- 进一步了解[通过服务连接应用](/zh/docs/concepts/services-networking/connect-applications-service/)。
|
||||
- 进一步了解[通过服务连接应用](/zh-cn/docs/concepts/services-networking/connect-applications-service/)。
|
||||
|
||||
|
|
|
|||
|
|
@ -126,7 +126,7 @@ When you access Dashboard on an empty cluster, you'll see the welcome page. This
|
|||
当访问空集群的 Dashboard 时，你会看到欢迎界面。
|
||||
页面包含一个指向此文档的链接，以及一个用于部署第一个应用程序的按钮。
|
||||
此外，你可以看到在默认情况下有哪些默认系统应用运行在 `kube-system`
|
||||
[名字空间](/zh/docs/tasks/administer-cluster/namespaces/) 中，比如 Dashboard 自己。
|
||||
[名字空间](/zh-cn/docs/tasks/administer-cluster/namespaces/) 中，比如 Dashboard 自己。
|
||||
|
||||
<!--
|
||||
|
||||
|
|
@ -163,13 +163,13 @@ The deploy wizard expects that you provide the following information:
|
|||
- **App name** (mandatory): Name for your application. A [label](/docs/concepts/overview/working-with-objects/labels/) with the name will be added to the Deployment and Service, if any, that will be deployed.
|
||||
-->
|
||||
- **应用名称**（必填）：应用的名称。内容为`应用名称`的
|
||||
[标签](/zh/docs/concepts/overview/working-with-objects/labels/)
|
||||
[标签](/zh-cn/docs/concepts/overview/working-with-objects/labels/)
|
||||
会被添加到任何将被部署的 Deployment 和 Service。
|
||||
|
||||
<!--
|
||||
The application name must be unique within the selected Kubernetes [namespace](/docs/tasks/administer-cluster/namespaces/). It must start with a lowercase character, and end with a lowercase character or a number, and contain only lowercase letters, numbers and dashes (-). It is limited to 24 characters. Leading and trailing spaces are ignored.
|
||||
-->
|
||||
在选定的 Kubernetes [名字空间](/zh/docs/tasks/administer-cluster/namespaces/) 中，
|
||||
在选定的 Kubernetes [名字空间](/zh-cn/docs/tasks/administer-cluster/namespaces/) 中，
|
||||
应用名称必须唯一。必须由小写字母开头，以数字或者小写字母结尾，
|
||||
并且只含有小写字母、数字和中划线（-）。小于等于24个字符。开头和结尾的空格会被忽略。
|
||||
|
||||
|
|
@ -177,7 +177,7 @@ The deploy wizard expects that you provide the following information:
|
|||
- **Container image** (mandatory): The URL of a public Docker [container image](/docs/concepts/containers/images/) on any registry, or a private image (commonly hosted on the Google Container Registry or Docker Hub). The container image specification must end with a colon.
|
||||
-->
|
||||
- **容器镜像**（必填）：公共镜像仓库上的 Docker
|
||||
[容器镜像](/zh/docs/concepts/containers/images/) 或者私有镜像仓库
|
||||
[容器镜像](/zh-cn/docs/concepts/containers/images/) 或者私有镜像仓库
|
||||
（通常是 Google Container Registry 或者 Docker Hub）的 URL。容器镜像参数说明必须以冒号结尾。
|
||||
|
||||
<!--
|
||||
|
|
@ -189,14 +189,14 @@ The deploy wizard expects that you provide the following information:
|
|||
A [Deployment](/docs/concepts/workloads/controllers/deployment/) will be created to
|
||||
maintain the desired number of Pods across your cluster.
|
||||
-->
|
||||
系统会创建一个 [Deployment](/zh/docs/concepts/workloads/controllers/deployment/)
|
||||
系统会创建一个 [Deployment](/zh-cn/docs/concepts/workloads/controllers/deployment/)
|
||||
以保证集群中运行期望的 Pod 数量。
|
||||
|
||||
<!--
|
||||
- **Service** (optional): For some parts of your application (e.g. frontends) you may want to expose a [Service](/docs/concepts/services-networking/service/) onto an external, maybe public IP address outside of your cluster (external Service).
|
||||
-->
|
||||
- **服务**（可选）：对于部分应用（比如前端），你可能想对外暴露一个
|
||||
[Service](/zh/docs/concepts/services-networking/service/) ，这个 Service
|
||||
[Service](/zh-cn/docs/concepts/services-networking/service/) ，这个 Service
|
||||
可能用的是集群之外的公网 IP 地址（外部 Service）。
|
||||
|
||||
<!--
|
||||
|
|
@ -234,14 +234,14 @@ If needed, you can expand the **Advanced options** section where you can specify
|
|||
to the Deployment and displayed in the application's details.
|
||||
-->
|
||||
- **描述**：这里你输入的文本会作为一个
|
||||
[注解](/zh/docs/concepts/overview/working-with-objects/annotations/)
|
||||
[注解](/zh-cn/docs/concepts/overview/working-with-objects/annotations/)
|
||||
添加到 Deployment，并显示在应用的详细信息中。
|
||||
|
||||
<!--
|
||||
- **Labels**: Default [labels](/docs/concepts/overview/working-with-objects/labels/) to be used for your application are application name and version. You can specify additional labels to be applied to the Deployment, Service (if any), and Pods, such as release, environment, tier, partition, and release track.
|
||||
-->
|
||||
- **标签**：应用默认使用的
|
||||
[标签](/zh/docs/concepts/overview/working-with-objects/labels/) 是应用名称和版本。
|
||||
[标签](/zh-cn/docs/concepts/overview/working-with-objects/labels/) 是应用名称和版本。
|
||||
你可以为 Deployment、Service（如果有）定义额外的标签，比如 release（版本）、
|
||||
environment（环境）、tier（层级）、partition（分区） 和 release track（版本跟踪）。
|
||||
|
||||
|
|
@ -260,7 +260,7 @@ If needed, you can expand the **Advanced options** section where you can specify
|
|||
-->
|
||||
- **名字空间**：Kubernetes 支持多个虚拟集群依附于同一个物理集群。
|
||||
这些虚拟集群被称为
|
||||
[名字空间](/zh/docs/tasks/administer-cluster/namespaces/)，
|
||||
[名字空间](/zh-cn/docs/tasks/administer-cluster/namespaces/)，
|
||||
可以让你将资源划分为逻辑命名的组。
|
||||
|
||||
<!--
|
||||
|
|
@ -287,7 +287,7 @@ If needed, you can expand the **Advanced options** section where you can specify
|
|||
- **Image Pull Secret**: In case the specified Docker container image is private, it may require [pull secret](/docs/concepts/configuration/secret/) credentials.
|
||||
-->
|
||||
- **镜像拉取 Secret**：如果要使用私有的 Docker 容器镜像，需要拉取
|
||||
[Secret](/zh/docs/concepts/configuration/secret/) 凭证。
|
||||
[Secret](/zh-cn/docs/concepts/configuration/secret/) 凭证。
|
||||
|
||||
<!--
|
||||
Dashboard offers all available secrets in a dropdown list, and allows you to create a new secret.
|
||||
|
|
@ -299,7 +299,7 @@ If needed, you can expand the **Advanced options** section where you can specify
|
|||
Dashboard 通过下拉菜单提供所有可用的 Secret，并允许你创建新的 Secret。
|
||||
Secret 名称必须遵循 DNS 域名语法，比如 `new.image-pull.secret`。
|
||||
Secret 的内容必须是 base64 编码的，并且在一个
|
||||
[`.dockercfg`](/zh/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod)
|
||||
[`.dockercfg`](/zh-cn/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod)
|
||||
文件中声明。Secret 名称最大可以包含 253 个字符。
|
||||
|
||||
<!--
|
||||
|
|
@ -313,21 +313,21 @@ If needed, you can expand the **Advanced options** section where you can specify
|
|||
- **CPU requirement (cores)** and **Memory requirement (MiB)**: You can specify the minimum [resource limits](/docs/tasks/configure-pod-container/limit-range/) for the container. By default, Pods run with unbounded CPU and memory limits.
|
||||
-->
|
||||
- **CPU 需求（核数）**和**内存需求（MiB）**：你可以为容器定义最小的
|
||||
[资源限制](/zh/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/)。
|
||||
[资源限制](/zh-cn/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/)。
|
||||
默认情况下，Pod 没有 CPU 和内存限制。
|
||||
|
||||
<!--
|
||||
- **Run command** and **Run command arguments**: By default, your containers run the specified Docker image's default [entrypoint command](/docs/user-guide/containers/#containers-and-commands). You can use the command options and arguments to override the default.
|
||||
-->
|
||||
- **运行命令**和**运行命令参数**：默认情况下，你的容器会运行 Docker 镜像的默认
|
||||
[入口命令](/zh/docs/tasks/inject-data-application/define-command-argument-container/)。
|
||||
[入口命令](/zh-cn/docs/tasks/inject-data-application/define-command-argument-container/)。
|
||||
你可以使用 command 选项覆盖默认值。
|
||||
|
||||
<!--
|
||||
- **Run as privileged**: This setting determines whether processes in [privileged containers](/docs/user-guide/pods/#privileged-mode-for-pod-containers) are equivalent to processes running as root on the host. Privileged containers can make use of capabilities like manipulating the network stack and accessing devices.
|
||||
-->
|
||||
- **以特权模式运行**：这个设置决定了在
|
||||
[特权容器](/zh/docs/concepts/workloads/pods/#privileged-mode-for-containers)
|
||||
[特权容器](/zh-cn/docs/concepts/workloads/pods/#privileged-mode-for-containers)
|
||||
中运行的进程是否像主机中使用 root 运行的进程一样。
|
||||
特权容器可以使用诸如操纵网络堆栈和访问设备的功能。
|
||||
|
||||
|
|
@ -335,7 +335,7 @@ If needed, you can expand the **Advanced options** section where you can specify
|
|||
- **Environment variables**: Kubernetes exposes Services through [environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/). You can compose environment variable or pass arguments to your commands using the values of environment variables. They can be used in applications to find a Service. Values can reference other variables using the `$(VAR_NAME)` syntax.
|
||||
-->
|
||||
- **环境变量**：Kubernetes 通过
|
||||
[环境变量](/zh/docs/tasks/inject-data-application/environment-variable-expose-pod-information/)
|
||||
[环境变量](/zh-cn/docs/tasks/inject-data-application/environment-variable-expose-pod-information/)
|
||||
暴露 Service。你可以构建环境变量，或者将环境变量的值作为参数传递给你的命令。
|
||||
它们可以被应用用于查找 Service。值可以通过 `$(VAR_NAME)` 语法关联其他变量。
|
||||
|
||||
|
|
@ -350,7 +350,7 @@ The manifests use the Kubernetes [API](/docs/concepts/overview/kubernetes-api/)
|
|||
|
||||
Kubernetes 支持声明式配置。所有的配置都存储在清单文件
|
||||
（YAML 或者 JSON 配置文件）中。这些
|
||||
清单使用 Kubernetes [API](/zh/docs/concepts/overview/kubernetes-api/) 定义的资源模式。
|
||||
清单使用 Kubernetes [API](/zh-cn/docs/concepts/overview/kubernetes-api/) 定义的资源模式。
|
||||
|
||||
<!--
|
||||
As an alternative to specifying application details in the deploy wizard,
|
||||
|
|
|
|||
|
|
@ -42,7 +42,7 @@ a [Getting started guide](/docs/setup/),
|
|||
or someone else setup the cluster and provided you with credentials and a location.
|
||||
-->
|
||||
要访问集群，你需要知道集群位置并拥有访问它的凭证。
|
||||
通常，当你完成[入门指南](/zh/docs/setup/)时，这会自动设置完成，或者由其他人设置好集群并将凭证和位置提供给你。
|
||||
通常，当你完成[入门指南](/zh-cn/docs/setup/)时，这会自动设置完成，或者由其他人设置好集群并将凭证和位置提供给你。
|
||||
|
||||
<!--
|
||||
Check the location and credentials that kubectl knows about with this command:
|
||||
|
|
@ -59,7 +59,7 @@ kubectl. Complete documentation is found in the [kubectl manual](/docs/reference
|
|||
-->
|
||||
|
||||
许多[样例](https://github.com/kubernetes/examples/tree/master/)
|
||||
提供了使用 kubectl 的介绍。完整文档请见 [kubectl 手册](/zh/docs/reference/kubectl/)。
|
||||
提供了使用 kubectl 的介绍。完整文档请见 [kubectl 手册](/zh-cn/docs/reference/kubectl/)。
|
||||
|
||||
<!--
|
||||
### Directly accessing the REST API
|
||||
|
|
@ -222,7 +222,7 @@ describes how you can configure this as a cluster administrator.
|
|||
-->
|
||||
在一些集群中，API 服务器不需要身份认证；它运行在本地，或由防火墙保护着。
|
||||
对此并没有一个标准。
|
||||
[配置对 API 的访问](/zh/docs/concepts/security/controlling-access/)
|
||||
[配置对 API 的访问](/zh-cn/docs/concepts/security/controlling-access/)
|
||||
讲解了作为集群管理员可如何对此进行配置。
|
||||
|
||||
<!--
|
||||
|
|
@ -235,7 +235,7 @@ Kubernetes officially supports client libraries for [Go](#go-client), [Python](#
|
|||
Kubernetes 官方支持 [Go](#go-client)、[Python](#python-client)、[Java](#java-client)、
|
||||
[dotnet](#dotnet-client)、[JavaScript](#javascript-client) 和 [Haskell](#haskell-client)
|
||||
语言的客户端库。还有一些其他客户端库由对应作者而非 Kubernetes 团队提供并维护。
|
||||
参考[客户端库](/zh/docs/reference/using-api/client-libraries/)了解如何使用其他语言
|
||||
参考[客户端库](/zh-cn/docs/reference/using-api/client-libraries/)了解如何使用其他语言
|
||||
来访问 API 以及如何执行身份认证。
|
||||
|
||||
<!-- #### Go client -->
|
||||
|
|
@ -264,7 +264,7 @@ The Go client can use the same [kubeconfig file](/docs/concepts/cluster-administ
|
|||
as the kubectl CLI does to locate and authenticate to the API server. See this [example](https://git.k8s.io/client-go/examples/out-of-cluster-client-configuration/main.go):
|
||||
-->
|
||||
Go 客户端可以使用与 kubectl 命令行工具相同的
|
||||
[kubeconfig 文件](/zh/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
[kubeconfig 文件](/zh-cn/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
定位和验证 API 服务器。参见这个
|
||||
[例子](https://git.k8s.io/client-go/examples/out-of-cluster-client-configuration/main.go)：
|
||||
|
||||
|
|
@ -295,7 +295,7 @@ func main() {
|
|||
If the application is deployed as a Pod in the cluster, see [Accessing the API from within a Pod](/docs/tasks/access-application-cluster/access-cluster/#accessing-the-api-from-a-pod).
|
||||
-->
|
||||
如果该应用程序部署为集群中的一个
|
||||
Pod，请参阅[从 Pod 内访问 API](/zh/docs/tasks/access-application-cluster/access-cluster/#accessing-the-api-from-a-pod)。
|
||||
Pod，请参阅[从 Pod 内访问 API](/zh-cn/docs/tasks/access-application-cluster/access-cluster/#accessing-the-api-from-a-pod)。
|
||||
|
||||
<!-- #### Python client -->
|
||||
#### Python 客户端 {#python-client}
|
||||
|
|
@ -312,7 +312,7 @@ The Python client can use the same [kubeconfig file](/docs/concepts/cluster-admi
|
|||
as the kubectl CLI does to locate and authenticate to the API server. See this [example](https://github.com/kubernetes-client/python/blob/master/examples/out_of_cluster_config.py):
|
||||
-->
|
||||
Python 客户端可以使用与 kubectl 命令行工具相同的
|
||||
[kubeconfig 文件](/zh/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
[kubeconfig 文件](/zh-cn/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
定位和验证 API 服务器。参见这个
|
||||
[例子](https://github.com/kubernetes-client/python/blob/master/examples/out_of_cluster_config.py)：
|
||||
|
||||
|
|
@ -355,7 +355,7 @@ as the kubectl CLI does to locate and authenticate to the API server. See this [
|
|||
了解当前支持的版本。
|
||||
|
||||
Java 客户端可以使用 kubectl 命令行所使用的
|
||||
[kubeconfig 文件](/zh/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
[kubeconfig 文件](/zh-cn/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
以定位 API 服务器并向其认证身份。
|
||||
参看此[示例](https://github.com/kubernetes-client/java/blob/master/examples/src/main/java/io/kubernetes/client/examples/KubeConfigFileClientExample.java)：
|
||||
|
||||
|
|
@ -421,7 +421,7 @@ as the kubectl CLI does to locate and authenticate to the API server. See this [
|
|||
参见[.Net 客户端库页面](https://github.com/kubernetes-client/csharp)了解更多安装选项。
|
||||
关于可支持的版本，参见[https://github.com/kubernetes-client/csharp/releases](https://github.com/kubernetes-client/csharp/releases)。
|
||||
|
||||
.Net 客户端可以使用与 kubectl CLI 相同的 [kubeconfig 文件](/zh/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
.Net 客户端可以使用与 kubectl CLI 相同的 [kubeconfig 文件](/zh-cn/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
来定位并验证 API 服务器。
|
||||
参见[样例](https://github.com/kubernetes-client/csharp/blob/master/examples/simple/PodList.cs):
|
||||
|
||||
|
|
@ -468,7 +468,7 @@ as the kubectl CLI does to locate and authenticate to the API server. See this [
|
|||
参考[https://github.com/kubernetes-client/javascript/releases](https://github.com/kubernetes-client/javascript/releases)了解可支持的版本。
|
||||
|
||||
JavaScript 客户端可以使用 kubectl 命令行所使用的
|
||||
[kubeconfig 文件](/zh/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
[kubeconfig 文件](/zh-cn/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
以定位 API 服务器并向其认证身份。
|
||||
参见[此例](https://github.com/kubernetes-client/javascript/blob/master/examples/example.js)：
|
||||
|
||||
|
|
@ -499,7 +499,7 @@ as the kubectl CLI does to locate and authenticate to the API server. See this [
|
|||
|
||||
[Haskell 客户端](https://github.com/kubernetes-client/haskell)
|
||||
可以使用 kubectl 命令行所使用的
|
||||
[kubeconfig 文件](/zh/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
[kubeconfig 文件](/zh-cn/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
|
||||
以定位 API 服务器并向其认证身份。
|
||||
参见[此例](https://github.com/kubernetes-client/haskell/blob/master/kubernetes-client/example/App.hs)：
|
||||
|
||||
|
|
@ -519,4 +519,4 @@ exampleWithKubeConfig = do
|
|||
<!--
|
||||
* [Accessing the Kubernetes API from a Pod](/docs/tasks/run-application/access-api-from-pod/)
|
||||
-->
|
||||
* [从 Pod 中访问 API](/zh/docs/tasks/run-application/access-api-from-pod/)
|
||||
* [从 Pod 中访问 API](/zh-cn/docs/tasks/run-application/access-api-from-pod/)
|
||||
|
|
|
|||
|
|
@ -369,5 +369,5 @@ x509 certificates to use for authentication as documented
|
|||
[here](/docs/tasks/tls/managing-tls-in-a-cluster).
|
||||
-->
|
||||
你可以通过 `certificates.k8s.io` API 提供 x509 证书，用来做身份验证，
|
||||
如[本](/zh/docs/tasks/tls/managing-tls-in-a-cluster)文档所述。
|
||||
如[本](/zh-cn/docs/tasks/tls/managing-tls-in-a-cluster)文档所述。
|
||||
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ for details.
|
|||
取决于安装模式，你的 Kubernetes 集群可能和一个被标记为默认的已有 StorageClass 一起部署。
|
||||
这个默认的 StorageClass 以后将被用于动态的为没有特定存储类需求的 PersistentVolumeClaims
|
||||
配置存储。更多细节请查看
|
||||
[PersistentVolumeClaim 文档](/zh/docs/concepts/storage/persistent-volumes/#perspersistentvolumeclaims)。
|
||||
[PersistentVolumeClaim 文档](/zh-cn/docs/concepts/storage/persistent-volumes/#perspersistentvolumeclaims)。
|
||||
|
||||
<!--
|
||||
The pre-installed default StorageClass may not fit well with your expected workload;
|
||||
|
|
@ -150,5 +150,5 @@ for details about addon manager and how to disable individual addons.
|
|||
<!--
|
||||
* Learn more about [PersistentVolumes](/docs/concepts/storage/persistent-volumes/).
|
||||
-->
|
||||
* 进一步了解 [PersistentVolumes](/zh/docs/concepts/storage/persistent-volumes/)
|
||||
* 进一步了解 [PersistentVolumes](/zh-cn/docs/concepts/storage/persistent-volumes/)
|
||||
|
||||
|
|
|
|||
|
|
@ -136,8 +136,8 @@ PersistentVolumes 可以有多种回收策略，包括 "Retain"、"Recycle" 和
|
|||
* Learn more about [PersistentVolumes](/docs/concepts/storage/persistent-volumes/).
|
||||
* Learn more about [PersistentVolumeClaims](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims).
|
||||
-->
|
||||
* 进一步了解 [PersistentVolumes](/zh/docs/concepts/storage/persistent-volumes/)
|
||||
* 进一步了解 [PersistentVolumeClaims](/zh/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims)
|
||||
* 进一步了解 [PersistentVolumes](/zh-cn/docs/concepts/storage/persistent-volumes/)
|
||||
* 进一步了解 [PersistentVolumeClaims](/zh-cn/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims)
|
||||
|
||||
### 参考 {#reference}
|
||||
|
||||
|
|
|
|||
|
|
@ -66,10 +66,10 @@ Once you have upgraded the cluster, remember to
|
|||
-->
|
||||
如果你的集群是使用 `kubeadm` 安装工具部署而来，
|
||||
那么升级集群的详细信息，请参阅
|
||||
[升级 kubeadm 集群](/zh/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/)。
|
||||
[升级 kubeadm 集群](/zh-cn/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/)。
|
||||
|
||||
升级集群之后，要记得
|
||||
[安装最新版本的 `kubectl`](/zh/docs/tasks/tools/).
|
||||
[安装最新版本的 `kubectl`](/zh-cn/docs/tasks/tools/).
|
||||
|
||||
<!-- ### Manual deployments -->
|
||||
### 手动部署 {#manual-deployments}
|
||||
|
|
@ -109,10 +109,10 @@ kubelet, or upgrade the {{< skew latestVersion >}}
|
|||
kubelet on that node and bring the node back into service.
|
||||
-->
|
||||
现在，你应该
|
||||
[安装最新版本的 `kubectl`](/zh/docs/tasks/tools/).
|
||||
[安装最新版本的 `kubectl`](/zh-cn/docs/tasks/tools/).
|
||||
|
||||
对于集群中的每个节点，
|
||||
[排空](/zh/docs/tasks/administer-cluster/safely-drain-node/)
|
||||
[排空](/zh-cn/docs/tasks/administer-cluster/safely-drain-node/)
|
||||
节点，然后，或者用一个运行了 {{< skew latestVersion >}} kubelet 的新节点替换它；
|
||||
或者升级此节点的 kubelet，并使节点恢复服务。
|
||||
|
||||
|
|
|
|||
|
|
@ -261,7 +261,7 @@ for more detail on how to deploy `cloud-controller-manager`.
|
|||
版本为 N+1 的 `kube-controller-manager` 不能启用领导者迁移，
|
||||
因为在使用外部云驱动的情况下，它不再运行已迁移的控制器，因此不参与迁移。
|
||||
|
||||
请参阅[云控制器管理器管理](/zh/docs/tasks/administer-cluster/running-cloud-controller/)
|
||||
请参阅[云控制器管理器管理](/zh-cn/docs/tasks/administer-cluster/running-cloud-controller/)
|
||||
了解有关如何部署 `cloud-controller-manager` 的更多细节。
|
||||
|
||||
<!--
|
||||
|
|
|
|||
|
|
@ -69,7 +69,7 @@ There are two supported policies:
|
|||
### 配置
|
||||
|
||||
CPU 管理策略通过 kubelet 参数 `--cpu-manager-policy`
|
||||
或 [KubeletConfiguration](/zh/docs/reference/config-api/kubelet-config.v1beta1/)
|
||||
或 [KubeletConfiguration](/zh-cn/docs/reference/config-api/kubelet-config.v1beta1/)
|
||||
中的 `cpuManagerPolicy` 字段来指定。
|
||||
支持两种策略：
|
||||
|
||||
|
|
@ -134,7 +134,7 @@ CPUManager so that the cpu-sets set up by the new policy won’t conflict with i
|
|||
4. Edit the kubelet configuration to change the CPU manager policy to the desired value.
|
||||
5. Start kubelet.
|
||||
-->
|
||||
1. [腾空](/zh/docs/tasks/administer-cluster/safely-drain-node)节点。
|
||||
1. [腾空](/zh-cn/docs/tasks/administer-cluster/safely-drain-node)节点。
|
||||
2. 停止 kubelet。
|
||||
3. 删除旧的 CPU 管理器状态文件。该文件的路径默认为 `/var/lib/kubelet/cpu_manager_state`。
|
||||
这将清除 CPUManager 维护的状态，以便新策略设置的 cpu-sets 不会与之冲突。
|
||||
|
|
@ -169,8 +169,8 @@ are enforced using CFS quota.
|
|||
### none 策略
|
||||
|
||||
`none` 策略显式地启用现有的默认 CPU 亲和方案，不提供操作系统调度器默认行为之外的亲和性策略。
|
||||
通过 CFS 配额来实现 [Guaranteed Pods](/zh/docs/tasks/configure-pod-container/quality-service-pod/)
|
||||
和 [Burstable Pods](/zh/docs/tasks/configure-pod-container/quality-service-pod/)
|
||||
通过 CFS 配额来实现 [Guaranteed Pods](/zh-cn/docs/tasks/configure-pod-container/quality-service-pod/)
|
||||
和 [Burstable Pods](/zh-cn/docs/tasks/configure-pod-container/quality-service-pod/)
|
||||
的 CPU 使用限制。
|
||||
|
||||
<!--
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ content_type: task
|
|||
This document helps you get started using the Kubernetes [NetworkPolicy API](/docs/concepts/services-networking/network-policies/) to declare network policies that govern how pods communicate with each other.
|
||||
-->
|
||||
本文可以帮助你开始使用 Kubernetes 的
|
||||
[NetworkPolicy API](/zh/docs/concepts/services-networking/network-policies/)
|
||||
[NetworkPolicy API](/zh-cn/docs/concepts/services-networking/network-policies/)
|
||||
声明网络策略去管理 Pod 之间的通信
|
||||
|
||||
{{% thirdparty-content %}}
|
||||
|
|
@ -39,12 +39,12 @@ Make sure you've configured a network provider with network policy support. Ther
|
|||
-->
|
||||
你首先需要有一个支持网络策略的 Kubernetes 集群。已经有许多支持 NetworkPolicy 的网络提供商，包括：
|
||||
|
||||
* [Antrea](/zh/docs/tasks/administer-cluster/network-policy-provider/antrea-network-policy/)
|
||||
* [Calico](/zh/docs/tasks/administer-cluster/network-policy-provider/calico-network-policy/)
|
||||
* [Cilium](/zh/docs/tasks/administer-cluster/network-policy-provider/cilium-network-policy/)
|
||||
* [Kube-router](/zh/docs/tasks/administer-cluster/network-policy-provider/kube-router-network-policy/)
|
||||
* [Romana](/zh/docs/tasks/administer-cluster/network-policy-provider/romana-network-policy/)
|
||||
* [Weave 网络](/zh/docs/tasks/administer-cluster/network-policy-provider/weave-network-policy/)
|
||||
* [Antrea](/zh-cn/docs/tasks/administer-cluster/network-policy-provider/antrea-network-policy/)
|
||||
* [Calico](/zh-cn/docs/tasks/administer-cluster/network-policy-provider/calico-network-policy/)
|
||||
* [Cilium](/zh-cn/docs/tasks/administer-cluster/network-policy-provider/cilium-network-policy/)
|
||||
* [Kube-router](/zh-cn/docs/tasks/administer-cluster/network-policy-provider/kube-router-network-policy/)
|
||||
* [Romana](/zh-cn/docs/tasks/administer-cluster/network-policy-provider/romana-network-policy/)
|
||||
* [Weave 网络](/zh-cn/docs/tasks/administer-cluster/network-policy-provider/weave-network-policy/)
|
||||
|
||||
<!-- steps -->
|
||||
|
||||
|
|
@ -142,7 +142,7 @@ The name of a NetworkPolicy object must be a valid
|
|||
[DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).
|
||||
-->
|
||||
NetworkPolicy 对象的名称必须是一个合法的
|
||||
[DNS 子域名](/zh/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).
|
||||
[DNS 子域名](/zh-cn/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).
|
||||
|
||||
<!--
|
||||
NetworkPolicy includes a `podSelector` which selects the grouping of Pods to which the policy applies. You can see this policy selects Pods with the label `app=nginx`. The label was automatically added to the Pod in the `nginx` Deployment. An empty `podSelector` selects all pods in the namespace.
|
||||
|
|
|
|||
|
|
@ -81,5 +81,5 @@ For in-tree cloud providers, you can run the in-tree cloud controller manager as
|
|||
-->
|
||||
对于树内（In-Tree）驱动，你可以将树内云控制器管理器作为集群中的
|
||||
{{< glossary_tooltip term_id="daemonset" text="DaemonSet" >}} 来运行。
|
||||
有关详细信息，请参阅[云控制器管理器管理](/zh/docs/tasks/administer-cluster/running-cloud-controller/)。
|
||||
有关详细信息，请参阅[云控制器管理器管理](/zh-cn/docs/tasks/administer-cluster/running-cloud-controller/)。
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ Your cluster must be running the CoreDNS add-on.
|
|||
explains how to use `kubeadm` to migrate from `kube-dns`.
|
||||
-->
|
||||
你的集群必须运行 CoreDNS 插件。
|
||||
文档[迁移到 CoreDNS](/zh/docs/tasks/administer-cluster/coredns/#migrating-to-coredns)
|
||||
文档[迁移到 CoreDNS](/zh-cn/docs/tasks/administer-cluster/coredns/#migrating-to-coredns)
|
||||
解释了如何使用 `kubeadm` 从 `kube-dns` 迁移到 CoreDNS。
|
||||
|
||||
<!-- steps -->
|
||||
|
|
@ -84,7 +84,7 @@ The DNS server supports forward lookups (A and AAAA records), port lookups (SRV
|
|||
and more. For more information, see [DNS for Services and Pods](/docs/concepts/services-networking/dns-pod-service/).
|
||||
-->
|
||||
DNS 服务器支持正向查找（A 和 AAAA 记录）、端口发现（SRV 记录）、反向 IP 地址发现（PTR 记录）等。
|
||||
更多信息，请参见[Pod 和 服务的 DNS](/zh/docs/concepts/services-networking/dns-pod-service/)。
|
||||
更多信息，请参见[Pod 和 服务的 DNS](/zh-cn/docs/concepts/services-networking/dns-pod-service/)。
|
||||
|
||||
<!--
|
||||
If a Pod's `dnsPolicy` is set to "`default`", it inherits the name resolution
|
||||
|
|
@ -94,7 +94,7 @@ But see [Known issues](/docs/tasks/administer-cluster/dns-debugging-resolution/#
|
|||
-->
|
||||
如果 Pod 的 `dnsPolicy` 设置为 "`default`"，则它将从 Pod 运行所在节点继承名称解析配置。
|
||||
Pod 的 DNS 解析行为应该与节点相同。
|
||||
但请参阅[已知问题](/zh/docs/tasks/administer-cluster/dns-debugging-resolution/#known-issues)。
|
||||
但请参阅[已知问题](/zh-cn/docs/tasks/administer-cluster/dns-debugging-resolution/#known-issues)。
|
||||
|
||||
<!--
|
||||
If you don't want this, or if you want a different DNS config for pods, you can
|
||||
|
|
@ -399,5 +399,5 @@ A cluster administrator can also migrate using [the deploy script](https://githu
|
|||
<!--
|
||||
- Read [Debugging DNS Resolution](/docs/tasks/administer-cluster/dns-debugging-resolution/).
|
||||
-->
|
||||
- 阅读[调试 DNS 解析](/zh/docs/tasks/administer-cluster/dns-debugging-resolution/)
|
||||
- 阅读[调试 DNS 解析](/zh-cn/docs/tasks/administer-cluster/dns-debugging-resolution/)
|
||||
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@ busybox 1/1 Running 0 <some-time>
|
|||
|
||||
{{< note >}}
|
||||
此示例在 `default` 命名空间创建 pod。 服务的 DNS 名字解析取决于 pod 的命名空间。 详细信息请查阅
|
||||
[服务和 Pod 的 DNS](/zh/docs/concepts/services-networking/dns-pod-service/#what-things-get-dns-names)。
|
||||
[服务和 Pod 的 DNS](/zh-cn/docs/concepts/services-networking/dns-pod-service/#what-things-get-dns-names)。
|
||||
{{< /note >}}
|
||||
|
||||
使用上面的清单来创建一个 Pod：
|
||||
|
|
@ -115,7 +115,7 @@ Take a look inside the resolv.conf file.
|
|||
### 先检查本地的 DNS 配置
|
||||
|
||||
查看 resolv.conf 文件的内容
|
||||
（阅读[定制 DNS 服务](/zh/docs/tasks/administer-cluster/dns-custom-nameservers/) 和
|
||||
（阅读[定制 DNS 服务](/zh-cn/docs/tasks/administer-cluster/dns-custom-nameservers/) 和
|
||||
后文的[已知问题](#known-issues) ，获取更多信息)
|
||||
|
||||
```shell
|
||||
|
|
@ -266,7 +266,7 @@ but it does not appear, see
|
|||
more information.
|
||||
-->
|
||||
如果你已经创建了 DNS 服务，或者该服务应该是默认自动创建的但是它并没有出现，
|
||||
请阅读[调试服务](/zh/docs/tasks/debug/debug-application/debug-service/)
|
||||
请阅读[调试服务](/zh-cn/docs/tasks/debug/debug-application/debug-service/)
|
||||
来获取更多信息。
|
||||
|
||||
<!--
|
||||
|
|
@ -297,7 +297,7 @@ For additional Kubernetes DNS examples, see the
|
|||
in the Kubernetes GitHub repository.
|
||||
-->
|
||||
如果你没看到对应的端点，请阅读
|
||||
[调试服务](/zh/docs/tasks/debug/debug-application/debug-service/)的端点部分。
|
||||
[调试服务](/zh-cn/docs/tasks/debug/debug-application/debug-service/)的端点部分。
|
||||
|
||||
若需要了解更多的 Kubernetes DNS 例子，请在 Kubernetes GitHub 仓库里查看
|
||||
[cluster-dns 示例](https://github.com/kubernetes/examples/tree/master/staging/cluster-dns)。
|
||||
|
|
@ -479,7 +479,7 @@ To learn more about name resolution, see
|
|||
[DNS for Services and Pods](/docs/concepts/services-networking/dns-pod-service/#what-things-get-dns-names).
|
||||
-->
|
||||
要进一步了解名字解析，请查看
|
||||
[服务和 Pod 的 DNS](/zh/docs/concepts/services-networking/dns-pod-service/#what-things-get-dns-names)。
|
||||
[服务和 Pod 的 DNS](/zh-cn/docs/concepts/services-networking/dns-pod-service/#what-things-get-dns-names)。
|
||||
|
||||
<!--
|
||||
## Known issues
|
||||
|
|
@ -538,7 +538,7 @@ Kubernetes 需要占用一个 `nameserver` 记录和三个`search`记录。
|
|||
With [Expanded DNS Configuration](/docs/concepts/services-networking/dns-pod-service/#expanded-dns-configuration),
|
||||
Kubernetes allows more DNS `search` records.
|
||||
-->
|
||||
使用[扩展 DNS 设置](/zh/docs/concepts/services-networking/dns-pod-service/#expanded-dns-configuration)，
|
||||
使用[扩展 DNS 设置](/zh-cn/docs/concepts/services-networking/dns-pod-service/#expanded-dns-configuration)，
|
||||
Kubernetes 允许更多的 `search` 记录。
|
||||
{{< /note >}}
|
||||
<!--
|
||||
|
|
@ -557,6 +557,6 @@ for more information.
|
|||
- [Autoscaling the DNS Service in a Cluster](/docs/tasks/administer-cluster/dns-horizontal-autoscaling/).
|
||||
- [DNS for Services and Pods](/docs/concepts/services-networking/dns-pod-service/)
|
||||
-->
|
||||
- 参阅[自动扩缩集群中的 DNS 服务](/zh/docs/tasks/administer-cluster/dns-horizontal-autoscaling/).
|
||||
- 阅读[服务和 Pod 的 DNS](/zh/docs/concepts/services-networking/dns-pod-service/)
|
||||
- 参阅[自动扩缩集群中的 DNS 服务](/zh-cn/docs/tasks/administer-cluster/dns-horizontal-autoscaling/).
|
||||
- 阅读[服务和 Pod 的 DNS](/zh-cn/docs/concepts/services-networking/dns-pod-service/)
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ Kubernetes cluster.
|
|||
-->
|
||||
* 本指南假设你的节点使用 AMD64 或 Intel 64 CPU 架构
|
||||
|
||||
* 确保已启用 [DNS 功能](/zh/docs/concepts/services-networking/dns-pod-service/)本身。
|
||||
* 确保已启用 [DNS 功能](/zh-cn/docs/concepts/services-networking/dns-pod-service/)本身。
|
||||
|
||||
* 建议使用 Kubernetes 1.4.0 或更高版本。
|
||||
|
||||
|
|
@ -412,6 +412,6 @@ patterns: *linear* and *ladder*.
|
|||
[implementation of cluster-proportional-autoscaler](https://github.com/kubernetes-sigs/cluster-proportional-autoscaler).
|
||||
|
||||
-->
|
||||
* 阅读[为关键插件 Pod 提供的调度保障](/zh/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/)
|
||||
* 阅读[为关键插件 Pod 提供的调度保障](/zh-cn/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/)
|
||||
* 进一步了解 [cluster-proportional-autoscaler 实现](https://github.com/kubernetes-sigs/cluster-proportional-autoscaler)
|
||||
|
||||
|
|
|
|||
|
|
@ -38,14 +38,14 @@ The `runtime-config` command line argument also supports 2 special keys:
|
|||
<!--
|
||||
- `api/all`, representing all known APIs
|
||||
- `api/legacy`, representing only legacy APIs. Legacy APIs are any APIs that have been
|
||||
explicitly [deprecated](/zh/docs/reference/using-api/deprecation-policy/).
|
||||
explicitly [deprecated](/zh-cn/docs/reference/using-api/deprecation-policy/).
|
||||
|
||||
For example, to turning off all API versions except v1, pass `--runtime-config=api/all=false,api/v1=true`
|
||||
to the `kube-apiserver`.
|
||||
-->
|
||||
- `api/all`：指所有已知的 API
|
||||
- `api/legacy`：指过时的 API。过时的 API 就是明确地
|
||||
[弃用](/zh/docs/reference/using-api/deprecation-policy/)
|
||||
[弃用](/zh-cn/docs/reference/using-api/deprecation-policy/)
|
||||
的 API。
|
||||
|
||||
例如：为了停用除去 v1 版本之外的全部其他 API 版本，
|
||||
|
|
@ -57,5 +57,5 @@ to the `kube-apiserver`.
|
|||
Read the [full documentation](/docs/reference/command-line-tools-reference/kube-apiserver/)
|
||||
for the `kube-apiserver` component.
|
||||
-->
|
||||
阅读[完整的文档](/zh/docs/reference/command-line-tools-reference/kube-apiserver/),
|
||||
阅读[完整的文档](/zh-cn/docs/reference/command-line-tools-reference/kube-apiserver/),
|
||||
以了解 `kube-apiserver` 组件。
|
||||
Loading…
Reference in New Issue