I can't change some resources, Immutability error

[UryDanko]

/kind bug

What steps did you take and what happened:

I created a cluster with a node pool and a few nodes in it by using AWSManagedMachinePool and MachinePool.
After that, I changed the disk size in the node pool.
I got an error:

one or more objects failed to apply, reason: error when patching "/dev/shm/1327104644": admission webhook "validation.awsmanagedmachinepool.infrastructure.cluster.x-k8s.io" denied the request: AWSManagedMachinePool.infrastructure.cluster.x-k8s.io "prov-node-pool" is invalid: spec.diskSize: Invalid value: 50: field is immutable.

What did you expect to happen:
I would expect that either disk size would be just increased. Or the nodes in the node pool will be rolled out with the new disk size.

Anything else you would like to add:
Actually almost the same error happen when I try, for example, to rename the node pool:

error when patching "/dev/shm/178698734": admission webhook "validation.awsmanagedmachinepool.infrastructure.cluster.x-k8s.io" denied the request: AWSManagedMachinePool.infrastructure.cluster.x-k8s.io "prov-node-pool" is invalid: spec.eksNodegroupName: Invalid value: "prov-node-pool": field is immutable

So I see that some fields (tags, node pool min/max size) can be changed, and some fields are immutable, so I can't modify them. Unless I delete them manually and create new ones

Environment:

• Cluster-api-provider-aws version: 2.5.2
• Cluster-api-operator version: 0.11.0
• Kubernetes version: (use kubectl version): 1.29

[k8s-ci-robot]

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.

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.

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[UryDanko]

/remove-lifecycle stale