From 73161087f46efc196f94fce476aa5ae39144ab92 Mon Sep 17 00:00:00 2001 From: xin gu <418294249@qq.com> Date: Thu, 7 Dec 2023 21:54:24 +0800 Subject: [PATCH] sync change-package-repository /tasks/debug/debug-cluster/_index verify-kubectl --- .../kubeadm/change-package-repository.md | 2 +- .../zh-cn/docs/tasks/debug/debug-cluster/_index.md | 6 +++--- .../docs/tasks/tools/included/verify-kubectl.md | 14 ++++++++------ 3 files changed, 12 insertions(+), 10 deletions(-) diff --git a/content/zh-cn/docs/tasks/administer-cluster/kubeadm/change-package-repository.md b/content/zh-cn/docs/tasks/administer-cluster/kubeadm/change-package-repository.md index 62e7f5238bf38..e1e7cbd421ce6 100644 --- a/content/zh-cn/docs/tasks/administer-cluster/kubeadm/change-package-repository.md +++ b/content/zh-cn/docs/tasks/administer-cluster/kubeadm/change-package-repository.md @@ -223,7 +223,7 @@ version. 在从一个 Kubernetes 小版本升级到另一个版本时,应执行此步骤以获取所需 Kubernetes 小版本的软件包访问权限。 -{{< tabs name="k8s_install_versions" >}} +{{< tabs name="k8s_upgrade_versions" >}} {{% tab name="Ubuntu、Debian 或 HypriotOS" %}} ### 故障原因 {#contributing-causes} @@ -329,7 +329,7 @@ This is an incomplete list of things that could go wrong, and how to adjust your - API server VM shutdown or apiserver crashing - Results - unable to stop, update, or start new pods, services, replication controller - - existing pods and services should continue to work normally, unless they depend on the Kubernetes API + - existing pods and services should continue to work normally unless they depend on the Kubernetes API - API server backing storage lost - Results - the kube-apiserver component fails to start successfully and become healthy @@ -401,7 +401,7 @@ This is an incomplete list of things that could go wrong, and how to adjust your 如果返回一个 URL,则意味着 kubectl 成功地访问到了你的集群。 @@ -55,9 +56,11 @@ The connection to the server was refused - did you specify th ``` 例如,如果你想在自己的笔记本上(本地)运行 Kubernetes 集群,你需要先安装一个 Minikube 这样的工具,然后再重新运行上面的命令。 @@ -72,9 +75,8 @@ kubectl cluster-info dump ### Troubleshooting the 'No Auth Provider Found' error message {#no-auth-provider-found} In Kubernetes 1.26, kubectl removed the built-in authentication for the following cloud -providers' managed Kubernetes offerings. -These providers have released kubectl plugins to provide the cloud-specific authentication. -For instructions, refer to the following provider documentation: +providers' managed Kubernetes offerings. These providers have released kubectl plugins +to provide the cloud-specific authentication. For instructions, refer to the following provider documentation: --> ### 排查"找不到身份验证提供商"的错误信息 {#no-auth-provider-found}