Is your feature request related to a problem? Please describe.
It would be convenient if it were possible to completely disable the operator on the helm chart. In my architecture, I deploy helm charts that create operators and CRDs in one phase, and then deploy custom resources in additional phases. This would mean using the fluent-operator chart more than once, which causes resource conflicts (for example, with the service account).
Describe the solution you'd like
Every resource template should be wrapped in a conditional allowing it to be enabled. In particular, the service account is causing problems when I attempt to deploy the helm chart a second time. If setting operator.enable: false, this resource would not be created.
Additional context
I've seen some other projects go as far as to create separate helm charts for the custom resources created by the operator or base helm chart. I'm also fine doing this in a single helm chart as long as I can disable anything I don't want.
Is your feature request related to a problem? Please describe.
It would be convenient if it were possible to completely disable the operator on the helm chart. In my architecture, I deploy helm charts that create operators and CRDs in one phase, and then deploy custom resources in additional phases. This would mean using the fluent-operator chart more than once, which causes resource conflicts (for example, with the service account).
Describe the solution you'd like
Every resource template should be wrapped in a conditional allowing it to be enabled. In particular, the service account is causing problems when I attempt to deploy the helm chart a second time. If setting
operator.enable: false, this resource would not be created.Additional context
I've seen some other projects go as far as to create separate helm charts for the custom resources created by the operator or base helm chart. I'm also fine doing this in a single helm chart as long as I can disable anything I don't want.
I'm happy to make this change in a PR.