You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are installing Flux Operator using OLM (from operatorhub), and all our clusters are multi-tenant. To provide our users with a good UX, we have configured the Flux default service account to a service account that is pre-created in all our end-user Flux namespaces, with the RBAC permissions normally given to end-users. This works great!
While experimenting with the new ResourceSet, I noticed that the default service account when reconciling is flux-operator, and I can not find a way to override this default in Flux Operator. Is this possible to configure as you obviously can when installing using Helm, ref. the multitenancy.defaultServiceAccount value. Would it be possible to make this configurable to us as cluster admins?
The text was updated successfully, but these errors were encountered:
The issue is that the RedHat Subscription does not allow setting container args, as an OpenShift admin you can only set environment variables. We could expose the SA default as an env var that when set would override the cmd flag. With this your subscription could be:
We are installing Flux Operator using OLM (from operatorhub), and all our clusters are multi-tenant. To provide our users with a good UX, we have configured the Flux default service account to a service account that is pre-created in all our end-user Flux namespaces, with the RBAC permissions normally given to end-users. This works great!
While experimenting with the new
ResourceSet
, I noticed that the default service account when reconciling isflux-operator
, and I can not find a way to override this default in Flux Operator. Is this possible to configure as you obviously can when installing using Helm, ref. themultitenancy.defaultServiceAccount
value. Would it be possible to make this configurable to us as cluster admins?The text was updated successfully, but these errors were encountered: