Name: rabbitmq-messaging-topology-operator-69996b7f7f-pwddf Namespace: openstack Priority: 0 Service Account: rabbitmq-messaging-topology-operator Node: instance/199.204.45.216 Start Time: Sat, 09 May 2026 05:19:49 +0000 Labels: app.kubernetes.io/component=messaging-topology-operator app.kubernetes.io/instance=rabbitmq-cluster-operator app.kubernetes.io/managed-by=Helm app.kubernetes.io/name=rabbitmq-cluster-operator app.kubernetes.io/part-of=rabbitmq helm.sh/chart=rabbitmq-cluster-operator-2.6.6 pod-template-hash=69996b7f7f Annotations: Status: Running IP: 10.0.0.24 IPs: IP: 10.0.0.24 Controlled By: ReplicaSet/rabbitmq-messaging-topology-operator-69996b7f7f Containers: rabbitmq-cluster-operator: Container ID: containerd://4c35523a088fedd4e5763915b81c2111d2d2c0e1aa1ea728c2945a7f2c3af4f3 Image: harbor.atmosphere.dev/docker.io/rabbitmqoperator/messaging-topology-operator:1.6.0 Image ID: harbor.atmosphere.dev/docker.io/rabbitmqoperator/messaging-topology-operator@sha256:5052e8bdb26996c62315f0707c6fb291fd84492e360cca7351e2c3fdf659be43 Ports: 9443/TCP, 8080/TCP Host Ports: 0/TCP, 0/TCP Command: /manager Args: --metrics-bind-address=:8080 State: Running Started: Sat, 09 May 2026 06:10:20 +0000 Last State: Terminated Reason: Error Exit Code: 1 Started: Sat, 09 May 2026 06:08:22 +0000 Finished: Sat, 09 May 2026 06:10:05 +0000 Ready: True Restart Count: 2 Liveness: http-get http://:http-metrics/metrics delay=5s timeout=5s period=30s #success=1 #failure=5 Readiness: http-get http://:http-metrics/metrics delay=5s timeout=5s period=30s #success=1 #failure=5 Environment: OPERATOR_NAMESPACE: openstack (v1:metadata.namespace) Mounts: /tmp/k8s-webhook-server/serving-certs from cert (ro) /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-zlvjm (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: cert: Type: Secret (a volume populated by a Secret) SecretName: rabbitmq-messaging-topology-operator-webhook Optional: false kube-api-access-zlvjm: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 3607 ConfigMapName: kube-root-ca.crt ConfigMapOptional: DownwardAPI: true QoS Class: BestEffort Node-Selectors: openstack-control-plane=enabled 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 32m (x2 over 32m) kubelet Liveness probe failed: Get "http://10.0.0.24:8080/metrics": dial tcp 10.0.0.24:8080: connect: connection refused Warning Unhealthy 32m (x2 over 32m) kubelet Readiness probe failed: Get "http://10.0.0.24:8080/metrics": dial tcp 10.0.0.24:8080: connect: connection refused Warning Unhealthy 30m kubelet Liveness probe failed: Get "http://10.0.0.24:8080/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 30m kubelet Readiness probe failed: Get "http://10.0.0.24:8080/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning BackOff 29m kubelet Back-off restarting failed container rabbitmq-cluster-operator in pod rabbitmq-messaging-topology-operator-69996b7f7f-pwddf_openstack(583b7ca8-ae8d-4795-ae32-b9f4a946759f) Normal Pulled 29m (x2 over 31m) kubelet Container image "harbor.atmosphere.dev/docker.io/rabbitmqoperator/messaging-topology-operator:1.6.0" already present on machine Normal Created 29m (x3 over 80m) kubelet Created container rabbitmq-cluster-operator Normal Started 29m (x3 over 80m) kubelet Started container rabbitmq-cluster-operator