[zh] sync /included/verify-kubectl.md
parent
986b0bc0a2
commit
0d1a62ff9b
|
@ -2,14 +2,20 @@
|
||||||
title: "验证 kubectl 的安装效果"
|
title: "验证 kubectl 的安装效果"
|
||||||
description: "如何验证 kubectl。"
|
description: "如何验证 kubectl。"
|
||||||
headless: true
|
headless: true
|
||||||
|
_build:
|
||||||
|
list: never
|
||||||
|
render: never
|
||||||
|
publishResources: false
|
||||||
---
|
---
|
||||||
<!--
|
<!--
|
||||||
---
|
|
||||||
title: "verify kubectl install"
|
title: "verify kubectl install"
|
||||||
description: "How to verify kubectl."
|
description: "How to verify kubectl."
|
||||||
headless: true
|
headless: true
|
||||||
---
|
_build:
|
||||||
-->
|
list: never
|
||||||
|
render: never
|
||||||
|
publishResources: false
|
||||||
|
-->
|
||||||
|
|
||||||
<!--
|
<!--
|
||||||
In order for kubectl to find and access a Kubernetes cluster, it needs a
|
In order for kubectl to find and access a Kubernetes cluster, it needs a
|
||||||
|
@ -20,7 +26,7 @@ or successfully deploy a Minikube cluster.
|
||||||
By default, kubectl configuration is located at `~/.kube/config`.
|
By default, kubectl configuration is located at `~/.kube/config`.
|
||||||
|
|
||||||
Check that kubectl is properly configured by getting the cluster state:
|
Check that kubectl is properly configured by getting the cluster state:
|
||||||
-->
|
-->
|
||||||
为了让 kubectl 能发现并访问 Kubernetes 集群,你需要一个
|
为了让 kubectl 能发现并访问 Kubernetes 集群,你需要一个
|
||||||
[kubeconfig 文件](/zh-cn/docs/concepts/configuration/organize-cluster-access-kubeconfig/),
|
[kubeconfig 文件](/zh-cn/docs/concepts/configuration/organize-cluster-access-kubeconfig/),
|
||||||
该文件在
|
该文件在
|
||||||
|
@ -28,7 +34,7 @@ Check that kubectl is properly configured by getting the cluster state:
|
||||||
创建集群时,或成功部署一个 Miniube 集群时,均会自动生成。
|
创建集群时,或成功部署一个 Miniube 集群时,均会自动生成。
|
||||||
通常,kubectl 的配置信息存放于文件 `~/.kube/config` 中。
|
通常,kubectl 的配置信息存放于文件 `~/.kube/config` 中。
|
||||||
|
|
||||||
通过获取集群状态的方法,检查是否已恰当的配置了 kubectl:
|
通过获取集群状态的方法,检查是否已恰当地配置了 kubectl:
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
kubectl cluster-info
|
kubectl cluster-info
|
||||||
|
@ -38,8 +44,8 @@ kubectl cluster-info
|
||||||
If you see a URL response, kubectl is correctly configured to access your cluster.
|
If you see a URL response, kubectl is correctly configured to access your cluster.
|
||||||
|
|
||||||
If you see a message similar to the following, kubectl is not configured correctly or is not able to connect to a Kubernetes cluster.
|
If you see a message similar to the following, kubectl is not configured correctly or is not able to connect to a Kubernetes cluster.
|
||||||
-->
|
-->
|
||||||
如果返回一个 URL,则意味着 kubectl 成功的访问到了你的集群。
|
如果返回一个 URL,则意味着 kubectl 成功地访问到了你的集群。
|
||||||
|
|
||||||
如果你看到如下所示的消息,则代表 kubectl 配置出了问题,或无法连接到 Kubernetes 集群。
|
如果你看到如下所示的消息,则代表 kubectl 配置出了问题,或无法连接到 Kubernetes 集群。
|
||||||
|
|
||||||
|
@ -52,11 +58,12 @@ The connection to the server <server-name:port> was refused - did you specify th
|
||||||
For example, if you are intending to run a Kubernetes cluster on your laptop (locally), you will need a tool like Minikube to be installed first and then re-run the commands stated above.
|
For example, if you are intending to run a Kubernetes cluster on your laptop (locally), you will need a tool like Minikube to be installed first and then re-run the commands stated above.
|
||||||
|
|
||||||
If kubectl cluster-info returns the url response but you can't access your cluster, to check whether it is configured properly, use:
|
If kubectl cluster-info returns the url response but you can't access your cluster, to check whether it is configured properly, use:
|
||||||
-->
|
-->
|
||||||
例如,如果你想在自己的笔记本上(本地)运行 Kubernetes 集群,你需要先安装一个 Minikube 这样的工具,然后再重新运行上面的命令。
|
例如,如果你想在自己的笔记本上(本地)运行 Kubernetes 集群,你需要先安装一个 Minikube
|
||||||
|
这样的工具,然后再重新运行上面的命令。
|
||||||
|
|
||||||
如果命令 `kubectl cluster-info` 返回了 url,但你还不能访问集群,那可以用以下命令来检查配置是否妥当:
|
如果命令 `kubectl cluster-info` 返回了 URL,但你还不能访问集群,那可以用以下命令来检查配置是否妥当:
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
kubectl cluster-info dump
|
kubectl cluster-info dump
|
||||||
```
|
```
|
||||||
|
|
Loading…
Reference in New Issue