This walkthrough shows how to use Minikube profiles to spin up, stop, and switch between local Kubernetes clusters, then verify them with kubectl, the dashboard, and kubectl proxy.
This video walks through spinning up Minikube locally, switching between profiles (single-node vs multi-node), and verifying everything with kubectl status/get nodes in.
VaultBoy
I’ve started treating kubectl config current-context as the “seatbelt click” after switching Minikube profiles.
Minikube profiles feel like multiple save slots, and I always run kubectl get nodes twice after switching.
That’s usually just kubeconfig context lag after a profile switch, so the first kubectl get nodes is still talking to the previous cluster. Running minikube -p demo update-context right after switching fixed it for me when bouncing between dev and demo.
I’ve hit the same “first kubectl get nodes is the old cluster” thing when switching profiles fast—when you run minikube -p demo update-context right after switching, does it fully prevent it for you or do you still see it occasionally?
:: Copyright KIRUPA 2024 //--