Name:             capi-controller-manager-bc4cf8c95-jpbr6
Namespace:        capi-system
Priority:         0
Service Account:  capi-manager
Node:             instance/199.19.213.202
Start Time:       Thu, 21 May 2026 05:39:24 +0000
Labels:           cluster.x-k8s.io/provider=cluster-api
                  control-plane=controller-manager
                  pod-template-hash=bc4cf8c95
Annotations:      <none>
Status:           Running
SeccompProfile:   RuntimeDefault
IP:               10.0.0.69
IPs:
  IP:           10.0.0.69
Controlled By:  ReplicaSet/capi-controller-manager-bc4cf8c95
Containers:
  manager:
    Container ID:  containerd://afd0fd7d6b447e93ea2f42dcc17d742d0d328820e8b883f6b3ecf56bab3c04a8
    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:   Thu, 21 May 2026 06:09:24 +0000
    Last State:  Terminated
      Reason:    Error
      Message:   controllerGroup="cluster.x-k8s.io" controllerKind="Machine" worker count=10
I0521 05:39:53.331189       1 controller.go:239] "Starting Controller" controller="machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment"
I0521 05:39:53.331211       1 controller.go:248] "Starting workers" controller="machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" worker count=10
I0521 05:39:53.331237       1 controller.go:239] "Starting Controller" controller="topology/machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet"
I0521 05:39:53.331254       1 controller.go:248] "Starting workers" controller="topology/machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" worker count=1
I0521 05:39:53.331294       1 controller.go:239] "Starting Controller" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding"
I0521 05:39:53.331306       1 controller.go:248] "Starting workers" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" worker count=10
E0521 06:09:19.241497       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": net/http: request canceled (Client.Timeout exceeded while awaiting headers), falling back to slow path
E0521 06:09:24.241312       1 leaderelection.go:436] error retrieving resource lock capi-system/controller-leader-election-capi: 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
I0521 06:09:24.241373       1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded
E0521 06:09:24.241456       1 main.go:433] "Problem running manager" err="leader election lost" logger="setup"

      Exit Code:    1
      Started:      Thu, 21 May 2026 05:39:25 +0000
      Finished:     Thu, 21 May 2026 06:09:24 +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-bc4cf8c95-jpbr6 (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-2lbk8 (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-2lbk8:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    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  34m                  default-scheduler  Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-jpbr6 to instance
  Normal  Pulled     4m31s (x2 over 34m)  kubelet            Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine
  Normal  Created    4m31s (x2 over 34m)  kubelet            Created container manager
  Normal  Started    4m31s (x2 over 34m)  kubelet            Started container manager