Closed GH-Djeff closed 3 years ago
We don't support the ingress addon with the none driver, we should fail with a good error message, rather than just spewing logs.
/assign
@sharifelgamal I'd appreciate if you could take a look at #8870 when you get a chance to see if the warning message is good.
I think we've done the wrong thing here, we should remove that warning and increase the addons timeout instead.
It's not convenient where minikube changed default driver between minor releases So short solution for now is to specify excplicitly vm driver. For instance for mac os it could be
minikube start --driver='hyperkit' && \
minikube addons enable ingress
For linux I use next bootstrap command
minikube start --driver='docker' && \
minikube addons enable ingress
When will we be able to use ingress addon with Docker driver on Mac?
@marcusthelin we have an issue (https://github.com/kubernetes/minikube/issues/7332) specifically tracking ingress on docker macos. it's one of our top priorities.
@sharifelgamal Thank you!
closing this in favor of https://github.com/kubernetes/minikube/issues/7332
Steps to reproduce the issue: Hello i'm trying to enable ingress addons in minikube
1.root@kmaster-01:/etc/kubernetes/Ingress# minikube addons enable ingress 🔎 Verifying ingress addon...
💣 enable failed: run callbacks: running callbacks: [verifying ingress addon pods : timed out waiting for the condition: timed out waiting for the condition]
😿 minikube is exiting due to an error. If the above message is not useful, open an issue: 👉 https://github.com/kubernetes/minikube/issues/new/choose
Full output of failed command: 1.root@kmaster-01:/etc/kubernetes/Ingress# minikube addons enable ingress 🔎 Verifying ingress addon...
💣 enable failed: run callbacks: running callbacks: [verifying ingress addon pods : timed out waiting for the condition: timed out waiting for the condition]
😿 minikube is exiting due to an error. If the above message is not useful, open an issue: 👉 https://github.com/kubernetes/minikube/issues/new/choose
Full output of
minikube start
command used, if not already included: root@kmaster-01:/etc/kubernetes/Ingress# minikube start 😄 minikube v1.12.1 on Debian bullseye/sid ✨ Using the none driver based on existing profile 👍 Starting control plane node minikube in cluster minikube 🏃 Updating the running none "minikube" bare metal machine ... ℹ️ OS release is Debian GNU/Linux bullseye/sid 🐳 Preparing Kubernetes v1.18.3 on Docker 19.03.12 ... 🤹 Configuring local host environment ...❗ The 'none' driver is designed for experts who need to integrate with an existing VM 💡 Most users should use the newer 'docker' driver instead, which does not require root! 📘 For more information, see: https://minikube.sigs.k8s.io/docs/reference/drivers/none/
❗ kubectl and minikube configuration will be stored in /root ❗ To use kubectl or minikube commands as your own user, you may need to relocate them. For example, to overwrite your own settings, run:
💡 This can also be done automatically by setting the env var CHANGE_MINIKUBE_NONE_USER=true 🔎 Verifying Kubernetes components... 🌟 Enabled addons: dashboard, default-storageclass, storage-provisioner 🏄 Done! kubectl is now configured to use "minikube"
Optional: Full output of
minikube logs
command: