Clusterctl describe shows duplicate status/reason

[lentzi90]

What steps did you take and what happened?

1. Create a workload cluster
2. Use clusterctl describe to show details about the cluster
3. Look at the STATUS and REASON column. STATUS shows things like Available: True, while REASON shows Available.

What did you expect to happen?

The columns should not duplicate information. Normally STATUS would show True and REASON would show Available.

Cluster API version

v1.11.0

Kubernetes version

v1.33.4

Anything else you would like to add?

No response

Label(s) to be applied

/kind bug
/area clusterctl

[sbueringer]

Doesn't seem to occur when running e.g. clusterctl describe cluster development-161 --kubeconfig-context=kind-capi-test --show-conditions=Cluster,MachineDeployment,MachineSet,Machine --grouping=false --show-machinesets

[sbueringer]

/priority important-longterm
/triage accepted

[irapandey]

I would like to take this up and work on the issue.

[irapandey]

/assign

[irapandey]

I was able to reproduce the issue - Made sure I could see what false shall look like

ira@Iras-MacBook-Pro ~ % clusterctl describe cluster development-20459

NAME                                                             REPLICAS  AVAILABLE  READY  UP TO DATE  STATUS            REASON        SINCE  MESSAGE
Cluster/development-20459                                        2/2       0          0      2           Available: False  NotAvailable  12m    * WorkersAvailable:
│                                                                                                                                                 * MachineDeployment development-20459-md-0-255bf: 0 available replicas, at least 1 required
│                                                                                                                                                   (spec.strategy.rollout.maxUnavailable is 0, spec.replicas is 1)
├─ClusterInfrastructure - DockerCluster/development-20459-6nhdp                                          Ready: True       Ready         9m36s
├─ControlPlane - KubeadmControlPlane/development-20459-rwz5c     1/1       0          0      1
│ └─Machine/development-20459-rwz5c-m95bz                        1         0          0      1           Ready: False      NotReady      8m31s  * NodeHealthy:
│                                                                                                                                                 * Node.Ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady
│                                                                                                                                                   message:Network plugin returns error: cni plugin not initialized
└─Workers
  └─MachineDeployment/development-20459-md-0-255bf               1/1       0          0      1           Available: False  NotAvailable  9m41s  0 available replicas, at least 1 required (spec.strategy.rollout.maxUnavailable is 0, spec.replicas
    │                                                                                                                                           is 1)
    └─Machine/development-20459-md-0-255bf-lc57t-2zg8n           1         0          0      1           Ready: False      NotReady      8m28s  * NodeHealthy:
                                                                                                                                                  * Node.Ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady
                                                                                                                                                    message:Network plugin returns error: cni plugin not initialized

What we expect shall look like this

ira@Iras-MacBook-Pro ~ % clusterctl describe cluster development-20459

NAME                                                             REPLICAS  AVAILABLE  READY  UP TO DATE  STATUS            REASON        SINCE  MESSAGE
Cluster/development-20459                                        2/2       0          0      2           False  NotAvailable  12m    * WorkersAvailable:
│                                                                                                                                                 * MachineDeployment development-20459-md-0-255bf: 0 available replicas, at least 1 required
│                                                                                                                                                   (spec.strategy.rollout.maxUnavailable is 0, spec.replicas is 1)
├─ClusterInfrastructure - DockerCluster/development-20459-6nhdp                                         True       Ready         9m36s
├─ControlPlane - KubeadmControlPlane/development-20459-rwz5c     1/1       0          0      1
│ └─Machine/development-20459-rwz5c-m95bz                        1         0          0      1            False      NotReady      8m31s  * NodeHealthy:
│                                                                                                                                                 * Node.Ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady
│                                                                                                                                                   message:Network plugin returns error: cni plugin not initialized
└─Workers
  └─MachineDeployment/development-20459-md-0-255bf               1/1       0          0      1          False  NotAvailable  9m41s  0 available replicas, at least 1 required (spec.strategy.rollout.maxUnavailable is 0, spec.replicas
    │                                                                                                                                           is 1)
    └─Machine/development-20459-md-0-255bf-lc57t-2zg8n           1         0          0      1           False      NotReady      8m28s  * NodeHealthy:
                                                                                                                                                  * Node.Ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady
                                                                                                                                                    message:Network plugin returns error: cni plugin not initialized

[sbueringer]

Not sure, @fabriziopandini ?