
                    For fargate, we pick up the best solutions provided by github life savers.
                    If google brings you here, you are so lucky! These life savers are angels, they have well solved your problems.
                    So do not waste time scrolling the original issue threads just to dig out solutions... 
                    Here you are, you are welcome. Then, go back to work!
                    

Yea thats the part in your documentation I was surprised by Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave +1 or me too comments

containers roadmap [EKS] [request]: Remove requirement of public IPs on EKS managed worker nodes

Hey folks Native support for Kubernetes taints is now available in managed node groups!

What's New
Docs
eksctl
CloudFormation 

containers roadmap [EKS] [request]: Managed Node Groups support for node taints

@cullenmcdermott

The new proposal looks interesting Quick question though Update 1/9/19:
After talking about this internally 

containers roadmap EKS IAM Roles for Service Accounts (Pods)

Alright following up here on what Bob mentioned in his Container Day keynote earlier today From now on you can give this feature a try in ap-southeast-1 

containers roadmap [ECR]: Allow for alternate mediaTypes

As a general comment on all resources it would be great if we had some way to define IAM role(s) with differing permissions 

containers roadmap AWS Controllers for Kubernetes (ACK)

upstream option is no longer supported in CoreDNS  v1.7.0 Tell us about the problem you're trying to solve What are you trying to do 

containers roadmap [EKS] CoreDNS v1.7.0 fails to start after upgrading cluster to Kubernetes 1.18

@tabern As part of this and for kube-proxy specifically Add support for managing CoreDNS and kube-proxy with EKS add-ons Roadmap feature from #252 

containers roadmap [EKS]: Support CoreDNS and kube-proxy in EKS add-ons

@tomfotherby  yep that works fine but that is using the old in-tree NFS driver approach rather than a new CSI plug-in driver This request is for CSI support 