What were you trying to accomplish?
Upgrade kube-proxy.

What happened?
kube-proxy is being downgraded kube-proxy:v1.20.4-eksbuild.2 -> kube-proxy:v1.20.4-eksbuild.1
This is because of hardcoded value in kube_proxy.go:
https://github.com/weaveworks/eksctl/blob/8c022c9b8d124e9a2fdb7a09820e5a5ffec529d4/pkg/addons/default/kube_proxy.go#L159

How to reproduce it?

• create EKS

Location

• Browser
• CLI
• API
• Documentation

Motivation

Connecting to AWS RDS is complicated without a step-by-step guide unique to Porter.

Requirements

• Document how to set up the RDS instance if it doesn't exist.
• Document how to connect to the RDS instance from the same VPC.
• Document how to configure VPC peering if an RDS instance already exist

PR o'clock

Description

Resolves #774

The change is intended to improve the ability to manage worker groups using maps. Which should allow to more flexibly add/remove worker groups (improve this: https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/docs/faq.md#how-do-i-safely-remove-old-worker-groups).

The change includes suggested in #774 changes which include:

The logs in info mode should state the reason for cordoning/termination.

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