Name: capi-controller-manager-5647546676-s2vn8 Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.227 Start Time: Sun, 28 Jun 2026 20:53:17 +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.82 IPs: IP: 10.0.0.82 Controlled By: ReplicaSet/capi-controller-manager-5647546676 Containers: manager: Container ID: containerd://eb2f24b2a339b1f0e99f3ac380026606eba802bfc6500e8d4c2f214b829c2809 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: Sun, 28 Jun 2026 20:58:04 +0000 Last State: Terminated Reason: Error Message: ker count=50 I0628 20:53:46.867997 1 controller.go:303] "Starting Controller" controller="topology/machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" I0628 20:53:46.868025 1 controller.go:306] "Starting workers" controller="topology/machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" worker count=1 I0628 20:53:46.967006 1 controller.go:303] "Starting Controller" controller="crdmigrator" controllerGroup="apiextensions.k8s.io" controllerKind="CustomResourceDefinition" I0628 20:53:46.967045 1 controller.go:306] "Starting workers" controller="crdmigrator" controllerGroup="apiextensions.k8s.io" controllerKind="CustomResourceDefinition" worker count=1 I0628 20:53:46.968215 1 controller.go:303] "Starting Controller" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" I0628 20:53:46.968248 1 controller.go:306] "Starting workers" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" worker count=10 E0628 20:57:17.761394 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\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" lock="capi-system/controller-leader-election-capi" E0628 20:57:22.761507 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" I0628 20:57:22.761575 1 leaderelection.go:299] "Failed to renew lease" lock="capi-system/controller-leader-election-capi" err="context deadline exceeded" E0628 20:57:22.761676 1 main.go:402] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Sun, 28 Jun 2026 20:53:19 +0000 Finished: Sun, 28 Jun 2026 20:57:22 +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-s2vn8 (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-5wc2b (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-5wc2b: 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 36m default-scheduler Successfully assigned capi-system/capi-controller-manager-5647546676-s2vn8 to instance Warning Unhealthy 31m (x3 over 32m) kubelet Liveness probe failed: Get "http://10.0.0.82:9440/healthz": dial tcp 10.0.0.82:9440: connect: connection refused Normal Pulled 31m (x2 over 36m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.13.2" already present on machine Normal Created 31m (x2 over 36m) kubelet Created container manager Normal Started 31m (x2 over 36m) kubelet Started container manager Warning Unhealthy 31m (x6 over 32m) kubelet Readiness probe failed: Get "http://10.0.0.82:9440/readyz": dial tcp 10.0.0.82:9440: connect: connection refused Normal Killing 31m (x2 over 31m) kubelet Container manager failed liveness probe, will be restarted