diff --git a/content/zh-cn/docs/reference/config-api/kubeadm-config.v1beta3.md b/content/zh-cn/docs/reference/config-api/kubeadm-config.v1beta3.md index 49b2e862d2..e5af2a4250 100644 --- a/content/zh-cn/docs/reference/config-api/kubeadm-config.v1beta3.md +++ b/content/zh-cn/docs/reference/config-api/kubeadm-config.v1beta3.md @@ -259,7 +259,7 @@ components by adding customized setting or overriding kubeadm default settings.<
The KubeProxyConfiguration type should be used to change the configuration passed to kube-proxy instances deployed in the cluster. If this object is not provided or provided only partially, kubeadm applies defaults.
See https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/ or -https://godoc.org/k8s.io/kube-proxy/config/v1alpha1#KubeProxyConfiguration +https://pkg.go.dev/k8s.io/kube-proxy/config/v1alpha1#KubeProxyConfiguration for kube-proxy official documentation.
-->KubeProxyConfiguration 类型用来更改传递给在集群中部署的 kube-proxy 实例 @@ -267,7 +267,7 @@ for kube-proxy official documentation.
关于 kube-proxy 的官方文档,可参阅 https://kubernetes.io/zh/docs/reference/command-line-tools-reference/kube-proxy/ -或者 https://godoc.org/k8s.io/kube-proxy/config/v1alpha1#KubeProxyConfiguration。 +或者 https://pkg.go.dev/k8s.io/kube-proxy/config/v1alpha1#KubeProxyConfiguration。
apiVersion: kubelet.config.k8s.io/v1beta1 @@ -279,7 +279,7 @@ https://kubernetes.io/zh/docs/reference/command-line-tools-reference/kube-proxy/The KubeletConfiguration type should be used to change the configurations that will be passed to all kubelet instances deployed in the cluster. If this object is not provided or provided only partially, kubeadm applies defaults.
See https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/ or -https://godoc.org/k8s.io/kubelet/config/v1beta1#KubeletConfiguration +https://pkg.go.dev/k8s.io/kubelet/config/v1beta1#KubeletConfiguration for kubelet official documentation.
Here is a fully populated example of a single YAML file containing multiple configuration types to be used during a
@@ -290,7 +290,7 @@ configuration types to be used during akubeadm init
run.kubeadm init
run.关于 kubelet 的官方文档,可参阅 https://kubernetes.io/zh/docs/reference/command-line-tools-reference/kubelet/ 或者 -https://godoc.org/k8s.io/kubelet/config/v1beta1#KubeletConfiguration。
+https://pkg.go.dev/k8s.io/kubelet/config/v1beta1#KubeletConfiguration。下面是一个为执行
@@ -298,34 +298,34 @@ https://godoc.org/k8s.io/kubelet/config/v1beta1#KubeletConfiguration。kubeadm init
而提供的、包含多个配置类型的单一 YAML 文件, 其中填充了很多部分。apiVersion: kubeadm.k8s.io/v1beta3 kind: InitConfiguration bootstrapTokens: -- token: "9a08jv.c0izixklcxtmnze7" - description: "kubeadm bootstrap token" - ttl: "24h" -- token: "783bde.3f89s0fje9f38fhf" - description: "another bootstrap token" - usages: - - authentication - - signing - groups: - - system:bootstrappers:kubeadm:default-node-token + - token: "9a08jv.c0izixklcxtmnze7" + description: "kubeadm bootstrap token" + ttl: "24h" + - token: "783bde.3f89s0fje9f38fhf" + description: "another bootstrap token" + usages: + - authentication + - signing + groups: + - system:bootstrappers:kubeadm:default-node-token nodeRegistration: name: "ec2-10-100-0-1" criSocket: "/var/run/dockershim.sock" taints: - - key: "kubeadmNode" - value: "someValue" - effect: "NoSchedule" + - key: "kubeadmNode" + value: "someValue" + effect: "NoSchedule" kubeletExtraArgs: v: 4 -ignorePreflightErrors: -- IsPrivilegedUser - imagePullPolicy: "IfNotPresent" + ignorePreflightErrors: + - IsPrivilegedUser + imagePullPolicy: "IfNotPresent" localAPIEndpoint: advertiseAddress: "10.100.0.1" bindPort: 6443 certificateKey: "e6a2eb8581237ab72a4f494f30285ec12a9694d750b9785706a83bfcbbbd2204" - skipPhases: - - addon/kube-proxy +skipPhases: + - addon/kube-proxy --- apiVersion: kubeadm.k8s.io/v1beta3 kind: ClusterConfiguration @@ -338,9 +338,9 @@ https://godoc.org/k8s.io/kubelet/config/v1beta1#KubeletConfiguration。 extraArgs: listen-client-urls: "http://10.100.0.1:2379" serverCertSANs: - - "ec2-10-100-0-1.compute-1.amazonaws.com" + - "ec2-10-100-0-1.compute-1.amazonaws.com" peerCertSANs: - - "10.100.0.1" + - "10.100.0.1" # external: # endpoints: # - "10.100.0.1:2379" @@ -358,33 +358,33 @@ https://godoc.org/k8s.io/kubelet/config/v1beta1#KubeletConfiguration。 extraArgs: authorization-mode: "Node,RBAC" extraVolumes: - - name: "some-volume" - hostPath: "/etc/some-path" - mountPath: "/etc/some-pod-path" - readOnly: false - pathType: File + - name: "some-volume" + hostPath: "/etc/some-path" + mountPath: "/etc/some-pod-path" + readOnly: false + pathType: File certSANs: - - "10.100.1.1" - - "ec2-10-100-0-1.compute-1.amazonaws.com" + - "10.100.1.1" + - "ec2-10-100-0-1.compute-1.amazonaws.com" timeoutForControlPlane: 4m0s controllerManager: extraArgs: "node-cidr-mask-size": "20" extraVolumes: - - name: "some-volume" - hostPath: "/etc/some-path" - mountPath: "/etc/some-pod-path" - readOnly: false - pathType: File + - name: "some-volume" + hostPath: "/etc/some-path" + mountPath: "/etc/some-pod-path" + readOnly: false + pathType: File scheduler: extraArgs: address: "10.100.0.1" extraVolumes: - - name: "some-volume" - hostPath: "/etc/some-path" - mountPath: "/etc/some-pod-path" - readOnly: false - pathType: File + - name: "some-volume" + hostPath: "/etc/some-path" + mountPath: "/etc/some-pod-path" + readOnly: false + pathType: File certificatesDir: "/etc/kubernetes/pki" imageRepository: "registry.k8s.io" clusterName: "example-cluster" @@ -446,6 +446,127 @@ node only (e.g. the node ip). - [ClusterConfiguration](#kubeadm-k8s-io-v1beta3-ClusterConfiguration) - [InitConfiguration](#kubeadm-k8s-io-v1beta3-InitConfiguration) - [JoinConfiguration](#kubeadm-k8s-io-v1beta3-JoinConfiguration) + +## `BootstrapToken` {#BootstrapToken} + + +**出现在:** + +- [InitConfiguration](#kubeadm-k8s-io-v1beta3-InitConfiguration) + + +BootstrapToken 描述的是一个启动引导令牌,以 Secret 形式存储在集群中。
+ ++
+ +## `BootstrapTokenString` {#BootstrapTokenString} + + +**出现在:** + +- [BootstrapToken](#BootstrapToken) + + ++ + + 字段 描述 + + token
[必需]
+BootstrapTokenString
++ + ++
token
用来在节点与控制面之间建立双向的信任关系。 +在向集群中添加节点时使用。+ + description
+string
++ + ++
description
设置一个对人友好的消息,说明为什么此令牌 +会存在以及其目标用途,这样其他管理员能够知道其目的。+ + ttl
+meta/v1.Duration
++ + ++
ttl
定义此令牌的声明周期。默认为24h
。 +expires
和ttl
是互斥的。+ + expires
+meta/v1.Time
++ + ++
expires
设置此令牌过期的时间戳。默认为在运行时基于 +ttl
来决定。 +expires
和ttl
是互斥的。+ + usages
+[]string
++ + ++
usages
描述此令牌的可能使用方式。默认情况下,令牌可用于 +建立双向的信任关系;不过这里可以改变默认用途。+ + + groups
+[]string
++ + ++
groups
设定此令牌被用于身份认证时对应的附加用户组。BootstrapTokenString 形式为
+abcdef.abcdef0123456789
的一个令牌, +用来从加入集群的节点角度验证 API 服务器的身份,或者 "kubeadm join" +在节点启动引导是作为一种身份认证方法。 +此令牌的生命期是短暂的,并且应该如此。+
+ + ## `ClusterConfiguration` {#kubeadm-k8s-io-v1beta3-ClusterConfiguration} @@ -922,7 +1043,7 @@ APIServer 包含集群中 API 服务器部署所必需的设置。+ + + 字段 描述 + + -
[必需]
+string
++ + 无描述 + + ++ + + -
[必需]
+string
++ + 无描述 +timeoutForControlPlane
-meta/v1.Duration
+meta/v1.Duration
@@ -990,14 +1111,14 @@ information will be fetched.
caCertHashes
specifies a set of public key pins to verify when token-based discovery is used. The root CA found during discovery must match one of these values. Specifying an empty set disables root CA pinning, which can be unsafe. -Each hash is specified as "<type>:<value>", where the only currently supported type is +Each hash is specified as<type>:<value>
, where the only currently supported type is "sha256". This is a hex-encoded SHA-256 hash of the Subject Public Key Info (SPKI) object in DER-encoded ASN.1. These hashes can be calculated using, for example, OpenSSL. -->caCertHashes
设置一组在基于令牌来发现服务时要验证的公钥指纹。 发现过程中获得的根 CA 必须与这里的数值之一匹配。 设置为空集合意味着禁用根 CA 指纹,因而可能是不安全的。 -每个哈希值的形式为 "<type>:<value>",当前唯一支持的 type 为 +每个哈希值的形式为<type>:<value>
,当前唯一支持的 type 为 "sha256"。 哈希值为主体公钥信息(Subject Public Key Info,SPKI)对象的 SHA-256 哈希值(十六进制编码),形式为 DER 编码的 ASN.1。 @@ -1177,7 +1298,7 @@ does not contain any other authentication informationtimeout
-meta/v1.Duration
+meta/v1.Duration
@@ -1675,14 +1796,14 @@ i.e.
taints: []
in the YAML file. This field is solely used for Nod@@ -1699,13 +1820,13 @@ the current node is registered.
kubeletExtraArgs
用来向 kubelet 传递额外参数。 这里的参数会通过 kubeadm 在运行时写入的、由 kubelet 来读取的环境文件来 传递给 kubelet 命令行。 -这里的设置会覆盖掉 'kubelet-config-1.X' ConfigMap 中包含的一般性的配置。 +这里的设置会覆盖掉kubelet-config
ConfigMap 中包含的一般性的配置。 命令行标志在解析时优先级更高。 这里的设置值仅作用于 kubeadm 运行所在的节点。 映射中的每个键对应命令行中的一个标志参数,只是去掉了前置的连字符。- -## `BootstrapToken` {#BootstrapToken} - - -**出现在:** - -- [InitConfiguration](#kubeadm-k8s-io-v1beta3-InitConfiguration) - - - imagePullPolicy
-core/v1.PullPolicy
+core/v1.PullPolicy
imagePullPolicy
设定 "kubeadm init" 和 "kubeadm join" 操作期间的镜像拉取策略。此字段的取值可以是 "Always"、"IfNotPresent" 或 @@ -1760,124 +1881,3 @@ first alpha-numerically.BootstrapToken 描述的是一个启动引导令牌,以 Secret 形式存储在集群中。
- --
- -## `BootstrapTokenString` {#BootstrapTokenString} - - -**出现在:** - -- [BootstrapToken](#BootstrapToken) - - -- - - 字段 描述 - - token
[必需]
-BootstrapTokenString
-- - --
token
用来在节点与控制面之间建立双向的信任关系。 -在向集群中添加节点时使用。- - description
-string
-- - --
description
设置一个对人友好的消息,说明为什么此令牌 -会存在以及其目标用途,这样其他管理员能够知道其目的。- - ttl
-meta/v1.Duration
-- - --
ttl
定义此令牌的声明周期。默认为24h
。 -expires
和ttl
是互斥的。- - expires
-meta/v1.Time
-- - --
expires
设置此令牌过期的时间戳。默认为在运行时基于 -ttl
来决定。 -expires
和ttl
是互斥的。- - usages
-[]string
-- - --
usages
描述此令牌的可能使用方式。默认情况下,令牌可用于 -建立双向的信任关系;不过这里可以改变默认用途。- - - groups
-[]string
-- - --
groups
设定此令牌被用于身份认证时对应的附加用户组。BootstrapTokenString 形式为
-abcdef.abcdef0123456789
的一个令牌, -用来从加入集群的节点角度验证 API 服务器的身份,或者 "kubeadm join" -在节点启动引导是作为一种身份认证方法。 -此令牌的生命期是短暂的,并且应该如此。-
-- - - 字段 描述 - - -
[必需]
-string
-- - 无描述 - - -- - - -
[必需]
-string
-- - 无描述 - -