Alias version pin is dropped when storage version is v1beta1

[jmdeal]

Description

Observed Behavior:
When the storage version is v1beta1, the version pin for an alias on a v1 NodePool is dropped. In practice this shouldn't be problematic since version pinning for discovered AMIs isn't supported until v1.0.0 (at which point v1 is the storage version), but this behavior is surprising.

Expected Behavior:
Users should be able to set a version pin on the v1 resource, even when the storage version is v1beta1.

Versions:

• Chart Version: 1.0.0
• Kubernetes Version (kubectl version): 1.30

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment