-
Notifications
You must be signed in to change notification settings - Fork 99
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
Usage with kube-rbac-proxy in front of kube-state-metrics #224
Comments
@daurnimator did you setup your own kubernetes cluster on droplets or are you referring to the managed Kubernetes product (DOKS)? |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs. |
This is with a DOKS cluster. |
Thanks for the info @daurnimator, I put something on our radar to investigate compatibility and will let you know what I find out. |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs. |
. |
wut? why was this closed by the stale bot; there was a comment 11 days ago. |
no idea why the bot still closed it :/ |
Hey @daurnimator, v3.9.0 introduces the |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs. |
We use kube-rbac-proxy in front of our kube-state-metrics instance as recommended by https://github.com/coreos/kube-prometheus.
How can we configure the do-agent to talk to it? As far as I can see, there is no argument to do-agent to get it to present a valid and RBAC authorized token or client TLS certificate.
Downstream issue: hashbang/gitops#31
The text was updated successfully, but these errors were encountered: