feat! Release 5.0.0

[zacharyblasczyk]

Upgrading from 4.x -> 5.x

5.0.0 introduced autoscaling to the EKS cluster and made the size variable the preferred way to set the cluster size.
Previously, unless the size variable was set explicitly, there were default values for the following variables:

• kubernetes_instance_types
• kubernetes_node_count
• elasticache_node_type
• database_instance_class

The size variable is now defaulted to small, and the following values to can be used to partially override the values
set by the size variable:

• kubernetes_instance_types
• kubernetes_min_nodes_per_az
• kubernetes_max_nodes_per_az
• elasticache_node_type
• database_instance_class

For more information on the available sizes, see the Cluster Sizing section.

If having the cluster scale nodes in and out is not desired, the kubernetes_min_nodes_per_az and
kubernetes_max_nodes_per_az can be set to the same value to prevent the cluster from scaling.

This upgrade is also intended to be used when upgrading eks to 1.29.

We have also upgraded the following Kubernetes addons:

• MySQL Aurora (8.0.mysql_aurora.3.07.1)
• redis (7.1)
• external-dns helm chart (v1.15.0)
• aws-efs-csi-driver (v2.0.7-eksbuild.1)
• aws-ebs-csi-driver (v1.35.0-eksbuild.1)
• coredns (v1.11.3-eksbuild.1)
• kube-proxy (v1.29.7-eksbuild.9)
• vpc-cni (v1.18.3-eksbuild.3)

⚠️ Please remove the enable_dummy_dns and enable_operator_alb variables
as they are no longer valid flags. They were provided to support older versions of
the module that relied on an alb not created by the ingress controller.