Replies: 1 comment 4 replies
-
Strimzi does not delete CRDs. It does not have any functionality for it - it even does not have the RBAC rights to do something like that. The logs indeed suggest that the CRDs were deleted - but it would have to be caused by something else. Maybe you can try to set finalizers on the CRDs or something like that to prevent it and see where the errors show up? |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Bug Description
We run 0.27.1 version strimzi on our Kafka cluster and we recently run into an issue with strimzi deleted the cluster unexpectedly. We hit this issue in 3 clusters already and I wonder what could be the trigger.
Before the deletion happens, we saw some test CRD created in this cluster, it's unclear what trigger these tests.
This is the log we saw:
Steps to reproduce
We don't have a way to reproduce it but it does happen 3 times.
Expected behavior
The Kafka CRD should not be deleted.
Strimzi version
0.27.1
Kubernetes version
1.22
Installation method
Helm chart
Infrastructure
Amazon EKS
Configuration files and logs
We can not paste full config here due to legal concern, but let us know what specific sections of config can help here. We are running Kafka version 2.8.1.
Additional context
My guess is something trigger the Strimzi to run its test suites, and during the test, it create/delete some kafka-mirrormaker-2 and kafkaconnect resources, after the test finished, it accidentally delete the Kafka resource as well, probably because the tests are failing.
It's unclear to me 1) what could trigger the test running 2) why the clusters are deleted after the tests output.
Beta Was this translation helpful? Give feedback.
All reactions