Name: orc-controller-manager-6cb597b5d4-fgrfz Namespace: orc-system Priority: 0 Service Account: orc-controller-manager Node: instance/199.204.45.25 Start Time: Thu, 23 Apr 2026 03:07:20 +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.3 IPs: IP: 10.0.0.3 Controlled By: ReplicaSet/orc-controller-manager-6cb597b5d4 Containers: manager: Container ID: containerd://6a555a7c4d9f58b8dd0df32d74c9a986c711712007b77174634db597cf1b3b63 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: Thu, 23 Apr 2026 03:15:53 +0000 Last State: Terminated Reason: Error Message: 2026-04-23T03:15:25Z 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: Thu, 23 Apr 2026 03:14:55 +0000 Finished: Thu, 23 Apr 2026 03:15:25 +0000 Ready: True Restart Count: 4 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-bgd76 (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: kube-api-access-bgd76: 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 37m default-scheduler Successfully assigned orc-system/orc-controller-manager-6cb597b5d4-fgrfz to instance Normal Pulling 37m kubelet Pulling image "harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0" Normal Pulled 37m kubelet Successfully pulled image "harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0" in 1.528s (1.528s including waiting) Warning Unhealthy 32m (x3 over 32m) kubelet Liveness probe failed: Get "http://10.0.0.3:8081/healthz": dial tcp 10.0.0.3:8081: connect: connection refused Normal Killing 32m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 31m kubelet Container image "harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0" already present on machine Normal Created 31m (x2 over 37m) kubelet Created container manager Normal Started 31m (x2 over 37m) kubelet Started container manager Warning Unhealthy 31m (x10 over 32m) kubelet Readiness probe failed: Get "http://10.0.0.3:8081/readyz": dial tcp 10.0.0.3:8081: connect: connection refused Warning Unhealthy 31m kubelet Liveness probe failed: Get "http://10.0.0.3:8081/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 31m (x4 over 31m) kubelet Readiness probe failed: Get "http://10.0.0.3:8081/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)