linux - kubectl cluster-info 为什么在控制平面而不是主节点上运行

Question

为什么 kubectl cluster-info 运行在control plane 而不是 ma​​ster 节点在控制平面上，它在特定的 IP 地址 https://192.168.49.2:8443 上运行而不是 localhost 或 127.0.0.1在终端中运行以下命令:

1. minikube 启动 --driver=docker

😄 minikube v1.20.0 on Ubuntu 16.04✨ Using the docker driver based on user configuration🎉 minikube 1.21.0 is available! Download it: https://github.com/kubernetes/minikube/releases/tag/v1.21.0💡 To disable this notice, run: 'minikube config set WantUpdateNotification false'

👍 Starting control plane node minikube in cluster minikube🚜 Pulling base image ...> gcr.io/k8s-minikube/kicbase...: 358.10 MiB / 358.10 MiB 100.00% 797.51 K❗ minikube was unable to download gcr.io/k8s-minikube/kicbase:v0.0.22, but successfully downloaded kicbase/stable:v0.0.22 as a fallback image🔥 Creating docker container (CPUs=2, Memory=2200MB) ...🐳 Preparing Kubernetes v1.20.2 on Docker 20.10.6 ...▪ Generating certificates and keys ...▪ Booting up control plane ...▪ Configuring RBAC rules ...🔎 Verifying Kubernetes components...▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5🌟 Enabled addons: storage-provisioner, default-storageclass🏄 Done! kubectl is now configured to use "minikube" cluster and "default" namespace bydefault

1. kubectl 集群信息

Kubernetes control plane is running at https://192.168.49.2:8443KubeDNS is running at https://192.168.49.2:8443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

Answer 1

Kubernetes 项目正在努力摆脱被认为具有攻击性的措辞，其中一项具体建议是 renaming master to control-plane .换句话说 control-plane 和 master 本质上是同一件事，目标是切换术语以专门使用 control-plane向前。 (更多信息在 this answer 中)

kubectl 命令是在客户端(即您的计算机)上执行并通过控制平面 与集群交互的命令行界面。您通过 cluster-info 看到的 IP 地址是您到达控制平面的 IP 地址