Enhancement Proposal
When traefik-k8s is deployed, it creates a Kubernetes LoadBalancer service. In many environments, that service gets a public IP assigned by the underlying cloud provider.
At the moment, I do not see that information exposed through Juju, for example through juju show-unit. Because of that, we currently query the Kubernetes API directly to retrieve the Traefik LoadBalancer address.
I would like to avoid depending on the Kubernetes API for this, and instead have the address exposed through Juju. It would be helpful if the charm exposed the external LoadBalancer address through a juju action.
Impact
Medium (The feature may be helpful in the future)
Impact Rationale
No response
Enhancement Proposal
When traefik-k8s is deployed, it creates a Kubernetes LoadBalancer service. In many environments, that service gets a public IP assigned by the underlying cloud provider.
At the moment, I do not see that information exposed through Juju, for example through
juju show-unit. Because of that, we currently query the Kubernetes API directly to retrieve the Traefik LoadBalancer address.I would like to avoid depending on the Kubernetes API for this, and instead have the address exposed through Juju. It would be helpful if the charm exposed the external LoadBalancer address through a juju action.
Impact
Medium (The feature may be helpful in the future)
Impact Rationale
No response