https://rancher.com/ logo
Title
a

ancient-painter-37799

12/10/2022, 3:01 AM
Hi, I am new to kubernetes and rancher and had a networking question for local installation of rancher desktop on Mac M1. I have a container that needs to post/get via python to another container. They can use the internal service to get access but I would like to use the egress url. That doesn't seem to work. Is there a way to update the rancher dns to automatically add the egress hostnames to the dns? using WGET, I see the other container using service address: /app # wget forms-flow-forms:3001 Connecting to forms-flow-forms:3001 (10.43.229.6:3001) saving to 'index.html' index.html 100% |***************************************************************************************************************************************************| 2195 0:00:00 ETA 'index.html' saved Using egress url, no go: /app # wget http://forms-flow-forms-flow.localhost wget: bad address 'forms-flow-forms-flow.localhost' But from my browser, i have access to: http://forms-flow-forms-flow.localhost (edited)
FYI, if I add the ingress url's to my /etc/hosts on the 127.0.0.0 line, it works but hoping it was automatic within rancher's dns
But doesn't resolve post to the same url ­čś×
c

calm-sugar-3169

12/12/2022, 10:29 PM
@ancient-painter-37799 wget and curl don't necessarily treat *.localhost the way browsers (e.g chrome) do. e.g https://github.com/curl/curl/issues/9192
a

ancient-painter-37799

12/13/2022, 6:48 PM
So the issue is different. I was just checking to see if the pods could talk to each other. The issue is the web (node.js) container builds a payload using the ingress url that will be used another containers post command. But uses the ingress url to build the payload and the other API container has no clue about the ingress url and fails ­čś×. Not sure how to resolve this.. sigh.