How to Use the Command 'minikube' (with Examples)

Minikube is a valuable tool for developers and IT professionals who want to deploy and test Kubernetes clusters locally on their personal machines. Minikube allows you to get a feel for how Kubernetes works without needing access to a remote cluster, making it ideal for learning, development, and experimentation. You can simulate a Kubernetes environment with significantly less overhead than setting up a full-scale cluster on cloud platforms.

Start the Cluster

Code:

minikube start

Motivation: Starting a Kubernetes cluster is the first step in using Minikube. It sets up a single-node Kubernetes cluster on your local machine, which is crucial for developers looking to test applications in a Kubernetes environment without the need for a full infrastructure setup.

Explanation: The start command initializes a Kubernetes cluster using Minikube. It sets up the necessary Kubernetes components on your local machine and allocates resources for the master node and any required pods.

Example Output:

😄  minikube v1.25.2 on Ubuntu 20.04
✨  Using the docker driver based on user configuration
👍  Starting control plane node minikube in cluster minikube
🔄  Restarting existing docker container for "minikube" ...
🐳  Preparing Kubernetes v1.22.3 on Docker 20.10.8 ...
🔎  Verifying Kubernetes components...
🌟  Enabled addons: default-storageclass, storage-provisioner
🏄  Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

Get the IP Address of the Cluster

Code:

minikube ip

Motivation: Understanding the IP address associated with your Minikube cluster is essential for accessing Kubernetes services, particularly when you need to interact with applications hosted on the cluster from outside your local machine.

Explanation: The ip command returns the IP address of the Minikube cluster. This address is used for accessing services within the cluster, acting as the primary interface for connecting to Kubernetes services and applications.

Example Output:

192.168.49.2

Access a Service Named my_service Exposed via a Node Port and Get the URL

Code:

minikube service my_service --url

Motivation: Developers often need to expose and access services running on a Kubernetes cluster to test or showcase functionality. By retrieving the publicly accessible URL for a service, developers can verify that their service is correctly configured and reachable.

Explanation: This command returns the URL needed to access the specified service (my_service), which is exposed via a node port. The --url flag provides the direct URL for accessing the service, simplifying the process of interacting with your application.

Example Output:

http://192.168.49.2:32000

Open the Kubernetes Dashboard in a Browser

Code:

minikube dashboard

Motivation: The Kubernetes Dashboard is an invaluable graphical interface that helps users visualize and manage the resources in their Kubernetes clusters. Opening it allows developers to quickly view and manipulate cluster resources.

Explanation: The dashboard command launches the Kubernetes Dashboard in the default web browser, providing a comprehensive view of your cluster’s resources, including workloads, services, configurations, and other cluster details.

Example Output:

🔌  Enabling dashboard ...
🤔  Verifying dashboard health ...
🚀  Launching proxy ...
🤔  Verifying proxy health ...
🎉  Opening http://127.0.0.1:40485/api/v1/namespaces/kubernetes-dashboard/services/http:kubernetes-dashboard:/proxy/ in your default browser...

Stop the Running Cluster

Code:

minikube stop

Motivation: Stopping the Minikube cluster is crucial when you need to conserve system resources or when you’re not actively using the cluster. This command shuts down the cluster gracefully, ensuring that no unnecessary resources are consumed.

Explanation: The stop command halts the Minikube cluster, effectively putting it on pause. This action frees up CPU and memory resources that were allocated for the Kubernetes components.

Example Output:

✋  Stopping "minikube" in docker ...
🛑  Powering off "minikube" via SSH ...
🛑  Node "minikube" stopped.

Delete the Cluster

Code:

minikube delete

Motivation: Deleting a Minikube cluster is useful when you wish to completely remove the setup from your system. This is often done to reset the environment or when Minikube is no longer needed on a particular machine.

Explanation: The delete command fully removes the Minikube cluster and all associated resources from your local machine. This action is irreversible, so care should be taken before executing.

Example Output:

🔥  Deleting "minikube" in docker ...
🔥  Removing /home/user/.minikube/machines/minikube ...
💀  Removed all traces of the "minikube" cluster.

Connect to LoadBalancer Services

Code:

minikube tunnel

Motivation: Many applications require a load balancer to efficiently distribute incoming traffic among various services. The tunnel command facilitates the connection to LoadBalancer services, making it possible to test these configurations locally on Minikube.

Explanation: minikube tunnel creates a network tunnel to facilitate access to LoadBalancer services. It sets up a static IP that simulates the behavior of a LoadBalancer service on a local machine.

Example Output:

🏃  Starting tunnel for service default my-loadbalancer-service.

Conclusion

Minikube is an excellent tool for developers and IT practitioners aiming to harness the power of Kubernetes on a local machine. With commands for starting, managing, and interacting with clustered applications, Minikube provides a versatile and user-friendly way to develop and test in a Kubernetes environment. By understanding and using these commands, users can fully leverage Minikube to meet their development and learning objectives.