-
Notifications
You must be signed in to change notification settings - Fork 63
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
Try reading the ca.crt and TokenReviewer JWT from the default service account #83
Try reading the ca.crt and TokenReviewer JWT from the default service account #83
Conversation
… account secret location to support running inside k8s
cf350ad
to
797fe07
Compare
that would be amazing!!! |
@kalafut any chance this change can be considered to merge-in? |
@riuvshyn Yes, we'll be adding it soon. |
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
I opened an issue that references this PR as the cause. I am unable to authenticate to external clusters (when vault is itself running in a cluster) due to the fact that in this change you default the tokenReviewerJWT to the POD token (if found) and one wasn't supplied in the auth configuration. |
This should help address #82