v1beta2 contract: align ProviderID, DataSecretName, and Replicas field types

[damdo]

Parent: #5448

In the new v1beta3 types, several fields change type to match the v1beta2 contract:

AWSMachine.Spec.ProviderID: *string → string

// +optional
// +kubebuilder:validation:MinLength=1
// +kubebuilder:validation:MaxLength=512
ProviderID string `json:"providerID,omitempty"`

EKSConfig.Status.DataSecretName: *string → string

DataSecretName string `json:"dataSecretName,omitempty"`

MachinePool Replicas: int32 → *int32

CAPI reads status.replicas from the infra MachinePool via unstructured access.

Replicas *int32 `json:"replicas,omitempty"`

Affects v1beta3 versions of: AWSMachinePoolStatus, AWSManagedMachinePoolStatus, RosaMachinePoolStatus.

Note: readyReplicas, availableReplicas, upToDateReplicas are NOT read from the infra provider by CAPI — they are computed by CAPI core. No need to add them to CAPA types.

The v1beta2 spoke types keep the old field types. Conversion webhooks handle the translation.

[kubernetes-prow]

This issue is currently awaiting triage.

If CAPA/CAPI contributors determines 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.

Details

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.