Name: orc-controller-manager-6cb597b5d4-sjjbl Namespace: orc-system Priority: 0 Service Account: orc-controller-manager Node: instance/199.19.213.215 Start Time: Mon, 15 Jun 2026 20:00:55 +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.238 IPs: IP: 10.0.0.238 Controlled By: ReplicaSet/orc-controller-manager-6cb597b5d4 Containers: manager: Container ID: containerd://9d742f908c5907241a8f4d261e6d410287c7538264f00d7e61af432c0f317e0d 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: Mon, 15 Jun 2026 20:10:47 +0000 Last State: Terminated Reason: Error Message: 2026-06-15T20:10: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: Mon, 15 Jun 2026 20:09:50 +0000 Finished: Mon, 15 Jun 2026 20:10:20 +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-brz9c (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: kube-api-access-brz9c: 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 48m default-scheduler Successfully assigned orc-system/orc-controller-manager-6cb597b5d4-sjjbl to instance Normal Pulling 48m kubelet Pulling image "harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0" Normal Pulled 48m kubelet Successfully pulled image "harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0" in 2.341s (2.341s including waiting) Normal Started 48m kubelet Started container manager Warning Unhealthy 43m (x3 over 43m) kubelet Liveness probe failed: Get "http://10.0.0.238:8081/healthz": dial tcp 10.0.0.238:8081: connect: connection refused Normal Killing 42m (x3 over 43m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 42m (x14 over 44m) kubelet Readiness probe failed: Get "http://10.0.0.238:8081/readyz": dial tcp 10.0.0.238:8081: connect: connection refused Normal Pulled 42m kubelet Container image "harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0" already present on machine Normal Created 42m (x2 over 48m) kubelet Created container manager Warning Unhealthy 38m (x17 over 42m) kubelet Readiness probe failed: Get "http://10.0.0.238:8081/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)