kube-controller-manager-minikube

From wikieduonline
Jump to navigation Jump to search

 kubectl get pods -A
NAMESPACE     NAME                               READY   STATUS             RESTARTS         
AGE
kube-system   etcd-minikube                      1/1     Running            7 (26m ago)      
13d
kube-system   kube-apiserver-minikube            1/1     Running            7 (26m ago)      
13d
kube-system   kube-controller-manager-minikube   0/1     CrashLoopBackOff   278 (3m6s ago)   
13d
kube-system   kube-scheduler-minikube            1/1     Running            7 (26m ago)      
13d
kube-system   storage-provisioner                0/1     Pending            0                13d
k logs -n kube-system kube-controller-manager-minikube
I0116 16:08:21.718079       1 serving.go:348] Generated self-signed cert in-memory
I0116 16:08:22.018780       1 controllermanager.go:187] "Starting" version="v1.27.4"
I0116 16:08:22.018811       1 controllermanager.go:189] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
I0116 16:08:22.019624       1 dynamic_cafile_content.go:157] "Starting controller" name="request-header::/var/lib/minikube/certs/front-proxy-ca.crt"
I0116 16:08:22.020074       1 secure_serving.go:210] Serving securely on 127.0.0.1:10257
I0116 16:08:22.020075       1 dynamic_cafile_content.go:157] "Starting controller" name="client-ca-bundle::/var/lib/minikube/certs/ca.crt"
I0116 16:08:22.020187       1 tlsconfig.go:240] "Starting DynamicServingCertificateController"
E0116 16:08:32.039255       1 controllermanager.go:233] "Error building controller context" err="failed to wait for apiserver being healthy: timed out waiting for the condition: failed to get apiserver /healthz status: Get \"https://192.168.49.2:8443/healthz\": tls: failed to verify certificate: x509: certificate is valid for 192.168.58.2, 10.96.0.1, 127.0.0.1, 10.0.0.1, not 192.168.49.2"


kube-controller-manager
minikube start
minikube addons list

See also

Advertising: