Name: capi-controller-manager-5647546676-l5ffp Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.223 Start Time: Thu, 20 Aug 2026 07:09:11 +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://b8cb85b3bc71d1027541f05fc30c480cb211657ecfe67f9c7e9df7cdd5320e1b 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, 20 Aug 2026 07:14:24 +0000 Last State: Terminated Reason: Error Message: MachineDeployment" worker count=50 I0820 07:09:41.016457 1 controller.go:303] "Starting Controller" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" I0820 07:09:41.016699 1 controller.go:306] "Starting workers" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" worker count=100 I0820 07:09:41.110472 1 controller.go:303] "Starting Controller" controller="crdmigrator" controllerGroup="apiextensions.k8s.io" controllerKind="CustomResourceDefinition" I0820 07:09:41.110516 1 controller.go:306] "Starting workers" controller="crdmigrator" controllerGroup="apiextensions.k8s.io" controllerKind="CustomResourceDefinition" worker count=1 I0820 07:09:41.113539 1 controller.go:303] "Starting Controller" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" I0820 07:09:41.113597 1 controller.go:306] "Starting workers" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" worker count=10 E0820 07:12:53.536325 1 leaderelection.go:445] "Failed to update lease optimistically, falling back to slow path" err="Put \"https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capi-system/leases/controller-leader-election-capi?timeout=5s\": net/http: request canceled (Client.Timeout exceeded while awaiting headers)" lock="capi-system/controller-leader-election-capi" E0820 07:12:58.536336 1 leaderelection.go:452] "Error retrieving lease lock" err="Get \"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" I0820 07:12:58.536432 1 leaderelection.go:299] "Failed to renew lease" lock="capi-system/controller-leader-election-capi" err="context deadline exceeded" E0820 07:12:58.536622 1 main.go:402] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 20 Aug 2026 07:09:12 +0000 Finished: Thu, 20 Aug 2026 07:12:58 +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-l5ffp (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-mbdwm (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-mbdwm: 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 9m49s default-scheduler Successfully assigned capi-system/capi-controller-manager-5647546676-l5ffp to instance Normal Pulled 9m49s kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.13.2" already present on machine Normal Created 9m49s kubelet Created container manager Normal Started 9m48s kubelet Started container manager Warning Unhealthy 5m39s (x3 over 5m59s) kubelet Liveness probe failed: Get "http://10.0.0.208:9440/healthz": dial tcp 10.0.0.208:9440: connect: connection refused Warning Unhealthy 4m39s (x14 over 5m59s) kubelet Readiness probe failed: Get "http://10.0.0.208:9440/readyz": dial tcp 10.0.0.208:9440: connect: connection refused Normal Killing 4m39s (x6 over 5m39s) kubelet Container manager failed liveness probe, will be restarted