Closed srilumpa closed 3 years ago
@srilumpa thank you for reporting this, does this happen consistantly or is it a flake?
I believe this is because the docker container IP was changed
โ Enabling 'default-storageclass' returned an error: running callbacks: [Error making standard the default storage class: Error listing StorageClasses: Get "https://172.17.0.2:8443/apis/storage.k8s.io/v1/storageclasses": x509: certificate is valid for 172.17.0.3, 10.96.0.1, 127.0.0.1, 10.0.0.1, not 172.17.0.2
I believe once we have a static IP for docker containers this error should not happen. do you mind verifying this happens only as a flake and minikube delete would fix it?
this PR might fix this issue https://github.com/kubernetes/minikube/pull/8764
but I am still puzzled why we had not seen this issue more often if that is an IP change problem.
/triage needs-information /triage support
@medyagh, thank you for your time on this.
Yes, running minikube delete
"fixes" it and I am able to start a new minikube cluster properly again
I belive this could result of the the IP change after minikube restart that could be fixed by static IP PR
the PR fixing this bug is still under works.
Steps to reproduce the issue:
In my setup, it seems that minikube changes of IP address between startups. This makes the enabling of some addons failing because the certificate is seen as invalid.
The only way for me to be able to start minikube again is to either restart my workstation (and this does not always fix the issue) or to delete my minikube instance an recreate it.
Full output of failed command:
Full output of
minikube start
command used, if not already included:Optional: Full output of
minikube logs
command: