I'm using the jammy64 version.
After finnish the lab, I run a nginx test deploy, pod, and installed a Nginx IngressController and tried to use with some pathprefix but nothing is working, and I discovered that my POD is not accessible from other hosts like controlplane or other node then the node that is running the pod.
I tested the WeaveNet and Flannel as well, but nothing changed.
vagrant@controlplane01:~$ k get pods -n teste-nginx -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
deploy-576c6b7b6-smzgb 1/1 Running 0 21h 10.244.0.2 node01 <none> <none>
vagrant@controlplane01:~$
Check the curl on controlplane:
vagrant@controlplane01:~$ curl -i http://10.244.0.2
curl: (28) Failed to connect to 10.244.0.2 port 80 after 130826 ms: Connection timed out
Your Workstation
Windows (10 or 11)
System Memory
16GB or more
What happened?
Running the Vagrant up I got this messages:
I'm using the jammy64 version. After finnish the lab, I run a nginx test deploy, pod, and installed a Nginx IngressController and tried to use with some pathprefix but nothing is working, and I discovered that my POD is not accessible from other hosts like controlplane or other node then the node that is running the pod. I tested the WeaveNet and Flannel as well, but nothing changed.
Check the curl on controlplane:
Test directly on node01
And of course with that my ingress rule is not working, I just got a 404 HTTP error.
I think that could be related to the two parameters that I mention on the subject, can someone help me ?
Relevant output
No response