This companion guide provides the detailed engineering documentation behind Lab 01 – Minikube Installation and Verification.
Topics covered include environment preparation, cluster deployment, validation procedures, rollout history research, deployment revision management, rollback concepts, troubleshooting, and lessons learned.
This lab was performed using an Ubuntu virtual machine with Docker, kubectl, and Minikube installed. The objective was to establish a local Kubernetes environment and verify that all core cluster components were operational before deploying workloads.
This companion document provides the detailed engineering notes behind Lab 01 – Minikube Installation and Verification. It includes deployment observations, validation steps, rollout history research, troubleshooting notes, and lessons learned.
A local Kubernetes cluster was deployed using Minikube. Initial validation focused on confirming successful startup of the Kubernetes control plane and validating communication with cluster services.
The following commands were used to deploy the cluster and verify basic Kubernetes functionality.
minikube start
minikube status
kubectl get nodes
kubectl cluster-info
kubectl rollout history deployment/nginx
kubectl rollout history deployment/nginx --revision=2
Displays the deployment revision history and allows inspection of a specific deployment revision.
Post-deployment validation confirmed that Kubernetes services were operational and ready for workload deployment. Verification focused on cluster health, node readiness, API availability, and dependency status.
Additional lab work focused on understanding how Kubernetes tracks deployment changes through rollout history. This exercise provided insight into revision management, deployment updates, and operational troubleshooting techniques.
kubectl rollout history deployment/nginx
kubectl rollout history deployment/nginx --revision=2
Testing demonstrated that Kubernetes creates a new deployment revision only when the deployment specification changes. Reapplying an identical image does not generate a new revision, while updating the deployment image version creates a new rollout.
kubectl set image deployment/nginx nginx=nginx:1.27
kubectl rollout status deployment/nginx
kubectl rollout history deployment/nginx
Rollout history provides visibility into previous deployment configurations and supports rollback operations. This capability allows administrators to investigate deployment changes and recover from unsuccessful updates.
kubectl rollout status deployment/nginx
kubectl rollout history deployment/nginx
kubectl rollout undo deployment/nginx