Skip to content
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

The Operator should create a new k8s ServiceAccount for each deployed Feast service #4766

Closed
tchughesiv opened this issue Nov 18, 2024 · 0 comments · Fixed by #4767
Closed
Labels
kind/feature New feature or request

Comments

@tchughesiv
Copy link
Contributor

tchughesiv commented Nov 18, 2024

Is your feature request related to a problem? Please describe.
The Operator should create a new service account for each deployed Feast service. This will ensure we're not using the default SA which can sometimes have been modified by the user or have elevated perms, etc.

Describe the solution you'd like
For each Feast service the operator deploys, a new service account should be created and used.

@tchughesiv tchughesiv added the kind/feature New feature or request label Nov 18, 2024
@tchughesiv tchughesiv changed the title The Operator should create a new service account for each FeatureStore CR The Operator should create a new k8s ServiceAccount for each FeatureStore CR Nov 18, 2024
@tchughesiv tchughesiv changed the title The Operator should create a new k8s ServiceAccount for each FeatureStore CR The Operator should create a new k8s ServiceAccount for each deployed Feast service Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant