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
From reading the docs, the operator functions similar to strimzi's entityoperator. It expects to be installed as an operator for each kafka cluster.
In a cluster with multiple kafka clusters, we only need to install the CRDs once. Rather than rely on helm's behavior for CRDs, it would be great if the chart provides a crdsOnly option. Alternatively, the CRDs could be a separate chart.
If this idea resonates with you, I can open up a PR.
The text was updated successfully, but these errors were encountered:
Upon installing the operator, I noticed the RBAC use ClusterRole and ClusterRoleBinding. Shouldn't this be Role and RoleBinding instead? The operator expects a single namespace, kafka cluster, and operator namespace. It doesn't make much sense for it to be at the Cluster level.
From reading the docs, the operator functions similar to strimzi's entityoperator. It expects to be installed as an operator for each kafka cluster.
In a cluster with multiple kafka clusters, we only need to install the CRDs once. Rather than rely on helm's behavior for CRDs, it would be great if the chart provides a
crdsOnly
option. Alternatively, the CRDs could be a separate chart.If this idea resonates with you, I can open up a PR.
The text was updated successfully, but these errors were encountered: