Name: capi-kubeadm-bootstrap-controller-manager-6558cd8d7f-dhzfz Namespace: capi-kubeadm-bootstrap-system Priority: 0 Service Account: capi-kubeadm-bootstrap-manager Node: instance/199.204.45.22 Start Time: Wed, 03 Jun 2026 00:51:11 +0000 Labels: cluster.x-k8s.io/provider=bootstrap-kubeadm control-plane=controller-manager pod-template-hash=6558cd8d7f Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.132 IPs: IP: 10.0.0.132 Controlled By: ReplicaSet/capi-kubeadm-bootstrap-controller-manager-6558cd8d7f Containers: manager: Container ID: containerd://c8b8472e01beefbf0db031ed90f5c000bb61d787f76c65cea5a7291e4559e1ea Image: harbor.atmosphere.dev/registry.k8s.io/cluster-api/kubeadm-bootstrap-controller:v1.10.5 Image ID: harbor.atmosphere.dev/registry.k8s.io/cluster-api/kubeadm-bootstrap-controller@sha256:e0f657538b3dc93a2eb0462561d0c895c78d9a515f048871bc90c927c0d4ce64 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,KubeadmBootstrapFormatIgnition=false,PriorityQueue=false --bootstrap-token-ttl=15m State: Running Started: Wed, 03 Jun 2026 01:06:47 +0000 Last State: Terminated Reason: Error Message: em/leases/kubeadm-bootstrap-manager-leader-election-capi?timeout=5s": net/http: request canceled (Client.Timeout exceeded while awaiting headers), falling back to slow path E0603 00:59:26.536379 1 leaderelection.go:429] Failed to update lock optimistically: the server was unable to return a response in the time allotted, but may still be processing the request (put leases.coordination.k8s.io kubeadm-bootstrap-manager-leader-election-capi), falling back to slow path E0603 01:00:08.539677 1 leaderelection.go:429] Failed to update lock optimistically: the server was unable to return a response in the time allotted, but may still be processing the request (put leases.coordination.k8s.io kubeadm-bootstrap-manager-leader-election-capi), falling back to slow path E0603 01:01:45.088808 1 leaderelection.go:429] Failed to update lock optimistically: Put "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capi-kubeadm-bootstrap-system/leases/kubeadm-bootstrap-manager-leader-election-capi?timeout=5s": net/http: request canceled (Client.Timeout exceeded while awaiting headers), falling back to slow path E0603 01:05:48.120357 1 leaderelection.go:429] Failed to update lock optimistically: Put "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capi-kubeadm-bootstrap-system/leases/kubeadm-bootstrap-manager-leader-election-capi?timeout=5s": net/http: request canceled (Client.Timeout exceeded while awaiting headers), falling back to slow path E0603 01:05:53.120072 1 leaderelection.go:472] Failed to update lock: Put "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capi-kubeadm-bootstrap-system/leases/kubeadm-bootstrap-manager-leader-election-capi?timeout=5s": context deadline exceeded I0603 01:05:53.120150 1 leaderelection.go:297] failed to renew lease capi-kubeadm-bootstrap-system/kubeadm-bootstrap-manager-leader-election-capi: context deadline exceeded E0603 01:05:53.120237 1 main.go:306] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Wed, 03 Jun 2026 00:51:17 +0000 Finished: Wed, 03 Jun 2026 01:05:53 +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-kubeadm-bootstrap-system (v1:metadata.namespace) POD_NAME: capi-kubeadm-bootstrap-controller-manager-6558cd8d7f-dhzfz (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-bt72n (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: cert: Type: Secret (a volume populated by a Secret) SecretName: capi-kubeadm-bootstrap-webhook-service-cert Optional: false kube-api-access-bt72n: 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 16m default-scheduler Successfully assigned capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager-6558cd8d7f-dhzfz to instance Normal Pulling 16m kubelet Pulling image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/kubeadm-bootstrap-controller:v1.10.5" Normal Pulled 16m kubelet Successfully pulled image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/kubeadm-bootstrap-controller:v1.10.5" in 188ms (4.588s including waiting) Warning Unhealthy 59s (x3 over 79s) kubelet Liveness probe failed: Get "http://10.0.0.132:9440/healthz": dial tcp 10.0.0.132:9440: connect: connection refused Normal Killing 59s kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 39s (x6 over 79s) kubelet Readiness probe failed: Get "http://10.0.0.132:9440/readyz": dial tcp 10.0.0.132:9440: connect: connection refused Normal Pulled 36s kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/kubeadm-bootstrap-controller:v1.10.5" already present on machine Normal Created 33s (x2 over 16m) kubelet Created container manager Normal Started 33s (x2 over 16m) kubelet Started container manager