We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I've configured VMAgent that uses bearer token secret but the secret isn't being processed at all.
VMAgent
Resource definition:
apiVersion: operator.victoriametrics.com/v1beta1 kind: VMAgent metadata: name: agent spec: remoteWrite: - url: https://metric-api.newrelic.com/prometheus/v1/write?prometheus_server=datasource bearerTokenSecret: key: token name: new-relic-token
Resulting in these pods being deployed without any configured remote write secret:
Port: 8429/TCP Host Port: 0/TCP Args: -httpListenAddr=:8429 -promscrape.config=/etc/vmagent/config_out/vmagent.env.yaml -remoteWrite.maxDiskUsagePerURL=1073741824 -remoteWrite.tmpDataPath=/tmp/vmagent-remotewrite-data -remoteWrite.url=https://metric-api.newrelic.com/prometheus/v1/write?prometheus_server=datasource State: Running
The text was updated successfully, but these errors were encountered:
If you don't mind, I've created a pull request to fix the issue: #421. Looking forward to hearing from you. Thanks!
Sorry, something went wrong.
Thanks, merged, soon it will be released with new patch release. It's a regression after code refactoring, badly written test didn't cover it (
Thank you very much for merging the PR! Very nice. I'm looking forward to the release.
No branches or pull requests
I've configured
VMAgent
that uses bearer token secret but the secret isn't being processed at all.Resource definition:
Resulting in these pods being deployed without any configured remote write secret:
The text was updated successfully, but these errors were encountered: