-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
1.8.0.GA
-
None
-
False
-
False
-
When deployed simple Kafka source/target cluster with MirrorMaker 2 - forcing annotation on target kafka cluster results in bringing down source target, rolling kmm2 pod (unable to contact source kafka?).
Seems like the whole connection is broken.
Interestingly, when forcing renewal of cluster certs on source cluster works fine.
In both cases correct (renewed) certs were present in kmm2 pod(s).
- relates to
-
ENTMQST-3249 [QE] KafkaConnect and KafkaMirrorMaker2 should roll when certificates or user credentials are updated
- Closed