Name: orc-controller-manager-6cb597b5d4-mvlq4 Namespace: orc-system Priority: 0 Service Account: orc-controller-manager Node: instance/199.204.45.41 Start Time: Fri, 06 Mar 2026 01:19:09 +0000 Labels: control-plane=controller-manager pod-template-hash=6cb597b5d4 Annotations: kubectl.kubernetes.io/default-container: manager Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.61 IPs: IP: 10.0.0.61 Controlled By: ReplicaSet/orc-controller-manager-6cb597b5d4 Containers: manager: Container ID: containerd://41423a51f65f6ca7838a8ddc80178140f09897dbc6427987c9f0582df5051f8d Image: harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0 Image ID: harbor.atmosphere.dev/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: Fri, 06 Mar 2026 01:29:48 +0000 Last State: Terminated Reason: Error Message: 2026-03-06T01:28:20Z 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: Fri, 06 Mar 2026 01:27:50 +0000 Finished: Fri, 06 Mar 2026 01:28:20 +0000 Ready: True Restart Count: 5 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-x4g9j (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: kube-api-access-x4g9j: 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 40m default-scheduler Successfully assigned orc-system/orc-controller-manager-6cb597b5d4-mvlq4 to instance Normal Pulling 40m kubelet Pulling image "harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0" Normal Pulled 40m kubelet Successfully pulled image "harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0" in 1.631s (1.631s including waiting) Warning Unhealthy 34m (x2 over 35m) kubelet Readiness probe failed: Get "http://10.0.0.61:8081/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 34m (x3 over 36m) kubelet Liveness probe failed: Get "http://10.0.0.61:8081/healthz": dial tcp 10.0.0.61:8081: connect: connection refused Normal Killing 34m kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 34m (x10 over 36m) kubelet Readiness probe failed: Get "http://10.0.0.61:8081/readyz": dial tcp 10.0.0.61:8081: connect: connection refused Normal Created 34m (x3 over 40m) kubelet Created container manager Normal Started 34m (x3 over 40m) kubelet Started container manager Normal Pulled 34m (x2 over 35m) kubelet Container image "harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0" already present on machine Warning BackOff 30m (x13 over 33m) kubelet Back-off restarting failed container manager in pod orc-controller-manager-6cb597b5d4-mvlq4_orc-system(5c48db25-88cb-4e8b-acd5-c6384fb8ad36)