minikube can't re-configure ingress to use a different ssl certificate

[LanDinh]

Steps to reproduce the issue:

Tutorial that was followed: https://minikube.sigs.k8s.io/docs/tutorials/custom_cert_ingress/

1. start minikube locally minikube start
2. enable ingress minikube addons enable ingress
3. add the auto-generated certificate in .pem:
4. kubectl -n kube-system create secret tls mkcert --key ~/.minikube/key.pem --cert ~/.minikube/cert.pem
5. minikube addons configure ingress
6. In the prompt to add the certificate: be stupid and have a typo: bogus-namespace/mkcert
7. Re-enable the ingress:
8. minikube addons disable ingress
9. minikube addons enable ingress
10. Notice the mistake
11. Try to re-configure the ingress: minikube addons configure ingress
12. instead of getting the prompt again, it auto-proceeds to ingress was successfully configured <--- this is the bug! Why would I be stuck with this typo forever?

Run minikube logs --file=logs.txt and drag and drop the log file into this issue

Full output of failed command if not minikube start:

[medyagh]

cc: @sharifelgamal

[sharifelgamal]

yeah, I can reproduce this pretty easily, it seems like it's by design:

minikube/cmd/minikube/cmd/config/configure.go

Lines 223 to 225 in 2ec8875

	if cfg.KubernetesConfig.CustomIngressCert == "" {
	cfg.KubernetesConfig.CustomIngressCert = AskForStaticValidatedValue("-- Enter custom cert(format is \"namespace/secret\"): ", validator)
	}

I agree that calling minikube addons configure ingress should allow for overriding existing config, so I'll add it our short term work to fix.

[medyagh]

@LanDinh

There is a PR that might fix this issue, here is the link to the binary from a PR that I think might fix this issue, do you mind trying it out ?

http://storage.googleapis.com/minikube-builds/12897/minikube-linux-amd64
http://storage.googleapis.com/minikube-builds/12897/minikube-darwin-amd64
http://storage.googleapis.com/minikube-builds/12897/minikube-windows-amd64.exe

[LanDinh]

I confirm that this is working - I especially like the warning about overwriting an existing certificate :) thanks!