sync create-cluster-kubeadm setup-ha-etcd-with-kubeadm kms-provider
xin gu
parent
94dc1fb4e0
commit
ff69424c36
|
|
@ -211,12 +211,12 @@ to a Kubernetes component, the component may exit with an error.
|
|||
<!--
|
||||
To configure the API server advertise address for control plane nodes created with both
|
||||
`init` and `join`, the flag `--apiserver-advertise-address` can be used.
|
||||
Preferably, this option can be set in the [kubeadm API](/docs/reference/config-api/kubeadm-config.v1beta3)
|
||||
Preferably, this option can be set in the [kubeadm API](/docs/reference/config-api/kubeadm-config.v1beta4)
|
||||
as `InitConfiguration.localAPIEndpoint` and `JoinConfiguration.controlPlane.localAPIEndpoint`.
|
||||
-->
|
||||
要为使用 `init` 或 `join` 创建的控制平面节点配置 API 服务器的公告地址，
|
||||
你可以使用 `--apiserver-advertise-address` 标志。
|
||||
最好在 [kubeadm API](/zh-cn/docs/reference/config-api/kubeadm-config.v1beta3)中使用
|
||||
最好在 [kubeadm API](/zh-cn/docs/reference/config-api/kubeadm-config.v1beta4)中使用
|
||||
`InitConfiguration.localAPIEndpoint` 和 `JoinConfiguration.controlPlane.localAPIEndpoint`
|
||||
来设置此选项。
|
||||
|
||||
|
|
@ -621,14 +621,12 @@ See a list of add-ons that implement the
|
|||
|
||||
<!--
|
||||
Please refer to the [Installing Addons](/docs/concepts/cluster-administration/addons/#networking-and-network-policy)
|
||||
page for a non-exhaustive list of networking addons supported by Kubernetes.
|
||||
|
||||
page for a non-exhaustive list of networking addons supported by Kubernetes.
|
||||
You can install a Pod network add-on with the following command on the
|
||||
control-plane node or a node that has the kubeconfig credentials:
|
||||
-->
|
||||
请参阅[安装插件](/zh-cn/docs/concepts/cluster-administration/addons/#networking-and-network-policy)页面，
|
||||
了解 Kubernetes 支持的网络插件的非详尽列表。
|
||||
|
||||
你可以使用以下命令在控制平面节点或具有 kubeconfig 凭据的节点上安装 Pod 网络附加组件：
|
||||
|
||||
```bash
|
||||
|
|
@ -1046,13 +1044,13 @@ match the kubeadm version with the versions of the control plane components, kub
|
|||
kubeadm can be used with Kubernetes components that are the same version as kubeadm
|
||||
or one version older. The Kubernetes version can be specified to kubeadm by using the
|
||||
`--kubernetes-version` flag of `kubeadm init` or the
|
||||
[`ClusterConfiguration.kubernetesVersion`](/docs/reference/config-api/kubeadm-config.v1beta3/)
|
||||
[`ClusterConfiguration.kubernetesVersion`](/docs/reference/config-api/kubeadm-config.v1beta4/)
|
||||
field when using `--config`. This option will control the versions
|
||||
of kube-apiserver, kube-controller-manager, kube-scheduler and kube-proxy.
|
||||
-->
|
||||
kubeadm 可以与 Kubernetes 组件一起使用，这些组件的版本与 kubeadm 相同，或者比它大一个版本。
|
||||
Kubernetes 版本可以通过使用 `--kubeadm init` 的 `--kubernetes-version` 标志或使用 `--config` 时的
|
||||
[`ClusterConfiguration.kubernetesVersion`](/zh-cn/docs/reference/config-api/kubeadm-config.v1beta3/)
|
||||
[`ClusterConfiguration.kubernetesVersion`](/zh-cn/docs/reference/config-api/kubeadm-config.v1beta4/)
|
||||
字段指定给 kubeadm。
|
||||
这个选项将控制 kube-apiserver、kube-controller-manager、kube-scheduler 和 kube-proxy 的版本。
|
||||
|
||||
|
|
|
|||
|
|
@ -218,14 +218,14 @@ on Kubernetes dual-stack support see [Dual-stack support with kubeadm](/docs/set
|
|||
NAME=${NAMES[$i]}
|
||||
cat << EOF > /tmp/${HOST}/kubeadmcfg.yaml
|
||||
---
|
||||
apiVersion: "kubeadm.k8s.io/v1beta3"
|
||||
apiVersion: "kubeadm.k8s.io/v1beta4"
|
||||
kind: InitConfiguration
|
||||
nodeRegistration:
|
||||
name: ${NAME}
|
||||
localAPIEndpoint:
|
||||
advertiseAddress: ${HOST}
|
||||
---
|
||||
apiVersion: "kubeadm.k8s.io/v1beta3"
|
||||
apiVersion: "kubeadm.k8s.io/v1beta4"
|
||||
kind: ClusterConfiguration
|
||||
etcd:
|
||||
local:
|
||||
|
|
@ -234,13 +234,20 @@ on Kubernetes dual-stack support see [Dual-stack support with kubeadm](/docs/set
|
|||
peerCertSANs:
|
||||
- "${HOST}"
|
||||
extraArgs:
|
||||
initial-cluster: ${NAMES[0]}=https://${HOSTS[0]}:2380,${NAMES[1]}=https://${HOSTS[1]}:2380,${NAMES[2]}=https://${HOSTS[2]}:2380
|
||||
initial-cluster-state: new
|
||||
name: ${NAME}
|
||||
listen-peer-urls: https://${HOST}:2380
|
||||
listen-client-urls: https://${HOST}:2379
|
||||
advertise-client-urls: https://${HOST}:2379
|
||||
initial-advertise-peer-urls: https://${HOST}:2380
|
||||
- name: initial-cluster
|
||||
value: ${NAMES[0]}=https://${HOSTS[0]}:2380,${NAMES[1]}=https://${HOSTS[1]}:2380,${NAMES[2]}=https://${HOSTS[2]}:2380
|
||||
- name: initial-cluster-state
|
||||
value: new
|
||||
- name: name
|
||||
value: ${NAME}
|
||||
- name: listen-peer-urls
|
||||
value: https://${HOST}:2380
|
||||
- name: listen-client-urls
|
||||
value: https://${HOST}:2379
|
||||
- name: advertise-client-urls
|
||||
value: https://${HOST}:2379
|
||||
- name: initial-advertise-peer-urls
|
||||
value: https://${HOST}:2380
|
||||
EOF
|
||||
done
|
||||
```
|
||||
|
|
|
|||
|
|
@ -47,9 +47,6 @@ for information security.
|
|||
The version of Kubernetes that you need depends on which KMS API version
|
||||
you have selected. Kubernetes recommends using KMS v2.
|
||||
|
||||
- If you selected KMS API v2, you should use Kubernetes v{{< skew currentVersion >}}
|
||||
(if you are running a different version of Kubernetes that also supports the v2 KMS
|
||||
API, switch to the documentation for that version of Kubernetes).
|
||||
- If you selected KMS API v1 to support clusters prior to version v1.27
|
||||
or if you have a legacy KMS plugin that only supports KMS v1,
|
||||
any supported Kubernetes version will work. This API is deprecated as of Kubernetes v1.28.
|
||||
|
|
@ -57,8 +54,6 @@ you have selected. Kubernetes recommends using KMS v2.
|
|||
-->
|
||||
你所需要的 Kubernetes 版本取决于你已选择的 KMS API 版本。Kubernetes 推荐使用 KMS v2。
|
||||
|
||||
- 如果你选择了 KMS API v2，则应使用 Kubernetes v{{< skew currentVersion >}}
|
||||
（如果你正在运行也支持 KMS API v2 的其他 Kubernetes 版本，需查阅该 Kubernetes 版本的文档）。
|
||||
- 如果你选择了 KMS API v1 来支持早于 v1.27 版本的集群，或者你有一个仅支持 KMS v1 的旧版 KMS 插件，
|
||||
那么任何受支持的 Kubernetes 版本都可以良好工作。此 API 自 Kubernetes v1.28 起被弃用。
|
||||
Kubernetes 不推荐使用此 API。
|
||||
|
|
|
|||
Loading…
Reference in New Issue