EKS Clusters Built with only whats required for fast and secure Kubernetes workloads
Amazon's EKS is great for handling the Kuberentes control plane & etcd, but it leaves some of the complexity of managing the Kubernetes nodes to the user. Why not incorporate the management of the nodes themsleves back into feature-rich Kubernetes abstractions?
By using the cloud native design of k3os and coupling it with Terraform and ASGs, we can decrease the "state" of our server layer and shift our complexity up to the Kubernetes layer. This essentially makes EKS as turn-key and fully managed as Azure's AKS and Google's GKE.
TF plan will create ASG comprised of k3os workers that should bootstrap themselves into an EKS cluster
Eventual goal is to have Terraform create the EKS cluster as well for a "single-click" deploy of a Kubernetes stack.
Variables to set
You will probably need to define the following TF vars (e.g. terraform.tfvars)
- aws_ami - AMI for k3os
- vpc_subnets - subnets that the ASG should deploy to
- vpc_id - VPC ID
- aws_profile - Local IAM profile for your
~/.aws/credentialsfile. Additioanlly you can change this section of the TF plan to just use the default. - aws_credentials_file - Path to AWS credentials file. Usually
~/.aws/credentials.