Minikube cluster
Minikube software runs a single-node Kubernetes cluster in a virtual machine.
The cluster/minikube/cdk-minikube start command creates a Minikube cluster with a configuration that’s adequate for a CDK deployment.
-
Determine which virtual machine driver you want Minikube to use. By default, the cdk-minikube command, which you run in the next step, starts Minikube with:
-
The Hyperkit driver on Intel x86-based macOS systems
-
The Docker driver on ARM-based macOS systems[1]
-
The Docker driver on Linux systems
The default driver option is fine for most users. For more information about Minikube virtual machine drivers, refer to Drivers in the Minikube documentation.
If you want to use a driver other than the default driver, specify the
--driveroption when you run the cdk-minikube command in the next step. -
-
Set up Minikube:
$ cd /path/to/forgeops/cluster/minikube $ ./cdk-minikube start Running: "minikube start --cpus=3 --memory=9g --disk-size=40g --cni=true --kubernetes-version=stable --addons=ingress,volumesnapshots --driver=hyperkit" 😄 minikube v1.30.1 on Darwin 13.2.1 ✨ Using the hyperkit driver based on user configuration 👍 Starting control plane node minikube in cluster minikube 🔥 Creating hyperkit VM (CPUs=3, Memory=9216MB, Disk=40960MB) ... 🐳 Preparing Kubernetes v1.26.3 on Docker 20.10.23 ... ▪ Generating certificates and keys ... ▪ Booting up control plane ... ▪ Configuring RBAC rules ... 🔗 Configuring CNI (Container Networking Interface) ... ▪ Using image registry.k8s.io/sig-storage/snapshot-controller:v6.1.0 ▪ Using image registry.k8s.io/ingress-nginx/controller:v1.7.0 ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5 ▪ Using image registry.k8s.io/ingress-nginx/kube-webhook-certgen:v20230312-helm-chart-4.5.2-28-g66a760794 ▪ Using image registry.k8s.io/ingress-nginx/kube-webhook-certgen:v20230312-helm-chart-4.5.2-28-g66a760794 ▪ Using image registry.k8s.io/metrics-server/metrics-server:v0.6.3 🔎 Verifying Kubernetes components ... 🔎 Verifying ingress addon ... 🌟 Enabled addons: storage-provisioner, metrics-server, default-storageclass, volumesnapshots, ingress 🏄 Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default -
Verify that your Minikube cluster is using the expected driver. For example:
Running: "minikube start --cpus=3 --memory=9g --disk-size=40g --cni=true --kubernetes-version=stable --addons=ingress,volumesnapshots --driver=hyperkit" 😄 minikube v1.30.1 on Darwin 13.2.1 ✨ Using the hyperkit driver based on user configuration ...
If you are running Minikube on an ARM-based macOS system and the cdk-minikube output indicates that you are using the qemu driver, you probably have not started the virtual machine that runs your Docker engine.