Comment 4 for bug 1867168

Thanks for the extra info - very useful :-)
I'd suggest that it's not best practice to access pods directly, especially outside the namespace
hosting them. The idiomatic k8s way is to do this via services which sit in front of the pods in question, and use selectors to associate themselves with the relevant pod(s).

Juju currently only supports setting up a single service to sit in front of all the application pods as a whole. We'll need to do some feature work to support anything different.