<p>Why kubectl cluster-info is running on <strong>control plane</strong> and not <strong>master node</strong>
And on the control plane it is running on a specific IP Address <strong><a href="https://192.168.49.2:8443" rel="nofollow noreferrer">https://192.168.49.2:8443</a></strong>
and not not <strong>localhost</strong> or <strong>127.0.0.1</strong>
Running the following command in terminal:</p>
<ol>
<li>minikube start --driver=docker</li>
</ol>
<blockquote>
<p>😄  minikube v1.20.0 on Ubuntu 16.04
✨  Using the docker driver based on user configuration
🎉  minikube 1.21.0 is available! Download it: <a href="https://github.com/kubernetes/minikube/releases/tag/v1.21.0" rel="nofollow noreferrer">https://github.com/kubernetes/minikube/releases/tag/v1.21.0</a>
💡  To disable this notice, run: 'minikube config set WantUpdateNotification false'</p>
</blockquote>
<blockquote>
<p>👍  Starting control plane node minikube in cluster minikube
🚜  Pulling base image ...
&gt; 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 &quot;minikube&quot; cluster and &quot;default&quot; namespace by
default</p>
</blockquote>
<ol start="2">
<li>kubectl cluster-info</li>
</ol>
<blockquote>
<p>Kubernetes control plane is running at <a href="https://192.168.49.2:8443" rel="nofollow noreferrer">https://192.168.49.2:8443</a>
KubeDNS is running at <a href="https://192.168.49.2:8443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy" rel="nofollow noreferrer">https://192.168.49.2:8443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy</a></p>
</blockquote>
<blockquote>
<p>To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.</p>
</blockquote>

teodoro
<p>The Kubernetes project is making an effort to move away from wording that can be considered offensive, with one concrete recommendation being <a href="https://github.com/kubernetes/community/blob/master/wg-naming/recommendations/001-master-control-plane.md" rel="noreferrer">renaming master to control-plane</a>. In other words <code>control-plane</code> and <code>master</code> mean essentially the same thing, and the goal is to switch the terminology to use <code>control-plane</code> exclusively going forward. (More info in <a href="https://stackoverflow.com/questions/66186014/what-is-the-difference-between-kubernetes-labels-node-role-kubernetes-io-master/66186779#66186779">this answer</a>)</p>
<p>The <code>kubectl</code> command is a command line interface that executes on a client (i.e your computer) and interacts with the cluster through the <code>control-plane</code>.
The IP address you are seing through <code>cluster-info</code> is the IP address through which you reach the control-plane</p>
