You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TODO: GrafanaSourceProvider: source_url should be a callable, to solve code ordering issue. We already have a public .update_source() method, so hopefully that will suffice.
With ingress per app, is it correct for all units of the same app have the same web_external_url in their certificate's SANs? I.e. would a CA complain if asked to generate two different certs for the same DNS? (The SANs of a unit's cert is made up of the unit's FQDN and the app's external url)
Should we also allow provisioning certificates with IPs as part of the SAN?
The text was updated successfully, but these errors were encountered:
Enhancement Proposal
This is a tracking issue for end-to-end TLS in COS Lite.
Spec
TODO: Update
Steps / History
Traefik
mutual_tls
misnomer) traefik-k8s-operator#204 @PietroPasotti @lucabelloloadBalancer.servers[].url
traefik-k8s-operator#219Loki
Alertmanager
Prometheus
Prometheus – Alertmanager
Prometheus - grafana agent
Grafana agent
Grafana
TODO: GrafanaSourceProvider:We already have a publicsource_url
should be a callable, to solve code ordering issue..update_source()
method, so hopefully that will suffice.Catalogue
For the whole stack
insecureSkipVerify
To do later
Won't do
Unresolved Questions
web_external_url
in their certificate's SANs? I.e. would a CA complain if asked to generate two different certs for the same DNS? (The SANs of a unit's cert is made up of the unit's FQDN and the app's external url)The text was updated successfully, but these errors were encountered: