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
The SPIFFE Workload API can be used to get a tls client key/certificate and keep it up to date (they typically rotate hourly). Exporters can then verify that only the spiffe id associated with Prometheus is able to fetch data from them.
I'm thinking there should be two new options added,
in scrape_config.tls_config, an option added for saying to use spiffe for this target
and an option up at the global section to specify where the spiffeSocketPath
The text was updated successfully, but these errors were encountered:
The SPIFFE Workload API can be used to get a tls client key/certificate and keep it up to date (they typically rotate hourly). Exporters can then verify that only the spiffe id associated with Prometheus is able to fetch data from them.
I'm thinking there should be two new options added,
in scrape_config.tls_config, an option added for saying to use spiffe for this target
and an option up at the global section to specify where the spiffeSocketPath
The text was updated successfully, but these errors were encountered: