Toader Sebastian

This currently is not supported by `koperator`. Are you open to take a stab at it and submit a PR with the implementation?

None of the kafka tools can be run from within a broker pod as all these try to bind to a port which is already in use by Kafka. Run...

You can set IP on the LoadBalancer through: ``` apiVersion: kafka.banzaicloud.io/v1beta1 kind: KafkaCluster ... spec: envoyConfig: loadBalancerIP: 'your static ip' ``` Note: This feature depends on whether the underlying cloud-provider...

Since the KafkaCluster CRD size is quite large the `kubectl apply` may not work in all cases. Can you try `kubectl replace -f https://github.com/banzaicloud/koperator/releases/download/v0.20.0/kafka-operator.crds.yaml`

@Raboo this is a limitation of `kubectl apply` as it creates annotation called `kubectl.kubernetes.io/last-applied-configuration` on the CRD under the hood and this annotation makes the KafkaCluster CRD too large for...

On the long run the KafkaCluster CRD could be split into multiple smaller CRDs however in that case you would have to manipulate multiple CRs for managing a Kafka cluster

Hope this https://kubernetes.io/docs/reference/using-api/server-side-apply/ solve it. They plan this to replace `kubectl apply`

Have you tried re-running the command with `--force-conflicts`? I guess you got this error due to the fact you created the CRD previously with kubectl which by default uses client...

That's a good question. The CRD definition is generated with `controller-gen`, see https://github.com/banzaicloud/koperator/blob/master/Makefile#L109 and not maintained manually.

The `.status` is not part of the CRD anymore after upgrading to `controller-gen` to latest version: https://github.com/banzaicloud/koperator/commit/e5722ba328678d1eda4045d5820c8e32bc62e208