-
Notifications
You must be signed in to change notification settings - Fork 109
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 the ability to specify which serviceAccount the agent pod uses #2876
Comments
Thanks for the suggestion and appreciate the willingness to contribute :) |
Yeah, I think it's ok. Thanks for willingness to contribute ^^ |
I don't think we'd need to do it - just saying that we need to make sure that this will be under the agent config and will not somehow affect via operator. |
Ah, ok. All good then |
Thanks guys, I created the PR. |
Thanks for merging 😄 |
In addition to this PR which added support for a
nodeSelector
, I think specifying a SA would also be beneficial, instead of having the agent pod start with the default SA.If this is something you'd approve of, I'm willing to give it a go and open a PR for it.
The text was updated successfully, but these errors were encountered: