Hi Drew,
If you’re deploying on MicroK8s the ingress IP is 127.0.0.1 (you’ll need the “ingress” addon in MicroK8s enabled). I think what you’re seeing is that there are two pieces here:
- A kubernetes “service” that refers to the services running in the pods, and uses (in your case) port 8000.
- A kubernetes “ingress” definition that gets picked up by an ingress controller (in your case configured by the “ingress” addon in MicroK8s) and instructs that ingress controller how/where to route traffic.
In Juju status the ingress charm reports the service IP because that’s what used to be reported in old pod-spec-set charms, but also because there’s no way for the charm to know what the IP(s) of the ingress controller is (as far as I’m aware).
Having said that, I’ve not tested TLS myself, but I know @pjdc has. Unfortunately I’m affected by https://github.com/ubuntu/microk8s/issues/2255 so I don’t have end to end ingress working currently on my MicroK8s install to be able to confirm this either way.
Hope that helps.
Tom