On Minikube, if KubePlus helm chart is deleted and then deployed again, it fails to start.
The "crd-hook" container shows the following error:
Trying inClusterConfig..Inside setup
Inside GetExistingResourceCompositions...
Url:http://localhost:5005/resourcecompositions
panic: Failed to load key pair: open /etc/webhook/certs/cert.pem: no such file or directory
goroutine 1 [running]:
main.main()
/home/vagrant/go/src/github.com/cloud-ark/kubeplus/mutating-webhook/main.go:41 +0x7bc
On Minikube, if KubePlus helm chart is deleted and then deployed again, it fails to start.
The "crd-hook" container shows the following error:
Trying inClusterConfig..Inside setup
Inside GetExistingResourceCompositions...
Url:http://localhost:5005/resourcecompositions
panic: Failed to load key pair: open /etc/webhook/certs/cert.pem: no such file or directory
goroutine 1 [running]:
main.main()
/home/vagrant/go/src/github.com/cloud-ark/kubeplus/mutating-webhook/main.go:41 +0x7bc