Fix relative links issue in zh content (#13312)
* `http://kubernetes.io/docs/` -> `/docs/` * `https://kubernetes.io/docs/` -> `/docs/`
This commit is contained in:
chenrui
committed by
Kubernetes Prow Robot
Kubernetes Prow Robot
parent
868899b059
commit
61ee18e87b
@@ -39,8 +39,7 @@ tags:
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
When you've configured the {{< glossary_tooltip text="Kubernetes API Server" term_id="kube-apiserver" >}} to [support additional APIs](https://kubernetes.io/docs/tasks/access-kubernetes-api/configure-aggregation-layer/), you can add `APIService` objects to "claim" a URL path in the Kubernetes API.
|
||||
When you've configured the {{< glossary_tooltip text="Kubernetes API Server" term_id="kube-apiserver" >}} to [support additional APIs](/docs/tasks/access-kubernetes-api/configure-aggregation-layer/), you can add `APIService` objects to "claim" a URL path in the Kubernetes API.
|
||||
-->
|
||||
|
||||
当您配置了 {{< glossary_tooltip text="Kubernetes API Server" term_id="kube-apiserver" >}} 来 [支持额外的 API](https://kubernetes.io/docs/tasks/access-kubernetes-api/configure-aggregation-layer/)，您就可以在 Kubernetes API 中增加 `APIService` 对象来 "申领（Claim）" 一个 URL 路径。
|
||||
|
||||
当您配置了 {{< glossary_tooltip text="Kubernetes API Server" term_id="kube-apiserver" >}} 来 [支持额外的 API](/docs/tasks/access-kubernetes-api/configure-aggregation-layer/)，您就可以在 Kubernetes API 中增加 `APIService` 对象来 "申领（Claim）" 一个 URL 路径。
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 云控制器管理器
|
||||
id: cloud-controller-manager
|
||||
date: 2018-04-12
|
||||
full_link: https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/
|
||||
full_link: /docs/tasks/administer-cluster/running-cloud-controller/
|
||||
short_description: >
|
||||
云控制器管理器是 1.8 的 alpha 特性。在未来发布的版本中，这是将 Kubernetes 与任何其他云集成的最佳方式。
|
||||
|
||||
@@ -18,7 +18,7 @@ tags:
|
||||
title: Cloud Controller Manager
|
||||
id: cloud-controller-manager
|
||||
date: 2018-04-12
|
||||
full_link: https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/
|
||||
full_link: /docs/tasks/administer-cluster/running-cloud-controller/
|
||||
short_description: >
|
||||
Cloud Controller Manager is an alpha feature in 1.8. In upcoming releases it will be the preferred way to integrate Kubernetes with any cloud.
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: CNI (容器网络接口)
|
||||
id: cni
|
||||
date: 2018-05-25
|
||||
full_link: https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni
|
||||
full_link: /docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni
|
||||
short_description: >
|
||||
容器网络接口 (CNI) 插件是遵循 appc/CNI 协议的一类网络插件。
|
||||
|
||||
@@ -17,7 +17,7 @@ tags:
|
||||
title: CNI (Container network interface)
|
||||
id: cni
|
||||
date: 2018-05-25
|
||||
full_link: https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni
|
||||
full_link: /docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni
|
||||
short_description: >
|
||||
Container network interface (CNI) plugins are a type of Network plugin that adheres to the appc/CNI specification.
|
||||
|
||||
@@ -37,9 +37,8 @@ tags:
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
* For information on Kubernetes and CNI refer to [this](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni).
|
||||
* For information on Kubernetes and CNI, see ["Network plugins"](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni).
|
||||
* For information on Kubernetes and CNI refer to [this](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni).
|
||||
* For information on Kubernetes and CNI, see ["Network plugins"](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni).
|
||||
-->
|
||||
|
||||
* 想了解 Kubernetes 和 CNI 请参考 ["网络插件"](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni)。
|
||||
|
||||
* 想了解 Kubernetes 和 CNI 请参考 ["网络插件"](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni)。
|
||||
|
||||
@@ -35,7 +35,7 @@ tags:
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Allows you to decouple environment-specific configuration from your {{< glossary_tooltip text="container images" term_id="container" >}}, so that your applications are easily portable. When storing confidential data use a [Secret](https://kubernetes.io/docs/concepts/configuration/secret/).
|
||||
Allows you to decouple environment-specific configuration from your {{< glossary_tooltip text="container images" term_id="container" >}}, so that your applications are easily portable. When storing confidential data use a [Secret](/docs/concepts/configuration/secret/).
|
||||
-->
|
||||
|
||||
ConfigMap 将您的环境配置信息和 {{< glossary_tooltip text="容器镜像" term_id="container" >}} 解耦，便于应用配置的修改。当您需要储存机密信息时可以使用 [Secret](https://kubernetes.io/docs/concepts/configuration/secret/) 对象。
|
||||
ConfigMap 将您的环境配置信息和 {{< glossary_tooltip text="容器镜像" term_id="container" >}} 解耦，便于应用配置的修改。当您需要储存机密信息时可以使用 [Secret](/docs/concepts/configuration/secret/) 对象。
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 容器存储接口 (CSI)
|
||||
id: csi
|
||||
date: 2018-06-25
|
||||
full_link: https://kubernetes.io/docs/concepts/storage/volumes/#csi
|
||||
full_link: /docs/concepts/storage/volumes/#csi
|
||||
short_description: >
|
||||
容器存储接口 （CSI）定义了存储系统暴露给容器的标准接口。
|
||||
|
||||
@@ -17,7 +17,7 @@ tags:
|
||||
title: Container Storage Interface (CSI)
|
||||
id: csi
|
||||
date: 2018-06-25
|
||||
full_link: https://kubernetes.io/docs/concepts/storage/volumes/#csi
|
||||
full_link: /docs/concepts/storage/volumes/#csi
|
||||
short_description: >
|
||||
The Container Storage Interface (CSI) defines a standard interface to expose storage systems to containers.
|
||||
|
||||
@@ -38,12 +38,11 @@ tags:
|
||||
<!--
|
||||
CSI allows vendors to create custom storage plugins for Kubernetes without adding them to the Kubernetes repository (out-of-tree plugins). To use a CSI driver from a storage provider, you must first [deploy it to your cluster](https://kubernetes-csi.github.io/docs/Setup.html). You will then be able to create a {{< glossary_tooltip text="Storage Class" term_id="storage-class" >}} that uses that CSI driver.
|
||||
|
||||
* [CSI in the Kubernetes documentation](https://kubernetes.io/docs/concepts/storage/volumes/#csi)
|
||||
* [CSI in the Kubernetes documentation](/docs/concepts/storage/volumes/#csi)
|
||||
* [List of available CSI drivers](https://kubernetes-csi.github.io/docs/Drivers.html)
|
||||
-->
|
||||
|
||||
CSI 允许存储驱动提供商为 Kubernetes 创建定制化的存储插件，而无需将这些插件的代码添加到 Kubernetes 代码仓库（外部插件）。要使用某个存储提供商的 CSI 驱动，你首先要[将它部署到你的集群上](https://kubernetes-csi.github.io/docs/Setup.html)。然后你才能创建使用该 CSI 驱动的 {{< glossary_tooltip text="Storage Class" term_id="storage-class" >}} 。
|
||||
|
||||
* [Kubernetes 文档中关于 CSI 的描述](https://kubernetes.io/docs/concepts/storage/volumes/#csi)
|
||||
* [Kubernetes 文档中关于 CSI 的描述](/docs/concepts/storage/volumes/#csi)
|
||||
* [可用的 CSI 驱动列表](https://kubernetes-csi.github.io/docs/Drivers.html)
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: Flexvolume
|
||||
id: flexvolume
|
||||
date: 2018-06-25
|
||||
full_link: https://kubernetes.io/docs/concepts/storage/volumes/#flexvolume
|
||||
full_link: /docs/concepts/storage/volumes/#flexvolume
|
||||
short_description: >
|
||||
Flexvolume 是创建 out-of-tree 卷插件的一种接口。 {{< glossary_tooltip text="容器存储接口（CSI）" term_id="csi" >}} 是比 Flexvolume 更新的接口，它解决了 Flexvolumes 的一些问题。
|
||||
|
||||
@@ -17,7 +17,7 @@ tags:
|
||||
title: Flexvolume
|
||||
id: flexvolume
|
||||
date: 2018-06-25
|
||||
full_link: https://kubernetes.io/docs/concepts/storage/volumes/#flexvolume
|
||||
full_link: /docs/concepts/storage/volumes/#flexvolume
|
||||
short_description: >
|
||||
Flexvolume is an interface for creating out-of-tree volume plugins. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface which addresses several problems with Flexvolumes.
|
||||
|
||||
@@ -41,11 +41,11 @@ FlexVolume 驱动程序的二进制文件和依赖项必须安装在主机上。
|
||||
如果可能的话，SIG Storage 建议实现 {{< glossary_tooltip text="CSI" term_id="csi" >}} 驱动程序，因为它解决了 Flexvolumes 的限制。
|
||||
|
||||
<!--
|
||||
* [Flexvolume in the Kubernetes documentation](https://kubernetes.io/docs/concepts/storage/volumes/#flexvolume)
|
||||
* [Flexvolume in the Kubernetes documentation](/docs/concepts/storage/volumes/#flexvolume)
|
||||
* [More information on Flexvolumes](https://github.com/kubernetes/community/blob/master/contributors/devel/flexvolume.md)
|
||||
* [Volume Plugin FAQ for Storage Vendors](https://github.com/kubernetes/community/blob/master/sig-storage/volume-plugin-faq.md)
|
||||
-->
|
||||
|
||||
* [Kubernetes 文档中的 Flexvolume](https://kubernetes.io/docs/concepts/storage/volumes/#flexvolume)
|
||||
* [Kubernetes 文档中的 Flexvolume](/docs/concepts/storage/volumes/#flexvolume)
|
||||
* [更多关于 Flexvolumes 的信息](https://github.com/kubernetes/community/blob/master/contributors/devel/flexvolume.md)
|
||||
* [存储供应商的卷插件 FAQ](https://github.com/kubernetes/community/blob/master/sig-storage/volume-plugin-faq.md)
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: ReplicaSet
|
||||
id: replica-set
|
||||
date: 2018-04-12
|
||||
full_link: https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/
|
||||
full_link: /docs/concepts/workloads/controllers/replicaset/
|
||||
short_description: >
|
||||
ReplicaSet 是下一代副本控制器。
|
||||
|
||||
@@ -18,7 +18,7 @@ tags:
|
||||
title: ReplicaSet
|
||||
id: replica-set
|
||||
date: 2018-04-12
|
||||
full_link: https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/
|
||||
full_link: /docs/concepts/workloads/controllers/replicaset/
|
||||
short_description: >
|
||||
ReplicaSet is the next-generation Replication Controller.
|
||||
|
||||
|
||||
@@ -37,9 +37,9 @@ tags:
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Allows for more control over how sensitive information is used and reduces the risk of accidental exposure, including [encryption](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#ensure-all-secrets-are-encrypted) at rest. A {{< glossary_tooltip text="Pod" term_id="pod" >}} references the secret as a file in a volume mount or by the kubelet pulling images for a pod. Secrets are great for confidential data and [ConfigMaps](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/) for non-confidential data.
|
||||
Allows for more control over how sensitive information is used and reduces the risk of accidental exposure, including [encryption](/docs/tasks/administer-cluster/encrypt-data/#ensure-all-secrets-are-encrypted) at rest. A {{< glossary_tooltip text="Pod" term_id="pod" >}} references the secret as a file in a volume mount or by the kubelet pulling images for a pod. Secrets are great for confidential data and [ConfigMaps](/docs/tasks/configure-pod-container/configure-pod-configmap/) for non-confidential data.
|
||||
-->
|
||||
|
||||
Secret 允许用户对如何使用敏感信息进行更多的控制，并减少信息意外暴露的风险，包括静态[加密](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#ensure-all-secrets-are-encrypted)。
|
||||
Secret 允许用户对如何使用敏感信息进行更多的控制，并减少信息意外暴露的风险，包括静态[加密](/docs/tasks/administer-cluster/encrypt-data/#ensure-all-secrets-are-encrypted)。
|
||||
{{< glossary_tooltip text="Pod" term_id="pod" >}} 通过挂载卷中的文件的方式引用 Secret，或者通过 kubelet 为 pod 拉取镜像时引用。
|
||||
Secret 非常适合机密数据使用，而 [ConfigMaps](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/) 适用于非机密数据。
|
||||
Secret 非常适合机密数据使用，而 [ConfigMaps](/docs/tasks/configure-pod-container/configure-pod-configmap/) 适用于非机密数据。
|
||||
|
||||
@@ -14,13 +14,13 @@ kubectl 用来控制 Kubernetes 集群管理器
|
||||
|
||||
kubectl controls the Kubernetes cluster manager.
|
||||
|
||||
Find more information at: https://kubernetes.io/docs/reference/kubectl/overview/
|
||||
Find more information at: /docs/reference/kubectl/overview/
|
||||
-->
|
||||
### 摘要
|
||||
|
||||
kubectl 用来控制 Kubernetes 集群管理器。
|
||||
|
||||
更多信息参见 https://kubernetes.io/docs/reference/kubectl/overview/
|
||||
更多信息参见 /docs/reference/kubectl/overview/
|
||||
|
||||
```
|
||||
kubectl [flags]
|
||||
|
||||
@@ -43,10 +43,10 @@ What is a bootstrap token more exactly?
|
||||
|
||||
<!--
|
||||
You can read more about bootstrap tokens here:
|
||||
https://kubernetes.io/docs/admin/bootstrap-tokens/
|
||||
/docs/admin/bootstrap-tokens/
|
||||
-->
|
||||
您可以在此处阅读有关引导令牌（bootstrap token）的更多信息：
|
||||
https://kubernetes.io/docs/admin/bootstrap-tokens/
|
||||
/docs/admin/bootstrap-tokens/
|
||||
|
||||
```
|
||||
kubeadm token [flags]
|
||||
@@ -123,6 +123,3 @@ kubeadm token [flags]
|
||||
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -359,8 +359,8 @@ using an external CRI implementation. -->
|
||||
|
||||
<!-- By default, `kubeadm` assigns a node name based on a machine's host address. You can override this setting with the `--node-name`flag. -->
|
||||
默认情况下, `kubeadm` 基于机器的 host 地址分配一个节点名称。你可以使用 `--node-name` 参数覆盖这个设置。
|
||||
<!-- The flag passes the appropriate [`--hostname-override`](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/#options) to the kubelet. -->
|
||||
这个参数会向 kubelet 传递相应的 [`--hostname-override`](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/#options) 参数。
|
||||
<!-- The flag passes the appropriate [`--hostname-override`](/docs/reference/command-line-tools-reference/kubelet/#options) to the kubelet. -->
|
||||
这个参数会向 kubelet 传递相应的 [`--hostname-override`](/docs/reference/command-line-tools-reference/kubelet/#options) 参数。
|
||||
|
||||
<!-- Be aware that overriding the hostname can [interfere with cloud providers](https://github.com/kubernetes/website/pull/8873). -->
|
||||
注意覆盖主机名称可能会 [干扰到云服务提供商](https://github.com/kubernetes/website/pull/8873)。
|
||||
@@ -394,8 +394,8 @@ without manual intervention. This and other limitations are expected to be
|
||||
resolved before self-hosting graduates from alpha. -->
|
||||
1.8 版本中的自托管功能有一些重要的限制。特别的, 一个自托管的集群如果不手动介入的话 _不能够从主节点的重新启动中恢复_ 。 这个以及其它的一些限制被期望在自托管功能从 alpha 状态毕业前解决。
|
||||
|
||||
<!-- By default, self-hosted control plane Pods rely on credentials loaded from [`hostPath`](https://kubernetes.io/docs/concepts/storage/volumes/#hostpath) volumes. Except for initial creation, these credentials are not managed by kubeadm. You can use `--feature-gates=StoreCertsInSecrets=true` to enable an experimental mode where control plane credentials are loaded from Secrets instead. This requires very careful control over the authentication and authorization configuration for your cluster, and may not be appropriate for your environment. -->
|
||||
默认情况下, self-hosted 控制平面 Pods 依赖位于 [`hostPath`](https://kubernetes.io/docs/concepts/storage/volumes/#hostpath) 数据卷中的证书。除了初始化创建证书的过程, 这些证书不被 kubeadm 管理。你可以使用 `--feature-gates=StoreCertsInSecrets=true` 参数来启用一个试验性的模式，在这个模式中控制平面证书从 Secrets 加载。 这要求对你的集群进行非常小心的对鉴权和授权配置的控制, 并且可能并不适合你的环境。
|
||||
<!-- By default, self-hosted control plane Pods rely on credentials loaded from [`hostPath`](/docs/concepts/storage/volumes/#hostpath) volumes. Except for initial creation, these credentials are not managed by kubeadm. You can use `--feature-gates=StoreCertsInSecrets=true` to enable an experimental mode where control plane credentials are loaded from Secrets instead. This requires very careful control over the authentication and authorization configuration for your cluster, and may not be appropriate for your environment. -->
|
||||
默认情况下, self-hosted 控制平面 Pods 依赖位于 [`hostPath`](/docs/concepts/storage/volumes/#hostpath) 数据卷中的证书。除了初始化创建证书的过程, 这些证书不被 kubeadm 管理。你可以使用 `--feature-gates=StoreCertsInSecrets=true` 参数来启用一个试验性的模式，在这个模式中控制平面证书从 Secrets 加载。 这要求对你的集群进行非常小心的对鉴权和授权配置的控制, 并且可能并不适合你的环境。
|
||||
|
||||
{{< caution >}}
|
||||
<!-- **Caution:** `StoreCertsInSecrets` is an alpha feature. It is deprecated in 1.12
|
||||
|
||||
@@ -70,7 +70,7 @@ kubefed join CLUSTER_NAME --host-cluster-context=HOST_CONTEXT [flags]
|
||||
-h, --help help for join
|
||||
--host-cluster-context string Host cluster context
|
||||
--no-headers When using the default or custom-column output format, don't print headers (default print headers).
|
||||
-o, --output string Output format. One of: json|yaml|wide|name|custom-columns=...|custom-columns-file=...|go-template=...|go-template-file=...|jsonpath=...|jsonpath-file=... See custom columns [http://kubernetes.io/docs/user-guide/kubectl-overview/#custom-columns], golang template [http://golang.org/pkg/text/template/#pkg-overview] and jsonpath template [http://kubernetes.io/docs/user-guide/jsonpath].
|
||||
-o, --output string Output format. One of: json|yaml|wide|name|custom-columns=...|custom-columns-file=...|go-template=...|go-template-file=...|jsonpath=...|jsonpath-file=... See custom columns [/docs/user-guide/kubectl-overview/#custom-columns], golang template [http://golang.org/pkg/text/template/#pkg-overview] and jsonpath template [/docs/user-guide/jsonpath].
|
||||
--save-config If true, the configuration of current object will be saved in its annotation. Otherwise, the annotation will be unchanged. This flag is useful when you want to perform kubectl apply on this object in the future.
|
||||
-a, --show-all When printing, show all resources (default hide terminated pods.)
|
||||
--show-labels When printing, show all labels as the last column (default hide labels column)
|
||||
@@ -90,7 +90,7 @@ kubefed join CLUSTER_NAME --host-cluster-context=HOST_CONTEXT [flags]
|
||||
-h, --help join 的帮助信息。
|
||||
--host-cluster-context string 主机集群上下文。
|
||||
--no-headers 当使用默认或者定制列输出格式时，不打印头信息（默认打印头信息）。
|
||||
-o, --output string 输出格式。下列之一： json|yaml|wide|name|custom-columns=...|custom-columns-file=...|go-template=...|go-template-file=...|jsonpath=...|jsonpath-file=... 参考定制列 [http://kubernetes.io/docs/user-guide/kubectl-overview/#custom-columns]，golang 模版 [http://golang.org/pkg/text/template/#pkg-overview] 和 jsonpath 模版 [http://kubernetes.io/docs/user-guide/jsonpath]。
|
||||
-o, --output string 输出格式。下列之一： json|yaml|wide|name|custom-columns=...|custom-columns-file=...|go-template=...|go-template-file=...|jsonpath=...|jsonpath-file=... 参考定制列 [/docs/user-guide/kubectl-overview/#custom-columns]，golang 模版 [http://golang.org/pkg/text/template/#pkg-overview] 和 jsonpath 模版 [/docs/user-guide/jsonpath]。
|
||||
--save-config 如果为 true，当前对象的配置将保存到它的注解中。否则将不会改变注解。 当你将来对此对象执行 kubectl apply 时，会用到该参数。
|
||||
-a, --show-all 打印时，显示所有资源。（默认隐藏已终止的 pod）
|
||||
--show-labels 打印时，将所有标签显示在最后一列。 (默认隐藏标签列）
|
||||
|
||||
Reference in New Issue
Block a user