-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
[kube-prometheus-stack] allow to create secrets for basic auth usage #1193
Conversation
Thank you for your contribution @thirdeyenick. Though I understand the need for this, I have the slightest hesitation on this PR. IMHO, one shouldn't do a basic auth like this. Rather the system should be integrated with an IDP. Because when done something like a secret file with the creds, wouldn't this be insecure? I would defer this PR for the rest of the owners @bismarck @gianrubio @scottrigby @vsliouniaev @Xtigyro Thank you @thirdeyenick for your patience and for helping us in defining the best solution for the community. |
Hi,
It for sure depends on the implementation of the ingress controller, which kind of credentials are needed in the k8s secret. |
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 would suggest to go for a more general solution like "extraSecrets".
I like the idea and did some changes. Should now be more generic. |
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.
lgtm
Anything to do for me still? |
nope, just waiting for @monotek approval. Since he requested a change and Github is waiting for it. I don't want to dismiss his review. |
This allows to create a secret which can be used for basic authentication in ingresses Signed-off-by: nick <nick@nine.ch>
Signed-off-by: nick <nick@nine.ch>
This feature is very useful, thanks for the hard work! Any estimation when it will be merged ? |
All requested changes are implemented. Dismissing to get the merge button enabled.
…rometheus-community#1193) * allow to create a secret for basic auth This allows to create a secret which can be used for basic authentication in ingresses Signed-off-by: nick <nick@nine.ch> * allow for a more generic usage Signed-off-by: nick <nick@nine.ch> Signed-off-by: Thor Anker Kvisgård Lange <tal@netic.dk>
…rometheus-community#1193) * allow to create a secret for basic auth This allows to create a secret which can be used for basic authentication in ingresses Signed-off-by: nick <nick@nine.ch> * allow for a more generic usage Signed-off-by: nick <nick@nine.ch> Signed-off-by: QuentinBisson <quentin@giantswarm.io>
…rometheus-community#1193) * allow to create a secret for basic auth This allows to create a secret which can be used for basic authentication in ingresses Signed-off-by: nick <nick@nine.ch> * allow for a more generic usage Signed-off-by: nick <nick@nine.ch>
Can this be used without ingress? |
What this PR does / why we need it:
This PR allows to pass hashed credentials to the helm chart. Those credentials will be stored in a k8s secret. That k8s secret can then be referenced to support basic authentication in ingress resources. The nginx ingress controller has that feature for example.
Although Prometheus does support basic authentication itself, the prometheus-operator project doesn't seem to allow to configure this via the Prometheus CRD.
Which issue this PR fixes
Special notes for your reviewer:
Checklist
[prometheus-couchdb-exporter]
)