fix: downward adjust the minimum controller node size

Panfactum · Mar 25, 2024 · 9c84950 · 9c84950
1 parent 43059ff
commit 9c84950
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/packages/reference/environments/production/us-east-2/aws_eks/terragrunt.hcl b/packages/reference/environments/production/us-east-2/aws_eks/terragrunt.hcl
@@ -30,7 +30,7 @@ inputs = {
   service_cidr          = "172.20.0.0/16"
 
   controller_node_count          = 3
-  controller_node_instance_types = ["t3a.large"]
+  controller_node_instance_types = ["t3a.medium"]
   controller_node_subnets = [
     "PRIVATE_A",
     "PRIVATE_B",

diff --git a/...ges/website/src/app/(web)/docs/guides/bootstrapping/kubernetes-cluster/page.mdx b/...ges/website/src/app/(web)/docs/guides/bootstrapping/kubernetes-cluster/page.mdx
@@ -162,7 +162,7 @@ The subnets you choose should be **private** and should each be in a different A
 
 The nodes created by this module are used to run cluster-critical controllers, without which your cluster will not
 function properly. [^5] You should use at least three to facilitate the high-availability algorithms used by some of the
-controllers. The `t3a.large` is the minimum recommended instance size if using three nodes.
+controllers. The `t3a.medium` is the minimum recommended instance size if using three nodes.
 
 [^5]: Additional "worker" nodes will be dynamically provisioned by [Karpenter](https://karpenter.sh/) in a future section of this guide.