- Notifications
You must be signed in to change notification settings - Fork926
fix(helm)!: remove prometheus-http port declaration from coderd service spec#12214
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
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.
This is probably a breaking change. I don't think we should provide an alternative though, customers can create their own service (if they really need a service) or they can use annotations/labels on the pod which we already support
/s/probably/definitely |
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
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.
👍
Uh oh!
There was an error while loading.Please reload this page.
This PR removes the
prometheus-http
port entirely from the coder service specification (originally added in#10448). It also removes the Helm valuecoder.service.prometheusNodePort
.Rationale: some cloud providers will helpfully expose all ports on a
LoadBalancer
service for you. The net effect of this is that settingCODER_PROMETHEUS_ENABLE
will end up exposing port 2112 on your coderd service to the internet, which is likely undesired behaviour.cc@bpmct for visibility, this will need to be called out in release notes