Name: capo-controller-manager-65565fdb7f-rx4wd Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.240 Start Time: Tue, 12 May 2026 12:27:37 +0000 Labels: cluster.x-k8s.io/provider=infrastructure-openstack control-plane=capo-controller-manager pod-template-hash=65565fdb7f Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.235 IPs: IP: 10.0.0.235 Controlled By: ReplicaSet/capo-controller-manager-65565fdb7f Containers: manager: Container ID: containerd://481fc352cf7380f7077e777837c488e615dcedc765c9d593fd02a69713b48a57 Image: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7 Image ID: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller@sha256:b964c2f374ad4f26a593749d3c737492d5c1821db143b26596c9285b9055a8b4 Ports: 9443/TCP, 9440/TCP Host Ports: 0/TCP, 0/TCP Command: /manager Args: --leader-elect --v=2 --diagnostics-address=127.0.0.1:8080 --insecure-diagnostics=true State: Running Started: Tue, 12 May 2026 12:36:11 +0000 Last State: Terminated Reason: Error Message: 33:59.729137 1 leaderelection.go:436] error retrieving resource lock capo-system/controller-leader-election-capo: Get "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capo-system/leases/controller-leader-election-capo?timeout=5s": dial tcp 10.96.0.1:443: connect: connection refused E0512 12:34:01.728602 1 leaderelection.go:429] Failed to update lock optimitically: Put "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capo-system/leases/controller-leader-election-capo?timeout=5s": dial tcp 10.96.0.1:443: connect: connection refused, falling back to slow path E0512 12:34:01.729272 1 leaderelection.go:436] error retrieving resource lock capo-system/controller-leader-election-capo: Get "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capo-system/leases/controller-leader-election-capo?timeout=5s": dial tcp 10.96.0.1:443: connect: connection refused E0512 12:34:03.728557 1 leaderelection.go:429] Failed to update lock optimitically: Put "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capo-system/leases/controller-leader-election-capo?timeout=5s": dial tcp 10.96.0.1:443: connect: connection refused, falling back to slow path E0512 12:34:03.729263 1 leaderelection.go:436] error retrieving resource lock capo-system/controller-leader-election-capo: Get "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capo-system/leases/controller-leader-election-capo?timeout=5s": dial tcp 10.96.0.1:443: connect: connection refused I0512 12:34:05.725953 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0512 12:34:05.727617 1 leaderelection.go:322] Failed to release lock: Put "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capo-system/leases/controller-leader-election-capo?timeout=5s": dial tcp 10.96.0.1:443: connect: connection refused E0512 12:34:05.727813 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Tue, 12 May 2026 12:32:08 +0000 Finished: Tue, 12 May 2026 12:36:02 +0000 Ready: True Restart Count: 2 Liveness: http-get http://:healthz/healthz delay=0s timeout=1s period=10s #success=1 #failure=3 Readiness: http-get http://:healthz/readyz delay=0s timeout=1s period=10s #success=1 #failure=3 Environment: CLUSTER_API_OPENSTACK_INSTANCE_CREATE_TIMEOUT: 10 Mounts: /tmp/k8s-webhook-server/serving-certs from cert (ro) /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-7v9ph (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: cert: Type: Secret (a volume populated by a Secret) SecretName: capo-webhook-service-cert Optional: false kube-api-access-7v9ph: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 3607 ConfigMapName: kube-root-ca.crt ConfigMapOptional: DownwardAPI: true QoS Class: BestEffort Node-Selectors: openstack-control-plane=enabled Tolerations: node-role.kubernetes.io/control-plane:NoSchedule node-role.kubernetes.io/master:NoSchedule 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 capo-system/capo-controller-manager-65565fdb7f-rx4wd to instance Warning Unhealthy 36m (x3 over 36m) kubelet Liveness probe failed: Get "http://10.0.0.235:9440/healthz": dial tcp 10.0.0.235:9440: connect: connection refused Normal Pulled 35m (x2 over 40m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7" already present on machine Warning Unhealthy 35m (x7 over 36m) kubelet Readiness probe failed: Get "http://10.0.0.235:9440/readyz": dial tcp 10.0.0.235:9440: connect: connection refused Normal Created 35m (x2 over 40m) kubelet Created container manager Normal Started 35m (x2 over 40m) kubelet Started container manager Normal Killing 33m (x2 over 36m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 33m (x3 over 33m) kubelet Liveness probe failed: Get "http://10.0.0.235:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 33m (x5 over 33m) kubelet Readiness probe failed: Get "http://10.0.0.235:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)