feat: Operator will create k8s serviceaccount for each feast service #4767
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Tommy Hughes <[email protected]>
dmartinol
approved these changes
Nov 19, 2024
shuchu
pushed a commit
to shuchu/feast
that referenced
this pull request
Nov 21, 2024
…east-dev#4767) create a serviceaccount for each feast service Signed-off-by: Tommy Hughes <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
For each feast service the operator deploys, a new service account will be created and used. This will ensure we're not using the default SA which can sometimes have been modified by the user or have elevated perms, etc.
Which issue(s) this PR fixes:
Fixes #4766