-
Notifications
You must be signed in to change notification settings - Fork 449
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
Add docs for bound service account token trigger authentication #1507
base: main
Are you sure you want to change the base?
Add docs for bound service account token trigger authentication #1507
Conversation
Thank you for your contribution! 🙏 We will review your PR as soon as possible.
Learn more about:
|
✅ Deploy Preview for keda ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
As default, KEDA doesn't have permission in the RBAC to create these tokens (and not granting it as default is worth IMHO), so maybe we could add an example of the required extra roles that needs to be added to KEDA operator service account (or event better, and example of all the required RBAC manifests)
content/docs/2.17/authentication-providers/bound-service-account-token.md
Outdated
Show resolved
Hide resolved
Signed-off-by: Max Cao <[email protected]>
…da-operator to request tokens Signed-off-by: Max Cao <[email protected]>
e19e46b
to
e0133f0
Compare
|
||
## Permissions for KEDA to request service account tokens | ||
|
||
By default, the KEDA operator does not have the necessary permissions to request service account tokens from an arbitrary service account. This is to prevent a privilege escalation where a bad actor could use KEDA to request tokens on behalf of any service account in the cluster. |
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.
We should document here the way how to enable this via Helm Chart, once we have the final implemenetation there
Provide a description of what has been changed
Adds docs for
BoundServiceAccountToken
trigger auth provider/source.Checklist
Depends on: kedacore/keda#6272