Closed storozhilov closed 3 years ago
This was intentional, #8841 (b27440d4aeabe0657f77a02f80acd8a300d4ac4d). It doesn't really say why, though.
@sharifelgamal might have more details on what was the problem (in 1.11) ?
@sharifelgamal - any more context on this? It seems like surprisingly this once worked.
As an unrelated bug, this check should respect --force but does not appear to yet.
Interesting, that would be my fault then. I always assumed it never worked so I added that error message, I'll look into fixing it. If anyone wants to take a crack at it in the interim, take the assignment from me.
Hi to all, thank you so much for your participation!
This was intentional, #8841 (b27440d). It doesn't really say why, though.
We were facing the same behavior as it's mentioned in #8841. This was due to some ingress-related images pulling takes too much time. Ingress addon would start in the end but minikube addons enable ingress
command is to fail after 3 min timeout.
Perhaps it makes sense to revert b27440d and to re-open #8841 where a sort of a timeout increase is to be done.. Not sure. Any idea?
@storozhilov That sounds like the right idea. I'll eventually get around to open the PR to revert that change, but if someone gets to it before me then I'll be happy to review.
Hi @sharifelgamal , I've issued https://github.com/kubernetes/minikube/pull/9574 but I need to complete a CLA signing procedure which I would like to avoid for now if possible. Would you be so kind to re-issue another PR with the same changes yourself? Thanks in advance! Ilya
Sure thing @storozhilov, thanks for the help.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
/remove-lifecycle stale
Hi to all, unfortunately ingress addon stopped to work with
none
VM driver starting from v1.12.x. v1.11.0 works fine. Help please. Thanks in advance! IlyaP.S. Great product by the way :+1: Thanks!
Steps to reproduce the issue:
sudo minikube start --vm-driver=none
sudo chown -Rv $USER $HOME/.kube $HOME/.minikube
sudo minikube addons enable ingress
Full output of failed command:
Full output of
minikube start
command used, if not already included:Optional: Full output of
minikube logs
command: