Cluster-API takes the reason and the message from the infra-machine (in our case, the KubeVirtMachine) Ready condition, into the cluster-api Machine's InfrastructureReady condition. Currently the text is something like "0 of 2 completed". This is not very informative.
This PR changes the behavior so now the KV Machine Ready condition will include both the reason and the message from the failed condition.
That way, the cluster-api InfrastructureReady condition, will also contain the same reason and message. This will make the actual issue, if exists, to more accessible to the user.
Release notes:
Remove the setup counter from the KV-Machine ready status
Needs approval from an approver in each of these files:
- ~~[OWNERS](https://github.com/kubernetes-sigs/cluster-api-provider-kubevirt/blob/main/OWNERS)~~ [nunnatsa]
Approvers can indicate their approval by writing `/approve` in a comment
Approvers can cancel approval by writing `/approve cancel` in a comment
What this PR does / why we need it
Cluster-API takes the reason and the message from the infra-machine (in our case, the KubeVirtMachine)
Ready
condition, into the cluster-apiMachine
'sInfrastructureReady
condition. Currently the text is something like"0 of 2 completed"
. This is not very informative.This PR changes the behavior so now the KV Machine Ready condition will include both the reason and the message from the failed condition.
That way, the cluster-api
InfrastructureReady
condition, will also contain the same reason and message. This will make the actual issue, if exists, to more accessible to the user.Release notes: