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