Merge pull request #42722 from asa3311/sync-zh-55

[zh] sync kops create-cluster-kubeadm /tasks/debug/_index
pull/42733/head
Kubernetes Prow Robot 2023-08-26 05:09:21 -07:00 committed by GitHub
commit 6f562f67e4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 17 additions and 8 deletions

View File

@ -426,12 +426,13 @@ including tools for logging, monitoring, network policy, visualization, and cont
* Learn more about `kOps` [advanced usage](https://kops.sigs.k8s.io/) for tutorials,
best practices and advanced configuration options.
* Follow `kOps` community discussions on Slack:
[community discussions](https://github.com/kubernetes/kops#other-ways-to-communicate-with-the-contributors).
[community discussions](https://kops.sigs.k8s.io/contributing/#other-ways-to-communicate-with-the-contributors).
(visit https://slack.k8s.io/ for an invitation to this Slack workspace).
* Contribute to `kOps` by addressing or raising an issue [GitHub Issues](https://github.com/kubernetes/kops/issues).
-->
* 了解有关 Kubernetes 的[概念](/zh-cn/docs/concepts/)和
[`kubectl`](/zh-cn/docs/reference/kubectl/) 的更多信息。
* 参阅 `kOps` [进阶用法](https://kops.sigs.k8s.io/) 获取教程、最佳实践和进阶配置选项。
* 通过 Slack[社区讨论](https://github.com/kubernetes/kops#other-ways-to-communicate-with-the-contributors)
参与 `kOps` 社区讨论。
* 通过 Slack[社区讨论](https://kops.sigs.k8s.io/contributing/#other-ways-to-communicate-with-the-contributors)
参与 `kOps` 社区讨论。(访问 https://slack.k8s.io/ 获取此 Slack 工作空间的邀请)
* 通过解决或提出一个 [GitHub Issue](https://github.com/kubernetes/kops/issues) 来为 `kOps` 做贡献。

View File

@ -136,16 +136,16 @@ For detailed instructions and other prerequisites, see [Installing kubeadm](/doc
{{< note >}}
<!--
If you have already installed kubeadm, run
`apt-get update && apt-get upgrade` or
`yum update` to get the latest version of kubeadm.
If you have already installed kubeadm, see the first two steps of the
[Upgrading Linux nodes](/docs/tasks/administer-cluster/kubeadm/upgrading-linux-nodes) document for instructions on how to upgrade kubeadm.
When you upgrade, the kubelet restarts every few seconds as it waits in a crashloop for
kubeadm to tell it what to do. This crashloop is expected and normal.
After you initialize your control-plane, the kubelet runs normally.
-->
如果你已经安装了kubeadm执行 `apt-get update && apt-get upgrade``yum update`
以获取 kubeadm 的最新版本。
如果你已经安装了 kubeadm
请查看[升级 Linux 节点](/zh-cn/docs/tasks/administer-cluster/kubeadm/upgrading-linux-nodes)文档的前两步,
了解如何升级 kubeadm 的说明。
升级时kubelet 每隔几秒钟重新启动一次,
在 crashloop 状态中等待 kubeadm 发布指令。crashloop 状态是正常现象。

View File

@ -4,6 +4,10 @@ description: 设置监控和日志记录以对集群进行故障排除或调试
weight: 40
content_type: concept
no_list: true
card:
name: tasks
weight: 999
title: 寻求帮助
---
<!--
title: "Monitoring, Logging, and Debugging"
@ -14,6 +18,10 @@ reviewers:
- davidopp
content_type: concept
no_list: true
card:
name: tasks
weight: 999
title: Getting help
-->
<!-- overview -->