Kate Stanley

Related to https://github.com/strimzi/strimzi-kafka-operator/issues/5458?

Looking into fixing this issue it seems to me that currently the Ready condition is set based on whether the reconciliation of the connector succeeded, not on whether the connector...

To implement the last suggestion of adding Warning conditions I could update this ConnectorStatusAndConditions inner class to parse the statusResult and pick out failing connector and topics and add conditions...

I guess the main difference is that currently as the user/ops team you have to write logic to parse the status, rather than relying on the known Kubernetes mechanism of...

From an initial investigation, if I set the following in the Kafka CR under CruiseControl.config: ``` sample.store.topic.replication.factor: 1 partition.sample.store.topic.partition.count: 5 broker.sample.store.topic.partition.count: 5 ``` then both the broker sample store and...

@ppatierno yes, but if I set `cruise.control.metrics.topic.replication.factor` in my CR the topic is still created with replication factor 3. Plus I noticed that there seems to be two configs relating...

@kyguy ah yeah if I add it to `spec.kafka.config` then it does change. So a question I have is, for the name of the metrics reporter topic, should we let...

Current behaviour is that `metric.reporter.topic` is the overriding setting, so if that is set that value will get used, if it is not set the default is used. I think...

@ppatierno I agree with your point about the UX experience. As a new user who didn't know how to configure cruise control in Strimzi I did the following: 1. Read...

I guess we never really got to an agreement on this issue about the way to set specify the configurations, but I wanted to at least circle back on the...