Replies: 2 comments 2 replies
-
That exception on its own just means that something is taking more time than it should. It does not really reveal any root cause which can be basically anything from unresponsive operands, insufficient resources for the operator or the operand, or in this case it could be also that the Kubernetes API server is not responding for some reason (or some admission controller in your Kubernetes cluster blocking the operation) etc. Having a DEBUG log might reveal more details about where exactly the issue is. |
Beta Was this translation helpful? Give feedback.
-
After changing the logLevel to TRACE (
I accessed the operator POD and ran a curl command to access the same endpoint, resulting in the following output:
Do you have any idea what might be causing this issue? |
Beta Was this translation helpful? Give feedback.
-
Bug Description
I'm installing strimzi using helm on my k8s. At the beggining everything was working fine, after while it just stopped working. It gets a timeout error.
The error starts after creating a KafkaConnect.
Steps to reproduce
0.39.0
- Just one line of configuration:replica: 1
Expected behavior
No response
Strimzi version
0.39.0
Kubernetes version
1.29
Installation method
Helm Chart
Infrastructure
Amazon EKS - Operator POD
Configuration files and logs
KafkaConnect YAML:
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions