Skip to content

update doc for 2.5 #3154

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 14, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 9 additions & 8 deletions docs/deploy/installation.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,7 @@ The LBC is supported by AWS. Some clusters may be using the legacy "in-tree" fun
* AWS Load Balancer Controller v2.0.0~v2.1.3 requires Kubernetes 1.15+
* AWS Load Balancer Controller v2.2.0~v2.3.1 requires Kubernetes 1.16-1.21
* AWS Load Balancer Controller v2.4.0+ requires Kubernetes 1.19+
* AWS Load Balancer Controller v2.5.0+ requires Kubernetes 1.22+

## Deployment considerations

Expand Down Expand Up @@ -81,15 +82,15 @@ Example condition for cluster name resource tag:
2. Download an IAM policy for the LBC using one of the following commands:<p>
If your cluster is in a US Gov Cloud region:
```
curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.4.7/docs/install/iam_policy_us-gov.json
curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.5.0/docs/install/iam_policy_us-gov.json
```
If your cluster is in a China region:
```
curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.4.7/docs/install/iam_policy_cn.json
curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.5.0/docs/install/iam_policy_cn.json
```
If your cluster is in any other region:
```
curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.4.7/docs/install/iam_policy.json
curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.5.0/docs/install/iam_policy.json
```

3. Create an IAM policy named `AWSLoadBalancerControllerIAMPolicy`. If you downloaded a different policy, replace `iam-policy` with the name of the policy that you downloaded.
Expand All @@ -115,7 +116,7 @@ Example condition for cluster name resource tag:
### Option B: Attach IAM policies to nodes
If you're not setting up IAM roles for service accounts, apply the IAM policies from the following URL at a minimum. Please be aware of the possibility that the controller permissions may be assumed by other users in a pod after retrieving the node role credentials, so the best practice would be using IRSA instead of attaching IAM policy directly.
```
curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.4.7/docs/install/iam_policy.json
curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.5.0/docs/install/iam_policy.json
```

The following IAM permissions subset is for those using `TargetGroupBinding` only and don't plan to use the LBC to manage security group rules:
Expand Down Expand Up @@ -198,7 +199,7 @@ We recommend using the Helm chart to install the controller. The chart supports
### Apply YAML
1. Download the spec for the LBC.
```
wget https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.4.7/v2_4_7_full.yaml
wget https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.5.0/v2_5_0_full.yaml
```
2. Edit the saved yaml file, go to the Deployment spec, and set the controller `--cluster-name` arg value to your EKS cluster name
```
Expand All @@ -222,15 +223,15 @@ We recommend using the Helm chart to install the controller. The chart supports
```
4. Apply the yaml file
```
kubectl apply -f v2_4_7_full.yaml
kubectl apply -f v2_5_0_full.yaml
```
5. Optionally download the default ingressclass and ingressclass params
```
wget https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.4.7/v2_4_7_ingclass.yaml
wget https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.5.0/v2_5_0_ingclass.yaml
```
6. Apply the ingressclass and params
```
kubectl apply -f v2_4_7_ingclass.yaml
kubectl apply -f v2_5_0_ingclass.yaml
```

## Create Update Strategy
Expand Down
2 changes: 1 addition & 1 deletion docs/deploy/upgrade/migrate_v1_v2.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ foo@bar:~$ kubectl describe deployment -n kube-system alb-ingress-controller |
Existing Ingress resources do not need to be deleted.

3. Install new AWSLoadBalancerController
1. Install AWSLoadBalancerController(v2.4.1) by following the [installation instructions](../installation.md)
1. Install AWSLoadBalancerController(v2.5.0) by following the [installation instructions](../installation.md)
2. Grant [additional IAM policy](../../install/iam_policy_v1_to_v2_additional.json) needed for migration to the controller.

4. Verify all Ingresses works as expected.