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

Multitenancy: allow non default service account when privileged is set to false. #210

Open
nikParasyr opened this issue Feb 19, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@nikParasyr
Copy link

Is your feature request related to a problem ?

Currenly when enabling multi-tenancy the --default-service-account flag is always set. This works well when fluxcd is deploying to one cluster, but doesnt work that well when fluxCD deploys to multiple clusters (in my case through cluster-api).
So, when the user defines spec.kubeconfig.secretRef.name to point to a workload cluster the SA account gets also set (to default or something else) which blocks all deployments. Setting it to a non default SA doesnt solve the issue.

Describe the solution you'd like.

In my understanding when multitenancy.priviledged is set to false the fluxCD components are not priviledged and can only impersonate. Therefore, not defining a service-account should not be an issue in terms of security and isolation.
So, i would like to be able to not set the default SA when multitenancy is enabled AND priviledged is set to false

Describe alternatives you've considered.

Not much tbh

Additional context.

No response

@nikParasyr nikParasyr added the enhancement New feature or request label Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant