Closed eyenx closed 2 months ago
@tvoran @swenson @tomhjp
Anyone able to review this pls? It's kinda sad this is laying around without reaction for more than 3 months.
I would also like to see this feature added to the chart.
If possible the chance to configure bearerTokenSecret
would also be welcomed.
I would also like to see this feature added to the chart.
If possible the chance to configure
bearerTokenSecret
would also be welcomed.
Would be nice I know, but HashiCorp does not care about contributions from outsiders. This will be laying around forever or they will implement it by themselves.
Thank you @tomhjp will look at it today
@tomhjp ready for a review :)
Hey @eyenx, thanks for your patience. I wanted to try writing a proper integration test that exercised these options for real, I've pushed some WIP in (EDIT) https://github.com/hashicorp/vault-helm/commit/c66c9a26fa4bc237ca94c56c0271ec4525977d53.
One thing I learnt while I was looking deeper is that the bearerTokenFile
option is deprecated, with users directed to authorization
instead: https://prometheus-operator.dev/docs/operator/api/#monitoring.coreos.com/v1.Endpoint. It does seem like a safer and improved pattern, WDYT about supporting authorization
instead of bearerTokenFile
in this PR?
Merged in #1025 - thanks again!
This implements a configurable
tlsConfig
for theserviceMonitor
used to grab metrics from the Vault API.Additionally it adds the possibility to set a
bearerTokenFile
for authentication purposes.