问题原文
原帖链接 · nugetminer23 · CC BY-SA 4.0
so I just got started digging into minikube after having problems with the docker-desktop here and there. I am following https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/, but I'm running into a problem.
I did exactly what the tutorial explains:
- Enable the ingress addon in minikube (Does this work with self-deployed ingress controller installed via helm as well, by the way?)
- Deployed an application
- Created the corresponding Ingress configuration
I verified all is available, and end up with the following output of kubectl get ingress:
NAME CLASS HOSTS ADDRESS PORTS AGE
example-ingress <none> hello-world.info 192.168.49.2 80 87m
However, when trying to access hello-world.info (either that, setup in my hosts file, or 192.168.49.2 directly, just for connectivity testing), I'm getting absolutely nothing besides request timeouts. The logs of my ingress-controller also don't mention any failed connection attempts.
The connection works just fine when manually starting a tunnel via minikube service ingress-nginx-controller-admission --namespace=kube-system.
Here's the output of minikube profile list:
|----------|-----------|---------|--------------|------|---------|---------|-------|
| Profile | VM Driver | Runtime | IP | Port | Version | Status | Nodes |
|----------|-----------|---------|--------------|------|---------|---------|-------|
| minikube | docker | docker | 192.168.49.2 | 8443 | v1.20.2 | Running | 1 |
|----------|-----------|---------|--------------|------|---------|---------|-------|
I'm running this example on a Windows machine via the docker-desktop runtime.
Where am I going wrong? My ultimate goal is to enable a docker-desktop like experience via my ingress. I don't want to have to manually enable / disable tunnels to access my cluster.
已采纳解答
原帖链接 · Wytrzymały Wiktor · CC BY-SA 4.0
(Does this work with self-deployed ingress controller installed via helm as well, by the way?)
minikube addons enable ingressenables the minikube implementation of the Nginx Ingress
My ultimate goal is to enable a docker-desktop like experience via my ingress. I don't want to have to manually enable / disable tunnels to access my cluster.
- Unfortunately, it is working as expected. After enabling ingress addon it is specifically stated that:
After the addon is enabled, please run "minikube tunnel" and your ingress resources would be available at "127.0.0.1". So in this scenario when using Minikube on Windows you are actually supposed to use minikube tunnel. Bear in mind that Minikube is mainly used for testing and learning purposes so some of it's features might not be ideal.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
