EKS Fargate profiles support

[richardcase]

/kind feature

Describe the solution you'd like
When creating a EKS cluster i want the option to be able to use fargate for the workloads. Adding support for fargate profiles would be needed.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• Cluster-api-provider-aws version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[richardcase]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[richardcase]

/remove-lifecycle stale

[michaelbeaumont]

Mapping this to MachinePool feels like a little bit of a mismatch given that we don't have version, replicas, bootstrap, etc. We have Nodes but we don't really have spec.replicas. Do we think this is important?

[richardcase]

/label adr-required

[k8s-ci-robot]

@richardcase: The label(s) /label adr-required cannot be applied. These labels are supported: api-review, community/discussion, community/maintenance, community/question, cuj/build-train-deploy, cuj/multi-user, platform/aws, platform/azure, platform/gcp, platform/minikube, platform/other, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash

In response to this:

/label adr-required

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[richardcase]

Mapping this to MachinePool feels like a little bit of a mismatch given that we don't have version, replicas, bootstrap, etc. We have Nodes but we don't really have spec.replicas. Do we think this is important?

As this doesn't really match well to upstream CAPI kinds I wonder if we just create an AWSFargateProfile kind with associated controller? And maybe it just cares about its matching AWSManagedControlPlane. WDYT?

[richardcase]

@michaelbeaumont @randomvariable - i think we should probably capture the decision on how we implement this in an ADR

[richardcase]

/milestone v0.6.5