Name: orc-controller-manager-6cb597b5d4-6bjwx Namespace: orc-system Priority: 0 Service Account: orc-controller-manager Node: instance/199.204.45.35 Start Time: Wed, 10 Jun 2026 10:24:24 +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.105 IPs: IP: 10.0.0.105 Controlled By: ReplicaSet/orc-controller-manager-6cb597b5d4 Containers: manager: Container ID: containerd://003bc59ade37b46e294c25a1a46ce0de778d8fd59a69a5d58efc7832b5c8fea4 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: Wed, 10 Jun 2026 10:32:01 +0000 Last State: Terminated Reason: Error Message: 2026-06-10T10:31:48Z 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: Wed, 10 Jun 2026 10:31:18 +0000 Finished: Wed, 10 Jun 2026 10:31:48 +0000 Ready: True Restart Count: 3 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-5d68p (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: kube-api-access-5d68p: 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 44m default-scheduler Successfully assigned orc-system/orc-controller-manager-6cb597b5d4-6bjwx to instance Normal Pulling 44m kubelet Pulling image "harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0" Normal Pulled 44m kubelet Successfully pulled image "harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0" in 2.087s (2.087s including waiting) Warning Unhealthy 39m (x3 over 39m) kubelet Liveness probe failed: Get "http://10.0.0.105:8081/healthz": dial tcp 10.0.0.105:8081: connect: connection refused Normal Created 38m (x2 over 44m) kubelet Created container manager Normal Started 38m (x2 over 44m) kubelet Started container manager Warning Unhealthy 38m (x10 over 39m) kubelet Readiness probe failed: Get "http://10.0.0.105:8081/readyz": dial tcp 10.0.0.105:8081: connect: connection refused Normal Killing 38m (x2 over 39m) kubelet Container manager failed liveness probe, will be restarted Normal Pulled 38m kubelet Container image "harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0" already present on machine Warning Unhealthy 38m (x4 over 38m) kubelet Readiness probe failed: Get "http://10.0.0.105:8081/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)