From 0a4a48635a21a5ce93f3f319a62ad349b7f7c47e Mon Sep 17 00:00:00 2001 From: sudobangbang Date: Tue, 27 Feb 2024 12:43:48 -0800 Subject: [PATCH] Update aws-eks.md --- docs/aws-eks.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/aws-eks.md b/docs/aws-eks.md index 801191f6..81a1fe4c 100644 --- a/docs/aws-eks.md +++ b/docs/aws-eks.md @@ -10,8 +10,9 @@ After creating the cluster we'll walk through installing the following add-ons a ## Table of Contents: 1. [Create EKS Cluster](#create-cluster) 2. [Make sure EKS Cluster has OIDC Provider](#check-oidc) -3. [Install EBS CSI Add-on](#ebs-addon) -4. [Install AWS LB Controller](#aws-lb) +3. [Install Node Autoscaling](#node-autoscaler) +4. [Install EBS CSI Add-on](#ebs-addon) +5. [Install AWS LB Controller](#aws-lb) 4. [Install NGINX Ingress Controller](#nginx-ingress) --- @@ -73,7 +74,7 @@ but below are the relevant bits. Note that `eksctl` "should" set up an OIDC prov --- -## Install Node Autoscaler +## Install Node Autoscaler To run the autoscaler on EKS, we need to create a policy and install Auto-Discovery Setup, which is the preferred method to configure [Cluster Autoscaler in EKS](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/aws/README.md#auto-discovery-setup). @@ -260,4 +261,4 @@ Assert that things are set up correctly: # pod/nginx-ingress-nginx-controller-76d7f6f4d5-g6fkv 1/1 Running 0 27h # service/nginx-ingress-nginx-controller LoadBalancer 10.100.36.152 eoapi-k8s-553d3ea234b-3eef2e6e61e5d161.elb.us-west-1.amazonaws.com 80:30342/TCP,443:30742/TCP 2d17h # service/nginx-ingress-nginx-controller-admission ClusterIP 10.100.34.22 443/TCP 2d17h - ``` \ No newline at end of file + ```