Merge pull request #49713 from my-git9/np-2761

[zh-cn]sync configure-upgrade-etcd.md
pull/49725/head
Kubernetes Prow Robot 2025-02-11 18:59:59 -08:00 committed by GitHub
commit 99e78ac65c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 5 additions and 4 deletions

View File

@ -296,12 +296,12 @@ the URL schema.
<!--
Similarly, to configure etcd with secure client communication, specify flags
`--key-file=k8sclient.key` and `--cert-file=k8sclient.cert`, and use HTTPS as
`--key=k8sclient.key` and `--cert=k8sclient.cert`, and use HTTPS as
the URL schema. Here is an example on a client command that uses secure
communication:
-->
类似地,要使用安全客户端通信对 etcd 进行配置,请指定参数 `--key-file=k8sclient.key`
`--cert-file=k8sclient.cert`,并使用 HTTPS 作为 URL 模式。
类似地,要使用安全客户端通信对 etcd 进行配置,请指定参数 `--key=k8sclient.key`
`--cert=k8sclient.cert`,并使用 HTTPS 作为 URL 模式。
使用安全通信的客户端命令的示例:
```
@ -343,7 +343,8 @@ flags `--etcd-certfile=k8sclient.cert`, `--etcd-keyfile=k8sclient.key` and
`--etcd-cafile=ca.cert`.
-->
一旦正确配置了 etcd只有具有有效证书的客户端才能访问它。要让 Kubernetes API 服务器访问,
可以使用参数 `--etcd-certfile=k8sclient.cert`、`--etcd-keyfile=k8sclient.key` 和 `--etcd-cafile=ca.cert` 配置。
可以使用参数 `--etcd-certfile=k8sclient.cert`、`--etcd-keyfile=k8sclient.key`
`--etcd-cafile=ca.cert` 配置。
{{< note >}}
<!--