Name: orc-controller-manager-b56d5d966-ftlqg Namespace: orc-system Priority: 0 Service Account: orc-controller-manager Node: instance/199.19.213.219 Start Time: Tue, 05 May 2026 23:07:07 +0000 Labels: control-plane=controller-manager pod-template-hash=b56d5d966 Annotations: kubectl.kubernetes.io/default-container: manager Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.149 IPs: IP: 10.0.0.149 Controlled By: ReplicaSet/orc-controller-manager-b56d5d966 Containers: manager: Container ID: containerd://b12abad16698eedac586c3b888504696ad1822dc805326a3aa59d510ea0646a5 Image: quay.io/orc/openstack-resource-controller:v2.2.0 Image ID: quay.io/orc/openstack-resource-controller@sha256:e3c51b1c3048c3f8c2856a6327810981fd4624602091021c4d310092c85e247c Port: Host Port: Command: /manager Args: --metrics-bind-address=:8443 --leader-elect --health-probe-bind-address=:8081 State: Running Started: Tue, 05 May 2026 23:18:26 +0000 Last State: Terminated Reason: Error Message: 2026-05-05T23:16:58Z ERROR setup Error starting manager {"error": "unable to create image controller: failed to get server groups: Get \"https://10.96.0.1:443/api\": dial tcp 10.96.0.1:443: i/o timeout"} main.main /workspace/cmd/manager/main.go:121 runtime.main /usr/local/go/src/runtime/proc.go:272 Exit Code: 1 Started: Tue, 05 May 2026 23:16:28 +0000 Finished: Tue, 05 May 2026 23:16:58 +0000 Ready: True Restart Count: 6 Limits: cpu: 500m memory: 256Mi Requests: cpu: 10m memory: 64Mi Liveness: http-get http://:8081/healthz delay=15s timeout=1s period=20s #success=1 #failure=3 Readiness: http-get http://:8081/readyz delay=5s timeout=1s period=10s #success=1 #failure=3 Environment: Mounts: /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-2ss5f (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: kube-api-access-2ss5f: 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: 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 ---- ------ ---- ---- ------- Normal Scheduled 39m default-scheduler Successfully assigned orc-system/orc-controller-manager-b56d5d966-ftlqg to instance Normal Pulling 39m kubelet Pulling image "quay.io/orc/openstack-resource-controller:v2.2.0" Normal Pulled 39m kubelet Successfully pulled image "quay.io/orc/openstack-resource-controller:v2.2.0" in 2.27s (2.27s including waiting) Normal Killing 34m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 33m kubelet Container image "quay.io/orc/openstack-resource-controller:v2.2.0" already present on machine Normal Created 33m (x2 over 39m) kubelet Created container manager Normal Started 33m (x2 over 39m) kubelet Started container manager Warning Unhealthy 33m (x3 over 33m) kubelet Readiness probe failed: Get "http://10.0.0.149:8081/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 33m (x11 over 35m) kubelet Readiness probe failed: Get "http://10.0.0.149:8081/readyz": dial tcp 10.0.0.149:8081: connect: connection refused Warning Unhealthy 33m (x4 over 34m) kubelet Liveness probe failed: Get "http://10.0.0.149:8081/healthz": dial tcp 10.0.0.149:8081: connect: connection refused Warning BackOff 28m (x7 over 31m) kubelet Back-off restarting failed container manager in pod orc-controller-manager-b56d5d966-ftlqg_orc-system(6682d2ae-16f7-407f-8036-d8b65ac04c8f)