Name: capi-controller-manager-bc4cf8c95-kcgtk Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.65 Start Time: Wed, 27 May 2026 10:40:44 +0000 Labels: cluster.x-k8s.io/provider=cluster-api control-plane=controller-manager pod-template-hash=bc4cf8c95 Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.40 IPs: IP: 10.0.0.40 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://aff356d39beff3b9cda3a53cb9b7a396486bfde4d22dfff6e6065574e1b26c5e Image: harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5 Image ID: harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller@sha256:d93407d031296336ccbabc8494005672dc048c4ebc616ccfc18f813d49bd87fc 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,ClusterResourceSet=true,ClusterTopology=true,RuntimeSDK=false,MachineSetPreflightChecks=true,MachineWaitForVolumeDetachConsiderVolumeAttachments=true,PriorityQueue=false State: Running Started: Wed, 27 May 2026 10:46:25 +0000 Last State: Terminated Reason: Error Message: erResourceSet" I0527 10:45:32.794624 1 controller.go:248] "Starting workers" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" worker count=10 E0527 10:45:37.675919 1 leaderelection.go:429] Failed to update lock optimistically: Put "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capi-system/leases/controller-leader-election-capi?timeout=5s": context deadline exceeded, falling back to slow path E0527 10:45:39.697591 1 event.go:359] "Server rejected event (will not retry!)" err="etcdserver: request timed out" event="&Event{ObjectMeta:{controller-leader-election-capi.18b36646f45ab5f3 capi-system 0 0001-01-01 00:00:00 +0000 UTC map[] map[] [] [] []},InvolvedObject:ObjectReference{Kind:Lease,Namespace:capi-system,Name:controller-leader-election-capi,UID:60e70542-c93c-456e-ae2b-752834bbbc05,APIVersion:coordination.k8s.io/v1,ResourceVersion:25125,FieldPath:,},Reason:LeaderElection,Message:capi-controller-manager-bc4cf8c95-kcgtk_66b00e4b-8abf-40de-a8a5-16c11aad28d4 became leader,Source:EventSource{Component:capi-controller-manager-bc4cf8c95-kcgtk_66b00e4b-8abf-40de-a8a5-16c11aad28d4,Host:,},FirstTimestamp:2026-05-27 10:45:32.674807283 +0000 UTC m=+25.027097546,LastTimestamp:2026-05-27 10:45:32.674807283 +0000 UTC m=+25.027097546,Count:1,Type:Normal,EventTime:0001-01-01 00:00:00 +0000 UTC,Series:nil,Action:,Related:nil,ReportingController:capi-controller-manager-bc4cf8c95-kcgtk_66b00e4b-8abf-40de-a8a5-16c11aad28d4,ReportingInstance:,}" E0527 10:45:42.675851 1 leaderelection.go:472] Failed to update lock: Put "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capi-system/leases/controller-leader-election-capi?timeout=5s": context deadline exceeded I0527 10:45:42.675895 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0527 10:45:42.675973 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Wed, 27 May 2026 10:45:07 +0000 Finished: Wed, 27 May 2026 10:45:54 +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: POD_NAMESPACE: capi-system (v1:metadata.namespace) POD_NAME: capi-controller-manager-bc4cf8c95-kcgtk (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-f8w8z (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-f8w8z: 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 35m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-kcgtk to instance Normal Pulled 30m (x2 over 35m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 30m (x2 over 35m) kubelet Created container manager Normal Started 30m (x2 over 35m) kubelet Started container manager Warning Unhealthy 30m kubelet Liveness probe failed: Get "http://10.0.0.40:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 30m kubelet Readiness probe failed: Get "http://10.0.0.40:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 29m (x5 over 31m) kubelet Liveness probe failed: Get "http://10.0.0.40:9440/healthz": dial tcp 10.0.0.40:9440: connect: connection refused Normal Killing 29m (x2 over 31m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 29m (x11 over 31m) kubelet Readiness probe failed: Get "http://10.0.0.40:9440/readyz": dial tcp 10.0.0.40:9440: connect: connection refused