Name: orc-controller-manager-6cb597b5d4-dmxlt Namespace: orc-system Priority: 0 Service Account: orc-controller-manager Node: instance/199.204.45.238 Start Time: Fri, 29 May 2026 22:43:45 +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.68 IPs: IP: 10.0.0.68 Controlled By: ReplicaSet/orc-controller-manager-6cb597b5d4 Containers: manager: Container ID: containerd://42edbc348ba4da1a1993155c5d2f113761644ab4bedbcacedde0373ee821bf65 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, 29 May 2026 22:52:21 +0000 Last State: Terminated Reason: Error Message: 2026-05-29T22:51: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: connect: connection refused"} main.main /workspace/cmd/manager/main.go:121 runtime.main /usr/local/go/src/runtime/proc.go:272 Exit Code: 1 Started: Fri, 29 May 2026 22:51:58 +0000 Finished: Fri, 29 May 2026 22:51:58 +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-xg5s2 (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: kube-api-access-xg5s2: 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 41m default-scheduler Successfully assigned orc-system/orc-controller-manager-6cb597b5d4-dmxlt to instance Normal Pulling 41m kubelet Pulling image "harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0" Normal Pulled 41m kubelet Successfully pulled image "harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0" in 1.566s (1.566s including waiting) Normal Created 37m (x2 over 41m) kubelet Created container manager Normal Started 37m (x2 over 41m) kubelet Started container manager Warning Unhealthy 34m (x3 over 35m) kubelet Liveness probe failed: Get "http://10.0.0.68:8081/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Killing 34m kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 33m (x14 over 35m) kubelet Readiness probe failed: Get "http://10.0.0.68:8081/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Pulled 33m (x2 over 37m) kubelet Container image "harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0" already present on machine