PR o'clock

Description

1. Add ingress rule to workers and cluster security groups to allow Fargate pods to communicate with EC2 nodes
2. Allow EKS Fargate profiles to be created via input eks_fargate_profiles = [...]. This also creates an IAM role for pod execution and extends the aws-auth ConfigMap.

Checklist

• CI tests are passing
• README.md has been updated aft

Looking for a recommendation before we use it in our higher level environment.

Requirement:

We're using self managed kops k8s clusters across all our environment
We decided to use spotallocation capacity optimized statergy
We need to test aws-node-termination-handler e2e in our lower level environment with 2 nodes 1 per AZ. before we say it's production grade and can be used in across the

Some log entries are using V(1) but still get emitted by default.
We should have a way to mute debug logs using a flag.

There should be a way to get a kubeconfig for eks clusters that already exist.

Similar to this PR for GCP: https://gist.github.com/geekflyer/b78adab2667d8526a1dd593bc5c844bf#file-gke-ts-L33-L66

This should be the UI endpoint not the API server.