Alberto García Lamela

> manual testing is working as expected against capi 1.0.5 and kubemark 0.3.0 > I've given this a review again and it LGTM, do we want to give others a...

thanks a lot @elmiko, this looks great to me other than https://github.com/kubernetes/autoscaler/pull/4840#discussion_r925771269

Immutability is one important lack in current CRD OpenAPI validation. Also the fact that any conceptually required field that you want to default needs to be declared optional for client...

>with open api a required field can be defaulted and no error occurs because defaulting happens client-side before hitting the api server @vincepri That's actually not true afaik, structural schema...

Is there any other use cases we can think of for labels/annotations? e.g Syncing from [class to Nodes](https://github.com/kubernetes-sigs/cluster-api/pull/6255). For autoscaling in particular I'd expect this to be baked in MachineDeploymentClass...

Hey I'm a bit confused here, if I'm reading correctly the original [issue description](https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/2794#issue-1006464146) describes a problem that happens because all Machines are requeued all of a sudden in bulk,...

Thanks for giving this a go @arianvp! before proceeding any further with the impl details let's make sure there's community alignment on the short/medium/long term view for the proposal since...

>One thing that might be useful is to have a list of existing approvers in existing infrastructure providers so that we know what workflows we should not break. Sounds like...

/assign

@vincepri PR is in good shape but given the timelines and the lack of feedback/testing in real use I think we should probably punt on this until we release v1beta1....