Improve status.Ready Fields in the contract

[fabriziopandini]

What would you like to be added (User Story)?

As a user I would like a clean and simple API

Detailed Description

As per 29th of May office hour discussion, status.Ready might be a little be confusing for at least two reasons:

• status.Ready is relevant in the provisioning workflow, but not after
• status.Ready is now confused with conditions.Ready

When designing the next API version we should consider if and how to remove the confusion about status.Ready

Anything else you would like to add?

see https://kubernetes.slack.com/archives/C8TSNPY4T/p1716892079243969

Label(s) to be applied

/kind api-change

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[sbueringer]

Will be addressed via #10897, pleaes take a look at the proposal for more details.
/close

[k8s-ci-robot]

@sbueringer: Closing this issue.

In response to this:

Will be addressed via #10897, pleaes take a look at the proposal for more details.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.