Skip to content
New issue

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

[prometheus-blackbox-exporter] Adjust configPath handling #4915

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Jakob3xD
Copy link

What this PR does / why we need it

Issue
I want to deploy the config map for the Blackbox config on my own, as I want to write some logic that adjust the ConfigMap more dynamically. Therefore I need to null the config value as otherwise the ConfigMap is created with the default chart values. When setting config to null the config path is set to /etc/blackbox_exporter/config.yml which does not exist.

Changes
I changed the config path logic to match the one of the config reloader. If no configPath is set, we use the default of /config/blackbox.yaml otherwise we use the configPath value. The default value of /etc/blackbox_exporter/config.yml gets removed as I don´t see the point in keeping it. If needed it can be set via configPath.

As it its a breaking change, I also bumped the version.

Which issue this PR fixes

None

Special notes for your reviewer

Checklist

  • DCO signed
  • Chart Version bumped
  • Title of the PR starts with chart name (e.g. [prometheus-couchdb-exporter])

{{- else }}
- "--config.file=/etc/blackbox_exporter/config.yml"
{{- end }}
- --config.file={{ .Values.configPath | default "/config/blackbox.yaml" }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As this is a major updat anyway we might think about to rename the var to .Values.configFile too.
Imho this fits better as the var currently contains a filename and not only the path.
Thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants