Skip to content

Commit e619a48

Browse files
authored
Merge pull request #3384 from M00nF1sh/main
update docs for v2.6.1 release
2 parents 71c45f5 + d8e3b59 commit e619a48

File tree

10 files changed

+24
-24
lines changed

10 files changed

+24
-24
lines changed

.ko.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
defaultBaseImage: public.ecr.aws/eks-distro-build-tooling/eks-distro-minimal-base-nonroot:2023-06-06-1686078098.2
1+
defaultBaseImage: public.ecr.aws/eks-distro-build-tooling/eks-distro-minimal-base-nonroot:2023-09-06-1694026927.2
22
builds:
33
- env:
44
- CGO_ENABLED=0

Makefile

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@
22
MAKEFILE_PATH = $(dir $(realpath -s $(firstword $(MAKEFILE_LIST))))
33

44
# Image URL to use all building/pushing image targets
5-
IMG ?= public.ecr.aws/eks/aws-load-balancer-controller:v2.6.0
5+
IMG ?= public.ecr.aws/eks/aws-load-balancer-controller:v2.6.1
66
# Image URL to use for builder stage in Docker build
7-
BUILD_IMAGE ?= public.ecr.aws/docker/library/golang:1.20.5
7+
BUILD_IMAGE ?= public.ecr.aws/docker/library/golang:1.20.8
88
# Image URL to use for base layer in Docker build
9-
BASE_IMAGE ?= public.ecr.aws/eks-distro-build-tooling/eks-distro-minimal-base-nonroot:2023-06-06-1686078098.2
9+
BASE_IMAGE ?= public.ecr.aws/eks-distro-build-tooling/eks-distro-minimal-base-nonroot:2023-09-06-1694026927.2
1010
IMG_PLATFORM ?= linux/amd64,linux/arm64
1111
# ECR doesn't appear to support SPDX SBOM
1212
IMG_SBOM ?= none

config/controller/kustomization.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,4 +9,4 @@ kind: Kustomization
99
images:
1010
- name: controller
1111
newName: public.ecr.aws/eks/aws-load-balancer-controller
12-
newTag: v2.6.0
12+
newTag: v2.6.1

docs/deploy/installation.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -87,15 +87,15 @@ Example condition for cluster name resource tag:
8787
2. Download an IAM policy for the LBC using one of the following commands:<p>
8888
If your cluster is in a US Gov Cloud region:
8989
```
90-
curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.0/docs/install/iam_policy_us-gov.json
90+
curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.1/docs/install/iam_policy_us-gov.json
9191
```
9292
If your cluster is in a China region:
9393
```
94-
curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.0/docs/install/iam_policy_cn.json
94+
curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.1/docs/install/iam_policy_cn.json
9595
```
9696
If your cluster is in any other region:
9797
```
98-
curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.0/docs/install/iam_policy.json
98+
curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.1/docs/install/iam_policy.json
9999
```
100100
101101
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.
@@ -121,7 +121,7 @@ Example condition for cluster name resource tag:
121121
### Option B: Attach IAM policies to nodes
122122
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.
123123
```
124-
curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.0/docs/install/iam_policy.json
124+
curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.1/docs/install/iam_policy.json
125125
```
126126
127127
The following IAM permissions subset is for those using `TargetGroupBinding` only and don't plan to use the LBC to manage security group rules:
@@ -204,7 +204,7 @@ We recommend using the Helm chart to install the controller. The chart supports
204204
### Apply YAML
205205
1. Download the spec for the LBC.
206206
```
207-
wget https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.6.0/v2_6_0_full.yaml
207+
wget https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.6.1/v2_6_1_full.yaml
208208
```
209209
2. Edit the saved yaml file, go to the Deployment spec, and set the controller `--cluster-name` arg value to your EKS cluster name
210210
```
@@ -228,15 +228,15 @@ We recommend using the Helm chart to install the controller. The chart supports
228228
```
229229
4. Apply the yaml file
230230
```
231-
kubectl apply -f v2_6_0_full.yaml
231+
kubectl apply -f v2_6_1_full.yaml
232232
```
233233
5. Optionally download the default ingressclass and ingressclass params
234234
```
235-
wget https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.6.0/v2_6_0_ingclass.yaml
235+
wget https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.6.1/v2_6_1_ingclass.yaml
236236
```
237237
6. Apply the ingressclass and params
238238
```
239-
kubectl apply -f v2_6_0_ingclass.yaml
239+
kubectl apply -f v2_6_1_ingclass.yaml
240240
```
241241
242242
## Create Update Strategy

docs/examples/echo_server.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -87,9 +87,9 @@ In this walkthrough, you'll
8787
1. Deploy all the echoserver resources (namespace, service, deployment)
8888

8989
```bash
90-
kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.0/docs/examples/echoservice/echoserver-namespace.yaml &&\
91-
kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.0/docs/examples/echoservice/echoserver-service.yaml &&\
92-
kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.0/docs/examples/echoservice/echoserver-deployment.yaml
90+
kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.1/docs/examples/echoservice/echoserver-namespace.yaml &&\
91+
kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.1/docs/examples/echoservice/echoserver-service.yaml &&\
92+
kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.1/docs/examples/echoservice/echoserver-deployment.yaml
9393
```
9494

9595
1. List all the resources to ensure they were created.
@@ -113,7 +113,7 @@ In this walkthrough, you'll
113113
1. Download the echoserver ingress manifest locally.
114114

115115
```bash
116-
wget https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.0/docs/examples/echoservice/echoserver-ingress.yaml
116+
wget https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.1/docs/examples/echoservice/echoserver-ingress.yaml
117117
```
118118

119119
1. Configure the subnets, either by add annotation to the ingress or add tags to subnets. This step is optional in lieu of auto-discovery.
@@ -300,7 +300,7 @@ You should get back a valid response.
300300
follow below steps if you want to use kube2iam to provide the AWS credentials
301301

302302
1. configure the proper policy
303-
The policy to be used can be fetched from https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.0/docs/install/iam_policy.json
303+
The policy to be used can be fetched from https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.1/docs/install/iam_policy.json
304304

305305
1. configure the proper role and create the trust relationship
306306
You have to find which role is associated with your K8S nodes. Once you found take note of the full arn:

helm/aws-load-balancer-controller/Chart.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
apiVersion: v2
22
name: aws-load-balancer-controller
33
description: AWS Load Balancer Controller Helm chart for Kubernetes
4-
version: 1.6.0
5-
appVersion: v2.6.0
4+
version: 1.6.1
5+
appVersion: v2.6.1
66
home: https://github.com/aws/eks-charts
77
icon: https://raw.githubusercontent.com/aws/eks-charts/master/docs/logo/aws.png
88
sources:

helm/aws-load-balancer-controller/test.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ replicaCount: 2
66

77
image:
88
repository: public.ecr.aws/eks/aws-load-balancer-controller
9-
tag: v2.6.0
9+
tag: v2.6.1
1010
pullPolicy: IfNotPresent
1111

1212
imagePullSecrets: []

helm/aws-load-balancer-controller/values.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ replicaCount: 2
66

77
image:
88
repository: public.ecr.aws/eks/aws-load-balancer-controller
9-
tag: v2.6.0
9+
tag: v2.6.1
1010
pullPolicy: IfNotPresent
1111

1212
imagePullSecrets: []

version-stable.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
2.6.0
1+
2.6.1

version.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
2.6.0
1+
2.6.1

0 commit comments

Comments
 (0)