-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
fix: convert consul scheme to lowercase while setting prometheus config #6098
Conversation
Signed-off-by: Jayapriya Pai <slashpai9@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a couple more places where we can do the same I believe.
The one on ScrapeConfigSpec is already taken care prometheus-operator/pkg/prometheus/promcfg.go Lines 2284 to 2286 in b6610bb
I don't see scheme used in other ScrapeConfigs |
prometheus-operator/pkg/prometheus/promcfg.go Lines 716 to 718 in b6610bb
prometheus-operator/pkg/prometheus/promcfg.go Lines 927 to 929 in b6610bb
prometheus-operator/pkg/prometheus/promcfg.go Lines 1180 to 1182 in b6610bb
prometheus-operator/pkg/prometheus/promcfg.go Lines 1582 to 1585 in b6610bb
|
I was looking in ScrapeConfig CRD :) For others some doesn't have validation api level and some are using http/https. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My bad!
Description
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Noticed while playing around ConsulSD config
Scheme
should be converted to lowercase to fix errorunsupported protocol scheme \"HTTPS\""
from PrometheusType of change
What type of changes does your code introduce to the Prometheus operator? Put an
x
in the box that apply.CHANGE
(fix or feature that would cause existing functionality to not work as expected)FEATURE
(non-breaking change which adds functionality)BUGFIX
(non-breaking change which fixes an issue)ENHANCEMENT
(non-breaking change which improves existing functionality)NONE
(if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)Changelog entry
Please put a one-line changelog entry below. This will be copied to the changelog file during the release process.