Winnie Kwon
FailureDomain in `AWSMachine`. From [CAPI book](https://cluster-api.sigs.k8s.io/developer/providers/machine-infrastructure.html?highlight=failuredomain#data-types) > providers will be expected to remove the field in the next version that provides breaking API changes, favoring the value defined on Machine.Spec.FailureDomain...
Top-level issue for Adopting CAPI's Server Side Apply to support ClusterClass * https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/3530 Specific Issues that require v1beta2 API * https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/3528 * https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/3536
/kind documentation
/test pull-cluster-api-provider-aws-e2e
Investigated the test failure and filed an issue - https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/3399 I've ran the tests multiple times locally and it passed except once, which had the same failure as the filed...
Gathering stats /retest
Test can pass but the cluster is affected by the continuous patching of subnets in AWSCluster by capi and capa controllers reported in https://github.com/kubernetes-sigs/cluster-api/issues/6320
Blocked by * https://github.com/kubernetes-sigs/cluster-api/issues/6320