If you're deploying a cluster with kube-aws:
t2.mediumshould be chosen for the cluster to work reliably
kube-aws tries its best to not modify your existing AWS resources therefore it's users' responsibility to ensure existing AWS resources provided to
kube-aws are properly configured.
Please note that you don't need to care if you've instructed
kube-aws to create all the AWS resources for you i.e. you've omitted
kube-aws does modify are:
hostedZoneIdconfiguration key in
cluster.yaml for more details.
All the other configurations for existing AWS resources must be done property by users before
kube-aws is run.
For example, if you're deploying a cluster to an existing VPC:
0.0.0.0/0would be needed or your cluster won't come up. See a relevant issue about it.
KubernetesClusterand your cluster's name for the value.
Once you understand pre-requisites, you are ready to launch your first Kubernetes cluster.