sedefsavas

/lgtm /approve

I agree, let's merge this right after the change is in CAPA.

This is a breaking change, we'll need to fix in the next major release.

[Slack thread](https://kubernetes.slack.com/archives/CD6U2V71N/p1648536004859049) this issue was originally discussed. /triage accepted /important long-term /kind documentation

/triage accepted /priority important-longterm /area provider/eks

Quoting from https://cluster-api.sigs.k8s.io/contributing#optional-vs-required ``` Fields SHOULD be pointers if there is a good reason for it, for example: - the nil and the zero values (by Go standards) have semantic...

> What about the primitive types field like string, int32 etc. In case we don't use pointer, suppose for int32 field how would w know if it is 0 or...

/triage accepted

@JoelSpeed There is no active work going on for this. Availability zones, placement groups and possibly other points in the issue all may be suitable to group together considering that...

I will write an ADR for this with @shysank to explain how AWS Systems Manager would be a good fit for this clean up. https://docs.aws.amazon.com/systems-manager/latest/userguide/execute-remote-commands.html CAPZ has a similar mechanism...