minikube addons enable ingress not working on mac

[joshuamataaraya]

Steps to reproduce the issue:

Run the following commands:

minikube config set vm-driver hyperkit
minikube delete
minikube start
minikube addons enable ingress

Full output of failed command:
❗ These changes will take effect upon a minikube delete and then a minikube start
🔥 Deleting "minikube" in hyperkit ...
💀 Removed all traces of the "minikube" cluster.
😄 minikube v1.19.0 on Darwin 11.2.3
✨ Using the hyperkit driver based on user configuration
👍 Starting control plane node minikube in cluster minikube
🔥 Creating hyperkit VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
❗ This VM is having trouble accessing https://k8s.gcr.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.20.2 on Docker 20.10.4 ...
▪ Generating certificates and keys ...
▪ Booting up control plane ...
▪ Configuring RBAC rules ...
🔎 Verifying Kubernetes components...
▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🌟 Enabled addons: default-storageclass, storage-provisioner
🏄 Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
▪ Using image k8s.gcr.io/ingress-nginx/controller:v0.44.0
▪ Using image docker.io/jettech/kube-webhook-certgen:v1.5.1
▪ Using image docker.io/jettech/kube-webhook-certgen:v1.5.1
🔎 Verifying ingress addon...

❌ Exiting due to MK_ENABLE: run callbacks: running callbacks: [waiting for app.kubernetes.io/name=ingress-nginx pods: timed out waiting for the condition]

😿 If the above advice does not help, please let us know:
👉 https://github.com/kubernetes/minikube/issues/new/choose

Running this on mac Big Sur 11.2.3

[spowelljr]

@joshuamataaraya Someone had this same issue #11147 they deleted ~/.minikube and their issue was fixed. Did you update from an older version of minikube before v1.19.0?

[btalbot]

ingres for 1.19 seems all sorts of messed up. Other reports for the ingress addon not starting at all seem to implicate the pod images not being available. For me, those are available and the ingress addon does start clearnly ... however.

MacOS 11.2.3 with the virtualbox driver and the ingress addon seems to start up just fine but then any attempt to create an Ingres object is rejected by the admission controller webhook at least from the logs of the ingress-nginx-controller pod:

E0420 02:18:41.607124       9 server.go:84] "failed to process webhook request" err="rejecting admission review because the request does not contain an Ingress resource but networking.k8s.io/v1, Kind=Ingress with name nemo-ingress in namespace nemo"

Ingress object is

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  namespace: nemo
  name: nemo-ingress
spec:
  rules:
...

[edit] I forgot to note that deleting the ValidatingWebhookConfiguration/ingress-nginx-admission allows the ingress to be deployed.

[medyagh]

thank you everyone for reporting this bug, this seems to be side effect of this PR #10879 that we tried to update the ingress to new version, unfortunately our integration test did not catch this problem,
Please stay tuned, we will create a fix for this and hopefully by adding an integration test this should never happen again.

Thank you for your patience

@joshuamataaraya @btalbot I will close this issue to track in it here

meanwhile could you try

kubectl delete -A ValidatingWebhookConfiguration ingress-nginx-admission

and see if that fixes the problem ?

dupe of #11121