Minikube Cluster Verification and status¶

Minikube cluster verification and status refers to the set of commands and procedures used to confirm that a local Kubernetes environment is running correctly and that the command-line tools are properly configured.

Verification Commands¶

Once the Minikube cluster has been started, the primary command used to check the overall health of the cluster is minikube status.^[400-devops__06-Kubernetes__minikube__01-install.md] This command provides a snapshot of the cluster's core components, indicating the state of the host, kubelet, and apiserver^[400-devops__06-Kubernetes__minikube__01-install.md].

A successful status check typically returns the following states for a standard single-node cluster^[400-devops__06-Kubernetes__minikube__01-install.md]: * type: Control Plane * host: Running * kubelet: Running * apiserver: Running * kubeconfig: Configured

To verify the connectivity and location of the cluster services, the kubectl cluster-info command is used^[400-devops__06-Kubernetes__minikube__01-install.md]. This outputs the URL where the Kubernetes Control Plane is running (often 127.0.0.1 on a specific port) and confirms that the CoreDNS service is accessible at the standard proxy endpoint^[400-devops__06-Kubernetes__minikube__01-install.md].

Node Verification¶

To inspect the compute resources within the cluster, kubectl get nodes is executed^[400-devops__06-Kubernetes__minikube__01-install.md]. In a standard Minikube setup, this returns a single node named minikube with the status Ready^[400-devops__06-Kubernetes__minikube__01-install.md]. The output also displays the roles assigned to the node (typically control-plane and master) as well as the Kubernetes version and the age of the node^[400-devops__06-Kubernetes__minikube__01-install.md].

Addons Management¶

Minikube extends standard Kubernetes functionality through a marketplace of addons. Users can inspect the installation status of these extensions using minikube addons list^[400-devops__06-Kubernetes__minikube__01-install.md]. This command displays a table of all available addons, their profile, and whether they are currently enabled or disabled^[400-devops__06-Kubernetes__minikube__01-install.md].

Common addons that are often enabled by default or during the initial start process include: * ingress: Enabled in the example configuration^[400-devops__06-Kubernetes__minikube__01-install.md]. * storage-provisioner: Enabled^[400-devops__06-Kubernetes__minikube__01-install.md]. * default-storageclass: Enabled^[400-devops__06-Kubernetes__minikube__01-install.md].

Sources¶

^[400-devops__06-Kubernetes__minikube__01-install.md]