Address issue #138 correct max-pods for t3/t2.small instances

[andredupreez]

Issue #138

Updated the t2 and t3.small instances max pods to 11 as per the updated CNI plugin version 1.3.0.
Maximum of 11 pods should be schedulable for the above mentioned instance types.

[vincentheet]

@micahhausler any chance you can approve and merge this small PR? Currently we have to deploy extra VM's which is not resource efficient.

The change reflects the official documentation https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html and your VPC CNI plugin correction in PR aws/amazon-vpc-cni-k8s#229

[micahhausler]

We have to hold off on merging this right now, as commented on #116, we have to wait for:

• Update CNI with new instance type limits - Updated instance types aws/amazon-vpc-cni-k8s#229
• Release new CNI version with updated instance types - CNI v 1.3.0
• Set new CNI version as default for new EKS clusters
• Update max-pods and release new AMI with updated instance types

We're working on making this process better, but for now this is blocked. Once 1.3.0 is released to EKS clusters (in the coming weeks) we'll release a new AMI with this update.

[vincentheet]

Seems like we are one checkbox further @micahhausler https://aws.amazon.com/about-aws/whats-new/2019/02/amazon-eks-releases-vpc-cni-plugin-v1-3-2-with-enhancements-for-/

[mogren]

Fixed in #231