- Notifications
You must be signed in to change notification settings - Fork927
docs: use consistent examples in prometheus doc and add namespaceSelector spec#16918
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
johnstcn left a comment• edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
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.
I'm fine with renaming;prom-http
was simply shorter to write but I missed the wider context. Good callout with thenamespaceSelector
!
I'm into it - less typing and I'm less likely to typo |
cf7d143
intomainUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
closes:#15385
use consistent
prom-http
port (@johnstcn looks like this was changed/added infix(helm)!: remove prometheus-http port declaration from coderd service spec #12214 - do we preferprom-http
overprometheus-http
or is it more important that they align?)add
namespaceSelector:
per@francisco-mata (thanks! - sorry it took so long to get this in)from issue: