terraform-aws-minikube
terraform-aws-minikube copied to clipboard
Terraform module for single node Kubernetes instance bootstrapped using kubeadm
AWS Minikube Terraform module
AWS Minikube is a single node Kubernetes deployment in AWS. It creates EC2 host and deploys Kubernetes cluster using Kubeadm tool. It provides full integration with AWS. It is able to handle ELB load balancers, EBS disks, Route53 domains etc.
- Updates
- Prerequisites and dependencies
- Including the module
- Using custom AMI Image
- Add-ons
- Custom add-ons
- Tagging
## Updates
- 26.8.2022 Update to Kubernetes 1.25.0 + Calico upgrade
- 21.8.2022 Update to Kubernetes 1.24.4
- 16.7.2022 Update to Kubernetes 1.24.3
- 27.6.2022 Update to Kubernetes 1.24.2
- 11.6.2022 Update to Kubernetes 1.24.1 + update add-ons + remove dependency on the template provider
- 8.5.2022 Update to Kubernetes 1.24.0 + update add-ons
- 23.3.2022 Update to Kubernetes 1.23.5 + update add-ons
- 19.2.2022 Update to Kubernetes 1.23.4
- 12.2.2022 Update to Kubernetes 1.23.2
- 29.12.2021 Update to Kubernetes 1.23.1
- 11.12.2021 Update to Kubernetes 1.23.0
## Prerequisites and dependencies
- AWS Minikube deploys into existing VPC / public subnet. If you don't have your VPC / subnet yet, you can use this configuration or this module to create one.
- The VPC / subnet should be properly linked with Internet Gateway (IGW) and should have DNS and DHCP enabled.
- Hosted DNS zone configured in Route53 (in case the zone is private you have to use IP address to copy
kubeconfig
and access the cluster).
- To deploy AWS Minikube there are no other dependencies apart from Terraform. Kubeadm is used only on the EC2 host and doesn't have to be installed locally.
Including the module
Although it can be run on its own, the main value is that it can be included into another Terraform configuration.
module "minikube" {
source = "github.com/scholzj/terraform-aws-minikube"
aws_region = "eu-central-1"
cluster_name = "my-minikube"
aws_instance_type = "t2.medium"
ssh_public_key = "~/.ssh/id_rsa.pub"
aws_subnet_id = "subnet-8a3517f8"
ami_image_id = "ami-b81dbfc5"
hosted_zone = "my-domain.com"
hosted_zone_private = false
tags = {
Application = "Minikube"
}
addons = [
"https://raw.githubusercontent.com/scholzj/terraform-aws-minikube/master/addons/storage-class.yaml",
"https://raw.githubusercontent.com/scholzj/terraform-aws-minikube/master/addons/heapster.yaml",
"https://raw.githubusercontent.com/scholzj/terraform-aws-minikube/master/addons/dashboard.yaml",
"https://raw.githubusercontent.com/scholzj/terraform-aws-minikube/master/addons/external-dns.yaml"
]
}
An example of how to include this can be found in the examples dir.
## Using custom AMI Image
AWS Minikube is built and tested on CentOS 7. But gives you the possibility to use their own AMI images. Your custom AMI image should be based on RPM distribution and should be similar to Cent OS 7. When ami_image_id
variable is not specified, the latest available CentOS 7 image will be used.
Add-ons
Currently, following add-ons are supported:
- Kubernetes dashboard
- Heapster for resource monitoring
- Storage class and CSI driver for automatic provisioning of persistent volumes
- External DNS (Replaces Route53 mapper)
- Ingress
The add-ons will be installed automatically based on the Terraform variables.
Custom add-ons
Custom add-ons can be added if needed. Fro every URL in the addons
list, the initialization scripts will automatically call kubectl -f apply <Addon URL>
to deploy it. Minikube is using RBAC. So the custom add-ons have to be RBAC ready.
Tagging
If you need to tag resources created by your Kubernetes cluster (EBS volumes, ELB load balancers etc.) check this AWS Lambda function which can do the tagging.