@@ -80,7 +80,7 @@ Example condition for cluster name resource tag:
80
80
81
81
1. Download IAM policy for the AWS Load Balancer Controller
82
82
```
83
- curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.4.2 /docs/install/iam_policy.json
83
+ curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.4.3 /docs/install/iam_policy.json
84
84
```
85
85
86
86
1. Create an IAM policy called AWSLoadBalancerControllerIAMPolicy
@@ -106,7 +106,7 @@ Example condition for cluster name resource tag:
106
106
### Option B: Attach IAM Policies to Nodes
107
107
If not setting up IAM for ServiceAccount, apply the IAM policies from the following URL at minimum.
108
108
```
109
- curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.4.2 /docs/install/iam_policy.json
109
+ curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.4.3 /docs/install/iam_policy.json
110
110
```
111
111
112
112
*IAM permission subset for those who use *TargetGroupBinding* only and don't plan to use the AWS Load Balancer Controller to manage security group rules:*
@@ -160,7 +160,6 @@ We recommend using the Helm chart. This supports Fargate and facilitates updatin
160
160
helm repo add eks https://aws.github.io/eks-charts
161
161
```
162
162
1. Install the TargetGroupBinding CRDs if upgrading the chart via `helm upgrade`.
163
-
164
163
```
165
164
kubectl apply -k "github.com/aws/eks-charts/stable/aws-load-balancer-controller//crds?ref=master"
166
165
```
@@ -169,12 +168,12 @@ We recommend using the Helm chart. This supports Fargate and facilitates updatin
169
168
The `helm install` command automatically applies the CRDs, but `helm upgrade` doesn't.
170
169
171
170
172
- Helm command for clusters with IRSA:
171
+ Helm install command for clusters with IRSA:
173
172
```
174
173
helm install aws-load-balancer-controller eks/aws-load-balancer-controller -n kube-system --set clusterName=<cluster-name> --set serviceAccount.create=false --set serviceAccount.name=aws-load-balancer-controller
175
174
```
176
175
177
- Helm command for clusters not using IRSA:
176
+ Helm install command for clusters not using IRSA:
178
177
```
179
178
helm install aws-load-balancer-controller eks/aws-load-balancer-controller -n kube-system --set clusterName=<cluster-name>
180
179
```
@@ -191,7 +190,7 @@ We recommend using the Helm chart. This supports Fargate and facilitates updatin
191
190
### Apply YAML
192
191
1. Download spec for load balancer controller.
193
192
```
194
- wget https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.4.2/v2_4_1_full .yaml
193
+ wget https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.4.3/v2_4_3_full .yaml
195
194
```
196
195
1. Edit the saved yaml file, go to the Deployment spec, and set the controller --cluster-name arg value to your EKS cluster name
197
196
```
@@ -215,7 +214,15 @@ We recommend using the Helm chart. This supports Fargate and facilitates updatin
215
214
```
216
215
1. Apply the yaml file
217
216
```
218
- kubectl apply -f v2_4_1_full.yaml
217
+ kubectl apply -f v2_4_3_full.yaml
218
+ ```
219
+ 1. Optionally download the default ingressclass and ingressclass params
220
+ ```
221
+ wget https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.4.3/v2_4_3_ingclass.yaml
222
+ ```
223
+ 1. Apply the ingressclass and params
224
+ ```
225
+ kubectl apply -f v2_4_3_ingclass.yaml
219
226
```
220
227
221
228
## Create Update Strategy
0 commit comments