Name: capi-controller-manager-5647546676-hmlmm Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.240 Start Time: Fri, 24 Jul 2026 18:12:42 +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.208 IPs: IP: 10.0.0.208 Controlled By: ReplicaSet/capi-controller-manager-5647546676 Containers: manager: Container ID: containerd://9b6965b994114acd9a4dfe234896bdf755459b6d9f07a78f638a3f873ffbae8e 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: Fri, 24 Jul 2026 18:18:18 +0000 Last State: Terminated Reason: Error Message: ntrollerKind="Machine" worker count=100 I0724 18:17:40.992896 1 controller.go:306] "Starting workers" controller="machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" worker count=50 I0724 18:17:40.992858 1 controller.go:306] "Starting workers" controller="machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" worker count=50 I0724 18:17:41.082460 1 controller.go:303] "Starting Controller" controller="crdmigrator" controllerGroup="apiextensions.k8s.io" controllerKind="CustomResourceDefinition" I0724 18:17:41.082505 1 controller.go:306] "Starting workers" controller="crdmigrator" controllerGroup="apiextensions.k8s.io" controllerKind="CustomResourceDefinition" worker count=1 I0724 18:17:41.093787 1 controller.go:303] "Starting Controller" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" I0724 18:17:41.093817 1 controller.go:306] "Starting workers" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" worker count=10 E0724 18:17:45.883470 1 leaderelection.go:445] "Failed to update lease optimistically, falling back to slow path" err="the server was unable to return a response in the time allotted, but may still be processing the request (put leases.coordination.k8s.io controller-leader-election-capi)" lock="capi-system/controller-leader-election-capi" E0724 18:17:50.877876 1 leaderelection.go:488] "Failed to update lease" err="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" lock="capi-system/controller-leader-election-capi" I0724 18:17:50.877941 1 leaderelection.go:299] "Failed to renew lease" lock="capi-system/controller-leader-election-capi" err="context deadline exceeded" E0724 18:17:50.878054 1 main.go:402] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Fri, 24 Jul 2026 18:16:55 +0000 Finished: Fri, 24 Jul 2026 18:18:01 +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-5647546676-hmlmm (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-5vk46 (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-5vk46: 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 42m default-scheduler Successfully assigned capi-system/capi-controller-manager-5647546676-hmlmm to instance Normal Pulled 37m (x2 over 42m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.13.2" already present on machine Warning Unhealthy 37m (x10 over 38m) kubelet Readiness probe failed: Get "http://10.0.0.208:9440/readyz": dial tcp 10.0.0.208:9440: connect: connection refused Normal Killing 37m (x4 over 38m) kubelet Container manager failed liveness probe, will be restarted Normal Created 37m (x2 over 42m) kubelet Created container manager Normal Started 37m (x2 over 42m) kubelet Started container manager Warning Unhealthy 36m kubelet Readiness probe failed: Get "http://10.0.0.208:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 36m kubelet Liveness probe failed: Get "http://10.0.0.208:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 36m (x4 over 38m) kubelet Liveness probe failed: Get "http://10.0.0.208:9440/healthz": dial tcp 10.0.0.208:9440: connect: connection refused