Access pods inside colima kubernetes cluster with curl

[gotpist1]

Hello! We have switched from minikube and using Colima with kubernetes. Everything fires up and internaly, pods can talk to eachother. Now, i want to be able to curl a pods health endpoint but with no prevail. I have started an ingress-controller following:

#133

And that seems to work well. But still, i cant call a pod from my host machine. Any insight on what might be missing?

[abiosoft]

@gotpist1 are the pods exposed behind a service? If yes, LoadBalancer or NodePort?

[gotpist1]

It's ClusterIp services. But i have enabled an nginx ingress controller inside the cluster. Then i have a config map that explains the different adressess.

[gotpist1]

Im thinking that i might need to expose the controller to my host with a NodePort service maybe.

[gotpist1]

Ok. So i followed this approach instead: https://blog.dustinrue.com/2022/08/colima-kubernetes-and-helm-chart-testing/comment-page-1/#comment-61503

But that doesn't work either. Everything seems to be in order, but still gets connection refused when trying to curl my host. FUDGE!

[abiosoft]

Can you share your setup or yaml files? Or maybe run something simple at first.

What is the output of kubectl get services?

[abiosoft]

Is the ingress not reachable without https? i.e. http://192.168.106.2/userpod/monitor/info/

[gotpist1]

Also, if i run curl against the external ip without https, i hit the nginx but get a 404 not found. That is to be expected, because in my ingress i specify the host seen above.

I have added a entry in my hosts file that points the external ip against my host aswell.

[gotpist1]

I need to be able to resolve the host, so i can use tls and let the ingress route me to the right place.

This might be an issue with my companys setup, but it worked fine on intel mac with minikube :(

[gotpist1]

if i use curl with the --resolve flag, it works. But that is not really ideal.

curl --resolve 'dmdp.localhost:443:192.168.106.2' https://dmdp.localhost/userpod/monitor/info -k

[gotpist1]

Just wanted to let you know that i solved this. Apparently, using an alias that ends with ".localhost" made everything act up real bad. As soon as i switched to ".local" everything worked as expected :)