[Bug]: Kafka Pods fails to restart to fetch latest configuration #9632
Unanswered
sachintandon-nexla
asked this question in
Q&A
Replies: 4 comments 1 reply
-
You should probably share the full log and the actual Strimzi configuration => the Kafka CR. The error suggests the broker is not responding. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Full logs:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Strimzi operator Deployment definition
|
Beta Was this translation helpful? Give feedback.
0 replies
-
@scholzj Please let me know if any more details are required. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Bug Description
Strimzi operator fails to restart kafka strimzipodsets automatically after the kafka configuration is updated . fails with below error.
Steps to reproduce
Expected behavior
No response
Strimzi version
0.39
Kubernetes version
1.28
Installation method
argoCD Helm Charts
Infrastructure
Amazon EKS
Configuration files and logs
No response
Additional context
Strimzi configuration :
Kafka Strimzi : 0.39
Kafka Version : 3.6.1
Error Logs from strimzi:
Beta Was this translation helpful? Give feedback.
All reactions