should arlon detect illegal/unsupported settings or changes to CAPI base cluster?

[bcle]

Arlon and ArgoCD apply CAPI manifests "as is". The user is fully responsible for the manifest contents. Examples of bad things that can happen:

• It's not always intuitive to know what kubernetes versions are supported by the current version of CAPI providers. It's also provider specific. For example, for AWS, clusterawsadm ami list is the best way. An unsupported version will result in a non-converging cluster that fails silently.
• During an update/upgrade caused by modifying a shared base cluster, existing cluster manifests disallow some resource fields (in the spec) to change. I forgot which one(s) I tried (instance type?). What'll happen is, in the best case, argocd will flag some resources as out of sync, and in the worst case, they will appear in sync and healthy, but actually unhealthy until you look at CAPI/CAPA pod logs. (duplicate of Changes to "immutable" fields of base cluster results in poor UX for existing clusters (OutOfSync) #137)

Aha! Link: https://pf9.aha.io/features/ARLON-134