Rolling update for KafkaConnect and KafkaMirrorMaker2

[opsocomusr]

When the clients ca certificate is renewed, the cluster operator triggers a rolling update for the kafka brokers and the entity operator. The user certificates are also renewed and updated in the respective secrets. But, the cluster operator does not trigger rolling update for the connect and mirrormaker deployments when the certificate is renewed and it continues to use the older truststore and keystore. Why is it not triggering rolling update for connect and mirrormaker?

[scholzj]

I think this is correct. There is probably no hook to roll the deploments when the certs change. Would you mind opening a Feature Request for it?

[opsocomusr]

I have created a feature request #5524 for this.

[scholzj]

Great, thanks.