Name: capi-controller-manager-5647546676-gbcvz Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.78 Start Time: Fri, 03 Jul 2026 19:39:47 +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.227 IPs: IP: 10.0.0.227 Controlled By: ReplicaSet/capi-controller-manager-5647546676 Containers: manager: Container ID: containerd://418ed1dcb9ff1488876e9aed15ab2a6d48b1f2fa97665066098876de290a2082 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, 03 Jul 2026 19:43:50 +0000 Last State: Terminated Reason: Error Message: 23097 1 controller.go:303] "Starting Controller" controller="topology/machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" I0703 19:40:17.723111 1 controller.go:306] "Starting workers" controller="topology/machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" worker count=1 I0703 19:40:17.815744 1 controller.go:303] "Starting Controller" controller="crdmigrator" controllerGroup="apiextensions.k8s.io" controllerKind="CustomResourceDefinition" I0703 19:40:17.815784 1 controller.go:306] "Starting workers" controller="crdmigrator" controllerGroup="apiextensions.k8s.io" controllerKind="CustomResourceDefinition" worker count=1 I0703 19:40:17.823334 1 controller.go:303] "Starting Controller" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" I0703 19:40:17.823373 1 controller.go:306] "Starting workers" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" worker count=10 E0703 19:43:22.386495 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" E0703 19:43:27.386590 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" I0703 19:43:27.386639 1 leaderelection.go:299] "Failed to renew lease" lock="capi-system/controller-leader-election-capi" err="context deadline exceeded" E0703 19:43:27.386716 1 main.go:402] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Fri, 03 Jul 2026 19:39:48 +0000 Finished: Fri, 03 Jul 2026 19:43:27 +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-gbcvz (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-tbv6b (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-tbv6b: 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 32m default-scheduler Successfully assigned capi-system/capi-controller-manager-5647546676-gbcvz to instance Warning Unhealthy 28m (x3 over 29m) kubelet Liveness probe failed: Get "http://10.0.0.227:9440/healthz": dial tcp 10.0.0.227:9440: connect: connection refused Warning Unhealthy 28m (x4 over 29m) kubelet Readiness probe failed: Get "http://10.0.0.227:9440/readyz": dial tcp 10.0.0.227:9440: connect: connection refused Normal Killing 28m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 28m (x2 over 32m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.13.2" already present on machine Normal Created 28m (x2 over 32m) kubelet Created container manager Normal Started 28m (x2 over 32m) kubelet Started container manager