The `kubernetes-addons` module within this framework allows you to deploy Kubernetes add-ons using both the Terraform Helm and Kubernetes providers with simple **true/false** flags.
The framework currently provides support for the following add-ons.
| Add-on | Description |
|-----------|-----------------
| Agones |
| FluentBit |
| OpenTelemetry |
| cert-manager |
| Cluster Autoscaler |
| AWS Load Balancer Controller
| Metrics Server |
| Nginx |
| Prometheus |
| Traefik |
| Windows VPC Controller |
| [Agones](./agones) | Deploys Agones into an EKS cluster. |
| [FluentBit](./aws-for-fluent-bit) | Deploys Fluent Bit into an EKS cluster. |
| [AWS Load Balancer Controller](./fargate-fluent-bit) | Deploys the AWS Load Balancer Controller into an EKS cluster. |
| [cert-manager](./cert-manager) | Deploys cert-manager into an EKS cluster.
| [Cluster Autoscaler](./cluster-autoscaler) | Deploys the standard cluster autoscaler. |
| [Metrics Server](./managed-add-ons) | Deploys the Kubernetes Metrics Server into an EKS cluster. |
| [Nginx](./nginx) | Deploys the NGINX Ingress Controller into an EKS cluster. |
| [OpenTelemetry](./aws-load-balancer-controller) | Deploys the OpenTelemetry Collector into an EKS cluster.
| [Prometheus](./prometheus) | Deploys Prometheus into an EKS cluster. |
| [Traefik](./traefik) | Deploys Traefik Proxy into an EKS cluster.
Amazon EKS doesn't modify any of your Kubernetes add-ons when you update a cluster to newer versions.
It's important to upgrade EKS Addons [Amazon VPC CNI](https://github.com/aws/amazon-vpc-cni-k8s), [DNS (CoreDNS)](https://docs.aws.amazon.com/eks/latest/userguide/managing-coredns.html) and [KubeProxy](https://docs.aws.amazon.com/eks/latest/userguide/managing-kube-proxy.html) for each EKS release.
This [README](eks_cluster_addons_upgrade/README.md) guides you to update the EKS Cluster and the addons for newer versions that matches with your EKS cluster version
Updating a EKS cluster instructions can be found in [AWS documentation](https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html).
The purpose of this document is to provide an overview of the steps for upgrading the EKS Cluster from one version to another. Please note that EKS upgrade documentation gets published by AWS every year.
The current version of the upgrade documentation while writing this [README](https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html)
#### Pre-Requisites:
1. Download the latest upgrade docs from AWS sites (https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html)
2. Always upgrade one increment at a time (E.g., 1.17 to 1.18). AWS doesn't support upgrades from 1.16 to 1.18 directly
This table shows the supported plugin versions for each EKS Kubernetes version
1. Change the version in Terraform to desired version under `base.tfvars`. See the example below
```hcl-terraform
kubernetes_version = "1.20"
```
2. Apply the changes to the cluster with Terraform. This step will upgrade the Control Plane and Data Plane to the newer version, and it will roughly take 35 mins to 1 hour
3. Once the Cluster is upgraded to desired version then please updated the following plugins as per the instructions
#### Steps to upgrade Add-ons:
Just update the latest versions in `base.tfvars` file as shown below. EKS Addon latest versions can be found in AWS EKS Console under Addon section or from AWS documentation.
##### KubeProxy
```hcl-terraform
enable_kube_proxy_addon = true
kube_proxy_addon_version = "v1.20.4-eksbuild.2"
```
##### CoreDNS
```hcl-terraform
enable_coredns_addon = true
coredns_addon_version = "v1.8.3-eksbuild.1"
```
##### VPC CNI
```hcl-terraform
enable_vpc_cni_addon = true
vpc_cni_addon_version = "v1.8.0-eksbuild.1"
```
Apply the changes to the cluster with Terraform.
## Important Note
Please note that you may need to update other Kubernetes Addons deployed through Helm Charts to match with new Kubernetes upgrade version
