Hi folks, can propeller connect to the custom agent end point from another namespace? Ideally different teams/orgs maintain/operate their own custom agents in their own namespace, separating from the propeller/scheduler/admin’s namespace, specifically, can the propeller do the end point:

service-name.namespace-name.svc.cluster.local:8000

, if the propeller is deployed in different namespace-name? My testing even shows the the same namespace does not work, except using the service name

service-name

. Anyone can shed some lights on any hard limit?

@billowy-church-83438 its just an endpoint it can you even be a separate service

yeah theoretically it is. it just weird that it just did not work in practice, as I used the service based on the regular service endpoint convention…

Kevin has tested it before, but he didn't document its details. Let's wait for him back.

sounds good. I am also testing various combination (different namespaces w/o k8s convention to access service endpoints, etc) on my side. will update back if anything.. currently only directly use IP:port can work across different namespaces