Name: capi-controller-manager-5647546676-hr4c5 Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.238 Start Time: Thu, 02 Jul 2026 01:12:10 +0000 Labels: cluster.x-k8s.io/provider=cluster-api control-plane=controller-manager pod-template-hash=5647546676 Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.123 IPs: IP: 10.0.0.123 Controlled By: ReplicaSet/capi-controller-manager-5647546676 Containers: manager: Container ID: containerd://89556f6ff3793afb639431e7eab2c59dd8d6dd1ed19d060b847e6055dba4a229 Image: harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.13.2 Image ID: harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller@sha256:e53df33f43352d5e7bf5a72fd4171c1447ef2123a4c551484e45395f3dbb1875 Ports: 9443/TCP, 9440/TCP, 8443/TCP Host Ports: 0/TCP, 0/TCP, 0/TCP Command: /manager Args: --leader-elect --diagnostics-address=:8443 --insecure-diagnostics=false --feature-gates=MachinePool=true,ClusterTopology=true,RuntimeSDK=false,MachineSetPreflightChecks=true,MachineWaitForVolumeDetachConsiderVolumeAttachments=true,PriorityQueue=true,ReconcilerRateLimiting=true,InPlaceUpdates=false,MachineTaintPropagation=false State: Running Started: Thu, 02 Jul 2026 01:16:34 +0000 Last State: Terminated Reason: Error Message: rkers to finish" controller="clusterclass" controllerGroup="cluster.x-k8s.io" controllerKind="ClusterClass" I0702 01:16:17.474978 1 internal.go:590] "Stopping and waiting for HTTP servers" I0702 01:16:17.475024 1 controller.go:326] "Shutdown signal received, waiting for all workers to finish" controller="clustercache" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" I0702 01:16:17.475011 1 controller.go:326] "Shutdown signal received, waiting for all workers to finish" controller="machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" I0702 01:16:17.475051 1 controller.go:326] "Shutdown signal received, waiting for all workers to finish" controller="topology/machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" I0702 01:16:17.475102 1 internal.go:594] "Wait completed, proceeding to shutdown the manager" I0702 01:16:17.475117 1 controller.go:326] "Shutdown signal received, waiting for all workers to finish" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" I0702 01:16:17.475132 1 controller.go:326] "Shutdown signal received, waiting for all workers to finish" controller="topology/machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" I0702 01:16:17.475144 1 controller.go:326] "Shutdown signal received, waiting for all workers to finish" controller="machinepool" controllerGroup="cluster.x-k8s.io" controllerKind="MachinePool" I0702 01:16:17.475159 1 controller.go:326] "Shutdown signal received, waiting for all workers to finish" controller="cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" I0702 01:16:17.475172 1 controller.go:326] "Shutdown signal received, waiting for all workers to finish" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" E0702 01:16:17.475184 1 main.go:402] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 02 Jul 2026 01:12:11 +0000 Finished: Thu, 02 Jul 2026 01:16:17 +0000 Ready: True Restart Count: 1 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: POD_NAMESPACE: capi-system (v1:metadata.namespace) POD_NAME: capi-controller-manager-5647546676-hr4c5 (v1:metadata.name) POD_UID: (v1:metadata.uid) Mounts: /tmp/k8s-webhook-server/serving-certs from cert (ro) /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-s6pb6 (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: cert: Type: Secret (a volume populated by a Secret) SecretName: capi-webhook-service-cert Optional: false kube-api-access-s6pb6: 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 38m default-scheduler Successfully assigned capi-system/capi-controller-manager-5647546676-hr4c5 to instance Warning Unhealthy 34m (x2 over 34m) kubelet Liveness probe failed: Get "http://10.0.0.123:9440/healthz": dial tcp 10.0.0.123:9440: connect: connection refused Warning Unhealthy 34m (x2 over 34m) kubelet Readiness probe failed: Get "http://10.0.0.123:9440/readyz": dial tcp 10.0.0.123:9440: connect: connection refused Normal Pulled 34m (x2 over 38m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.13.2" already present on machine Normal Created 34m (x2 over 38m) kubelet Created container manager Normal Started 34m (x2 over 38m) kubelet Started container manager