Minikube
Shakeout or debug your container services prior to deploying to Kubernetes.
Note
All Kubernetes manifests are expected to be in the MAKESTER__K8_MANIFESTS directory (defaults to $MAKESTER__WORK_DIR/k8s/manifests).
Warning
Care must be taken when managing multiple Kubernetes contexts. kubectl will operate against the active context.
The Makester minikube subsystem is an optional facility as it requires binaries that you will need
to install yourself. In the case of Kubernetes minikube, you can get the link to the installation
notes to minikube with:
For Kubernetes cluster interactions:
The Makester minikube subsystem help lists the available commands:
Command reference
Check Minikube local cluster status
Start Minikube locally and create a cluster (docker driver)
Access the Kubernetes dashboard (Ctrl-C to stop)
Stop Minikube local cluster
Delete Minikube local cluster
Get service access details
Note
Only applicable if LoadBalancer type is specified in your Kubernetes manifest.
Check current kubectl context
Note
Current context name is delimited with the *:
Change kubectl context
Change kubectl to the minikube context
Create Kubernetes resource(s)
Builds all manifest files in MAKESTER__K8_MANIFESTS directory:
Delete Kubernetes resource(s)
Deletes all manifest files in MAKESTER__K8_MANIFESTS directory:
View the pods and services
Variables
MAKESTER__MINIKUBE_EXE_NAME
The name of the binary Makester will search for in your PATH (defaults to minikube).
MAKESTER__MINIKUBE_EXE_NAME can be overridden if you have special requirements, or want to use a
minikube executable that is not in your PATH. Just set MAKESTER__MINIKUBE_EXE_NAME to your
preferred value in your Makefile:
MAKESTER__MINIKUBE_EXE_INSTALL
URL link that provides the instructions for installing the minikube binary. To print the URL
link:
MAKESTER__MINIKUBE
The path to the minikube binary as determined by Makester. Use MAKESTER__MINIKUBE for custom
minikube commands in your own Makefile.
Note
Override MAKESTER__MINIKUBE has no effect as it is dynamically generated by Makester based on the value of MAKESTER__MINIKUBE_EXE_NAME.
MAKESTER__KUBECTL_EXE_NAME
The name of the binary Makester will search for in your PATH (defaults to kubectl).
MAKESTER__KUBECTL_EXE_NAME can be overridden if you have special requirements, or want to use a
kubectl executable that is not in your PATH. Just set MAKESTER__KUBECTL_EXE_NAME to your
preferred value in your Makefile:
MAKESTER__KUBECTL_EXE_INSTALL
URL link that provides the instructions for installing the kubectl binary. To print the URL
link:
MAKESTER__KUBECTL
The path to the kubectl binary as determined by Makester. Use MAKESTER__KUBECTL for custom
kubectl commands in your own Makefile.
Note
Override MAKESTER__KUBECTL has no effect as it is dynamically generated by Makester based on the value of MAKESTER__KUBECTL_EXE_NAME.