Initial Giant Swarm Cluster API (CAPI) release for AWS with feature alignment between Giant Swarm clusters and Cluster API clusters. This is alpha quality and only intended for testing. There is no migration path to or from this release.

We should have a decision on all features part of our Giant Swarm clusters. Such a decision could be:

• already implemented;
• will be implemented within this milestone;
• will be implemented at a later point in time (which milestone, TBD);
• optional feature (not on the critical path; might be implemented if we have customers using it);
• dropped feature (we don't want to support it anymore; migration path might be needed if we have customers using it);

What should be part of this milestone?

• feature alignment (see above);
• cluster creation;
• cluster deletion;
• cluster access;
• cluster monitoring (metrics & dashboards)
• cluster alerting, with the option to disable it per cluster (also, useful for our existing clusters to improve oncall experience and flexibility);
• cluster workload access (DNS, load balancers);
• use flatcar;