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
I'm evaluating Deployment > Kubernetes > Overview > Helm and RedPanda Operator and I'm concerned about how this is supposed to work. Bundling FluxCD with Redpanda Operator seems like a big and unnecessary coupling of RedPanda to a specific GitOps framework.
It causes either duplication of resources in a cluster where FluxCD is already installed, or to cause version conflicts between the bundled and the already-installed FluxCD, and to make upgrades of either FluxCD or RedPanda Operator more complicated, and can only create trouble for users of other GitOps frameworks.
The operator should just be some CRDs and controllers for reacting to them, and have trust that deployment lifecycle of the operator itself is managed on some other layer, be it manual application of Helm charts, a GitOps framework, or Operator Lifecycle Manager, Operator-Controller, or whatever else the cluster admin uses to manage their operators.
Please consider providing a more bare-bones deployment of the operator, with no bundled GitOps tooling.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm evaluating Deployment > Kubernetes > Overview > Helm and RedPanda Operator and I'm concerned about how this is supposed to work. Bundling FluxCD with Redpanda Operator seems like a big and unnecessary coupling of RedPanda to a specific GitOps framework.
It causes either duplication of resources in a cluster where FluxCD is already installed, or to cause version conflicts between the bundled and the already-installed FluxCD, and to make upgrades of either FluxCD or RedPanda Operator more complicated, and can only create trouble for users of other GitOps frameworks.
The operator should just be some CRDs and controllers for reacting to them, and have trust that deployment lifecycle of the operator itself is managed on some other layer, be it manual application of Helm charts, a GitOps framework, or Operator Lifecycle Manager, Operator-Controller, or whatever else the cluster admin uses to manage their operators.
Please consider providing a more bare-bones deployment of the operator, with no bundled GitOps tooling.
Beta Was this translation helpful? Give feedback.
All reactions