Replies: 1 comment · 5 replies
-
TBH, it is not really clear what you are asking about. You share some misformatted operator deployment? Or Pod? But you talk about Kafka broker. So it is not really clear what your issue is. Please share the resources always as YAML (i.e. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Sorry, It was a typo. I meant to title the discussion as operator, not broker. |
Beta Was this translation helpful? Give feedback.
All reactions
-
$ kubectl get po strimzi-cluster-operator-67b78fb598-hz9j6 -n kafka -o yaml
|
Beta Was this translation helpful? Give feedback.
All reactions
-
$ kubectl logs strimzi-cluster-operator-67b78fb598-hz9j6 -n kafka
|
Beta Was this translation helpful? Give feedback.
All reactions
-
$ kubectl get crd -A
|
Beta Was this translation helpful? Give feedback.
All reactions
-
Great, but can you please edit your posts and use proper formatting? Without it, nobody can read it. https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I've installed strimzi kafka operator using the provided helm charts on a rancher k8s cluster. The kafka operator pod does not come to ready state as the Liveness and Readiness probes failed reporting: "failed: Get "http://10.42.1.16:8080/ready": dial tcp 10.42.1.16:8080: connect: connection refused". There are no other pods running except for the k8s system pods. I can't find any apparent reason for the failure.
NAME READY STATUS RESTARTS AGE
strimzi-cluster-operator-67b78fb598-hz9j6 0/1 Running 805 (4m14s ago) 3d15h
The is the output of "kubectl desrcibe" for the operator pod:
Name: strimzi-cluster-operator-67b78fb598-hz9j6
Namespace: kafka
Priority: 0
Node: ip-10-53-4-45.ec2.internal/10.53.4.45
Start Time: Thu, 15 Dec 2022 22:45:25 +0000
Labels: name=strimzi-cluster-operator
pod-template-hash=67b78fb598
strimzi.io/kind=cluster-operator
Annotations: cni.projectcalico.org/containerID: 5fb17b33beecec7dde015cef29b7e435ef7ecd8f8179422321bf20238454168c
cni.projectcalico.org/podIP: 10.42.1.16/32
cni.projectcalico.org/podIPs: 10.42.1.16/32
kubernetes.io/psp: global-unrestricted-psp
Status: Running
IP: 10.42.1.16
IPs:
IP: 10.42.1.16
Controlled By: ReplicaSet/strimzi-cluster-operator-67b78fb598
Containers:
strimzi-cluster-operator:
Container ID: containerd://fe92cfca4fcde11372f50e5245f3e7fadace1973c484d29eb1c25bed591d874e
Image: quay.io/strimzi/operator:0.32.0
Image ID: quay.io/strimzi/operator@sha256:c5e0e5dca7503a8371b8d366db0f49e3fc68f62ea480262e39b6cc277991c97c
Port: 8080/TCP
Host Port: 0/TCP
Args:
/opt/strimzi/bin/cluster_operator_run.sh
State: Running
Started: Mon, 19 Dec 2022 13:57:56 +0000
Last State: Terminated
Reason: Error
Exit Code: 137
Started: Mon, 19 Dec 2022 13:51:26 +0000
Finished: Mon, 19 Dec 2022 13:57:56 +0000
Ready: False
Restart Count: 805
Limits:
cpu: 4
memory: 2Gi
Requests:
cpu: 1
memory: 2Gi
Liveness: http-get http://:http/healthy delay=300s timeout=1s period=30s #success=1 #failure=3
Readiness: http-get http://:http/ready delay=300s timeout=1s period=30s #success=1 #failure=3
Environment:
STRIMZI_NAMESPACE: kafka (v1:metadata.namespace)
STRIMZI_FULL_RECONCILIATION_INTERVAL_MS: 120000
STRIMZI_OPERATION_TIMEOUT_MS: 300000
STRIMZI_DEFAULT_TLS_SIDECAR_ENTITY_OPERATOR_IMAGE: quay.io/strimzi/kafka:0.32.0-kafka-3.3.1
STRIMZI_DEFAULT_KAFKA_EXPORTER_IMAGE: quay.io/strimzi/kafka:0.32.0-kafka-3.3.1
STRIMZI_DEFAULT_CRUISE_CONTROL_IMAGE: quay.io/strimzi/kafka:0.32.0-kafka-3.3.1
STRIMZI_KAFKA_IMAGES: 3.2.0=quay.io/strimzi/kafka:0.32.0-kafka-3.2.0
3.2.1=quay.io/strimzi/kafka:0.32.0-kafka-3.2.1
3.2.3=quay.io/strimzi/kafka:0.32.0-kafka-3.2.3
3.3.1=quay.io/strimzi/kafka:0.32.0-kafka-3.3.1
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
strimzi-tmp:
Type: EmptyDir (a temporary directory that shares a pod's lifetime)
Medium: Memory
SizeLimit: 1Mi
co-config-volume:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: strimzi-cluster-operator
Optional: false
kube-api-access-5nb4d:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional:
DownwardAPI: true
QoS Class: Burstable
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
Warning Unhealthy 12m (x2410 over 3d15h) kubelet Liveness probe failed: Get "http://10.42.1.16:8080/healthy": dial tcp 10.42.1.16:8080: connect: connection refused
Warning Unhealthy 6m7s (x5319 over 3d15h) kubelet Readiness probe failed: Get "http://10.42.1.16:8080/ready": dial tcp 10.42.1.16:8080: connect: connection refused
Beta Was this translation helpful? Give feedback.
All reactions