β Exiting due to GUEST_START: failed to start node: wait 6m0s for node: wait for healthy API server: apiserver healthz never reported healthy: context deadline exceeded #19388
Labels
kind/support
Categorizes issue or PR as a support question.
What Happened?
Running the command
causes the error
π minikube v1.31.2 on Centos 9
β¨ Using the docker driver based on existing profile
π Starting control plane node minikube in cluster minikube
π Pulling base image ...
π Updating the running docker "minikube" container ...
β This container is having trouble accessing https://registry.k8s.io
π‘ To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/
π³ Preparing Kubernetes v1.27.4 on Docker 24.0.4 ...
π€¦ Unable to restart cluster, will reset it: apiserver health: apiserver healthz never reported healthy: context deadline exceeded
βͺ Generating certificates and keys ...
βͺ Booting up control plane ...
βͺ Configuring RBAC rules ...
π Configuring bridge CNI (Container Networking Interface) ...
E0806 19:48:54.831288 1512131 start.go:219] Unable to scale down deployment "coredns" in namespace "kube-system" to 1 replica: non-retryable failure while getting "coredns" deployment scale: Get "https://192.168.49.2:8443/apis/apps/v1/namespaces/kube-system/deployments/coredns/scale": dial tcp 192.168.49.2:8443: connect: connection refused
π Verifying Kubernetes components...
βͺ Using image gcr.io/k8s-minikube/storage-provisioner:v5
β Enabling 'default-storageclass' returned an error: running callbacks: [Error making standard the default storage class: Error listing StorageClasses: Get "https://192.168.49.2:8443/apis/storage.k8s.io/v1/storageclasses": dial tcp 192.168.49.2:8443: connect: connection refused]
π Enabled addons: storage-provisioner
^[[A
β Exiting due to GUEST_START: failed to start node: wait 6m0s for node: wait for healthy API server: apiserver healthz never reported healthy: context deadline exceeded
Attach the log file
logs.txt
Operating System
Other
Driver
Docker
The text was updated successfully, but these errors were encountered: