Note: this config option shouldn't be included when you're using the "ingress"
relation (e.g. traefik) - the charm will automatically assign an external url
to --web.external-url when related to an ingress provider.
There seems to be a bug where the correct URL is not passed from the ingress relation through to pebble. This affects the URL that is present on alert messages. Instead of the public URL the local cluster URL is passed which makes it hard to view the alert.
To Reproduce
Note: I've deployed COS via a Terraform module and the issue is present, on two separate environments.
Bug Description
When pebble runs the alertmanager service it configures the flag
--web.external-url
which from what I can tell is,The alertmanager-k8s charm config for web-external-url states
There seems to be a bug where the correct URL is not passed from the ingress relation through to pebble. This affects the URL that is present on alert messages. Instead of the public URL the local cluster URL is passed which makes it hard to view the alert.
To Reproduce
Note: I've deployed COS via a Terraform module and the issue is present, on two separate environments.
juju deploy alertmanger-k8s
juju deploy traefik-k8s
juju relate alertmanager-k8s traefik-k8s
kubectl exec -it alertmanager-k8s/0 -c alertmanager -- bash
/charm/bin/pebble plan
Observe incorrect address configured.
Environment
Relevant log output
Output from unit (only the relevant relations)