Ensure consistency across replica-based CLI printer columns

[killianmuldoon]

A couple of changes are being proposed to bring CLI printer columns related to replica columns in line with Kubernetes types.

Additional work needs to be done to bring the printer columns fully in line with Kubernetes. Note, the below changes can not be made until we are updating the Cluster API api version (currently at v1beta1).

Using the Kubernetes Daemonset as a model we have:

DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE

Replica related fields, and the source of their values, are listed below:

1. KubeadmControlPlane
   - Replicas => .status.replicas
   • Ready => .status.readyReplicas
   • Updated => .status.updatedReplicas
   • Unavailable => .status.unavailableReplicas
2. MachineDeployments
   • Replicas => .status.replicas
   • Ready => .status.readyReplicas
   • Updated => .status.updatedReplicas
   • Unavailable => .status.unavailableReplicas
3. MachineSets
   • Replicas => .status.replicas
   • Ready => .status.readyReplicas
   • Available => .status.availableReplicas
4. MachinePools
   • Replicas => .status.replicas

The following are needed to bring each of these types in line

• 🌱 Add desired number column to KCP, MD, MS, MachinePool #6164
• Rename 'replicas' to 'current' in KubeadmControlPlane, MachineDeployments and MachineSet kubectl output #6227
• Add "Available" and "Ready" to MachinePools
• Change "Unavailable" to "Available" in MachineDeployments and KubeadmControlPlane
• Change "Updated" to "Up-to-date" in MachineDeployments and KubeadmControlPlane
• Consider adding "Up-to_date" in MachineSets and MachinePools (This requires a more substantial change to the API)
• Reorder columns in all types so we have (DESIRED CURRENT READY UP-TO-DATE AVAILABLE)

/area api

[fabriziopandini]

/milestone Next
/kind api-change

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[fabriziopandini]

/lifecycle frozen

[fabriziopandini]

/triage accepted
/help

[k8s-ci-robot]

@fabriziopandini:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/triage accepted
/help

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/test-infra repository.