-
Start the Minikube cluster
$ minikube start --cpus 2 --memory 8192
You should see
Kubectl is now configured to use the cluster
-
Verify the Minikube cluster
a.
$ kubectl config use-context minikube
You should see `Switched to context "minikube"`
b.
$ kubectl cluster-info
You should see
Kubernetes master is running at https://192.168.99.100:8443
c.
$ kubectl get nodes
NAME STATUS ROLES AGE VERSION minikube Ready master 24d v1.10.0
-
Create configmaps; otherwise the ingress controller will throw
Error getting ConfigMap
$ kubectl apply -f https://github.com/kubernetes/minikube/blob/master/deploy/addons/ingress/ingress-configmap.yaml
-
Enable the ingress add-on
a.
$ minikube addons enable ingress
You should see
ingress was successfully enabled
b.
$ kubectl -n kube-system get pods
NAMESPACE NAME READY STATUS RESTARTS AGE kube-system nginx-ingress-controller-xxxxxxxxxx-xxxxx 1/1 Running 0 39s Wait for the controller to start. It may take a few minutes.
-
Review the logs to verify the installation. This is also useful for troubleshooting ingress resources.
$ kubectl -n kube-system logs <POD_NAME>
You should see
successfully acquired lease kube-system/ingress-controller-leader-nginx
To install tiller
into the minikube cluster
-
$ kubectl use-context minikube
-
$ helm init
.This command validates the helm client is installed correctly and initializes it up if necessary. Then, it connects to the minikube cluster and installs
tiller
into thekube-system
namespace. -
$ kubectl -n kube-system get pods
You should see
tiller
runningNAMESPACE NAME READY STATUS RESTARTS AGE kube-system tiller-deploy-xxxxxxxxxx-xxxxx 1/1 Running 0 39s Wait for the tiller to start. It may take a few minutes.
-
Review the logs to verify the installation.
$ kubectl -n kube-system logs POD_NAME
You should see
Starting Tiller v2.11.0 (tls=false)
The Kubernetes Dashboard can be useful for managing and troubleshooting your cluster
$ minikube dashboard
This command opens the Kubernetes Dashboard in a browser