Skip to content

Releases: kubernetes-sigs/aws-load-balancer-controller

v2.0.0-rc4

16 Oct 22:38
21418f4

Choose a tag to compare

v2.0.0-rc4 Pre-release
Pre-release

Warning: This is not a production release, please don't use it in production !

  1. The purpose of this release is to gather early feedbacks about the APIs and usage.
  2. If you have find issues or feedbacks, please create an issue with [V2] in title.
  3. It's backwards compatible with aws-alb-ingress-controller:v1.1.3+.

Documentation

Image: docker.io/amazon/aws-alb-ingress-controller:v2.0.0-rc4

Action Required

N/A

Install Instructions:

Install CertManager

we now have a pod webhook to automatically inject pod readinessGates, we'll offer a option to install without CertManager in our helm charts

  • For Kubernetes 1.16+: kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.0.2/cert-manager.yaml
  • For Kubernetes <1.16: kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.0.2/cert-manager-legacy.yaml

Install the Controller

  1. change your-cluster-name to be real clusterName in https://github.com/kubernetes-sigs/aws-alb-ingress-controller/blob/v2.0.0/config/samples/install_v2_0_0_rc4.yaml#L500
  2. apply the yaml

Changelog since v2.0.0-rc3

  1. Handle TargetGroupBinding's networking changed from non-nil to nil (#1510, @M00nF1sh )
  2. Fix addons_config default values (#1497, @kishorj )
  3. Fix NLB model for supporting multiple certificate ARNs (#1503, @kishorj )
  4. Respect region settings when get SDK credentials with IAMForSA support (#1508, @M00nF1sh )
  5. Make annotation based forward action backwards-compatible when numeric port is used (#1507, @M00nF1sh )
  6. Multiple bug fixes (#1504, @M00nF1sh )
  7. Add support for specifying source ranges for NLB (#1492, @kishorj )
  8. Echo controller version at startup and remove --master flag (#1506, @M00nF1sh )
  9. Add default AWS API throttle config for WAF/WAFv2 (#1505 , @M00nF1sh )
  10. Added installation and configuration docs(#1509, @kishorj )
  11. Fix IAM permissions template (#1498, @M00nF1sh )

v2.0.0-rc3

13 Oct 01:40
e2e2f13

Choose a tag to compare

v2.0.0-rc3 Pre-release
Pre-release

Warning: This is not a production release, please don't use it in production !

  1. The purpose of this release is to gather early feedbacks about the APIs and usage.
  2. If you have find issues or feedbacks, please create an issue with [V2] in title.
  3. It's backwards compatible with aws-alb-ingress-controller:v1.1.3+.

Documentation

Image: docker.io/amazon/aws-alb-ingress-controller:v2.0.0-rc3

Action Required(for v2.0.0-rc1/v2.0.0-rc2 users)

  1. The TargetGroupBinding CRDs are updated from v1alpha1 to v1beta1, which should be updated via the YAML manifest.
  2. If upgrading to this version without removing old resources, the finalizers on resources(Ingress/Service/TargetGroupBindings) should be manually removed. (one-time task)
  3. --ingress-class=alb should be specified as controller args, if not specified, the controller will look for Ingresses without IngressClass annotation or IngressClass==alb.
  4. the required IAM policy have been updated.

Install Instructions:

Install CertManager

we now have a pod webhook to automatically inject pod readinessGates, we'll offer a option to install without CertManager in our helm charts

  • For Kubernetes 1.16+: kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.0.2/cert-manager.yaml
  • For Kubernetes <1.16: kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.0.2/cert-manager-legacy.yaml

Install the Controller

  1. change your-cluster-name to be real clusterName in https://github.com/kubernetes-sigs/aws-alb-ingress-controller/blob/v2.0.0/config/samples/install_v2_0_0_rc3.yaml#L500
  2. apply the yaml

Changelog since v2.0.0-rc2

  1. finalize all user-facing elements(finalizer/tagging/labeling) (#1469, @M00nF1sh )
  2. TargetGroupBinding is prompted to v1beta1 from v1alpha1 (#1478, @M00nF1sh )
  3. Multiple bug fixes around Ingress rules (#1484, @M00nF1sh )
  4. Added secret/service event handler for Ingress updates. (#1471, @M00nF1sh )
  5. Added featureGates and command line flags ([#1479](#1479, @kishorj )
  6. retry listener-rule creation (#1472, @M00nF1sh )
  7. enable leader-election by default(#1462, @kishorj )

v2.0.0-rc2

30 Sep 23:13
520ab09

Choose a tag to compare

v2.0.0-rc2 Pre-release
Pre-release

Warning: This is not a production release, please don't use it in production !

  1. The purpose of this release is to gather early feedbacks about the APIs and usage.
  2. If you have find issues or feedbacks, please create an issue with [V2] in title.
  3. It's backwards compatible with aws-alb-ingress-controller:v1.1.3+.

Documentation (detailed documentation about new features coming soon)

Image: docker.io/amazon/aws-alb-ingress-controller:v2.0.0-rc2

Install Instructions:

Install CertManager

we now have a pod webhook to automatically inject pod readinessGates, we'll offer a option to install without CertManager in our helm charts

  • For Kubernetes 1.16+: kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.0.2/cert-manager.yaml
  • For Kubernetes <1.16: kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.0.2/cert-manager-legacy.yaml

Install the Controller

  1. change your-cluster-name to be real clusterName in https://github.com/kubernetes-sigs/aws-alb-ingress-controller/blob/v2.0.0/config/samples/install_v2_0_0_rc2.yaml#L485
  2. apply the yaml

Changelog since v2.0.0-rc1

  1. added auto ACM certificate discovery for Ingress hosts.(#1458)
  2. added mutating/validating webhook for TargetGroupBinding CRD(#1450)
  3. Fix two bug during securityGroup reconcile(#1459)
    • IPv6 CIDR is incorrectly handled in model deployer.
    • added retry without cache if securityGroup cache is out-dated.
  4. make container run as non-root and redact OIDC info in logs(#1451)
  5. we now offer a more restricted IAM permission: https://github.com/kubernetes-sigs/aws-alb-ingress-controller/blob/v2_ga/docs/install/iam_policy.json

v2.0.0-rc1

25 Sep 19:29
6521c59

Choose a tag to compare

v2.0.0-rc1 Pre-release
Pre-release

Warning: This is not a production release, please don't use it in production !

  1. The purpose of this release is to gather early feedbacks about the APIs and usage.
  2. If you have find issues or feedbacks, please create an issue with [V2] in title.
  3. It's backwards compatible with aws-alb-ingress-controller:v1.1.3+.

Documentation (detailed documentation about new features coming soon)

Image: docker.io/amazon/aws-alb-ingress-controller:v2.0.0-rc1

Install Instructions:

Install CertManager

we now have a pod webhook to automatically inject pod readinessGates, we'll offer a option to install without CertManager in our helm charts

  • For Kubernetes 1.16+: kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.0.2/cert-manager.yaml
  • For Kubernetes <1.16: kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.0.2/cert-manager-legacy.yaml

Install the Controller

  1. change your-cluster-name to be real clusterName in https://github.com/kubernetes-sigs/aws-alb-ingress-controller/blob/v2.0.0/config/samples/install_v2_0_0_rc1.yaml#L452
  2. apply the yaml

Changelog since v2.0.0-rc0

  1. Fixed several bugs around SecurityGroup handling.
  2. Added support for WAFRegional/WAFV2/Shield
  3. Added a webhook to automatically inject Pod readinessGate

v2.0.0-rc0

16 Sep 09:04
27779b4

Choose a tag to compare

v2.0.0-rc0 Pre-release
Pre-release

Warning: This is not a production release, please don't use it in production !

  1. The purpose of this release is to gather early feedbacks about the APIs and usage.
  2. If you have find issues or feedbacks, please create an issue with [V2] in title.
  3. It's backwards compatible with aws-alb-ingress-controller:v1.1.3+.

Documentation (detailed documentation about new features coming soon)

Image: docker.io/amazon/aws-alb-ingress-controller:v2.0.0-rc0

Install Instructions:

  1. change your-cluster-name to be real clusterName in https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v2.0.0/config/samples/install_v2_0_0_rc0.yaml
  2. apply the yaml

Features:

  1. all existing annotations(in v1) except below are supported(coming soon):
    • alb.ingress.kubernetes.io/waf-acl-id
    • alb.ingress.kubernetes.io/wafv2-acl-arn
    • alb.ingress.kubernetes.io/shield-advanced-protection
  2. ingress groups feature described in #914
    • alb.ingress.kubernetes.io/group.name
    • alb.ingress.kubernetes.io/group.order
  3. A new controller for Kubernetes Service which will provision NLBs in IP targeting mode.
    • create a normal NodePort Service. (we'll support you use a LoadBalancer type soon)
    • add annotation to your service service.beta.kubernetes.io/aws-load-balancer-type: nlb-ip
    • all other NLB related annotations in current kubernetes NLB support
  4. A new alpha CRD called TargetGroupBinding to allow you register/deregister targets from TargetGroups.

v1.1.9

22 Aug 05:25
6c19d2f

Choose a tag to compare

Documentation
Image: docker.io/amazon/aws-alb-ingress-controller:v1.1.8

Note

  • This version is the first multi-arch image, supported platforms:
    • linux/amd64
    • linux/arm64
  • This version have no code change compare with v1.1.8. (only change is recompiled with golang v1.15)

Changelog since v1.1.8

Action Required:

N/A

Other notable changes

v1.1.8

06 Jun 03:14
d8fe029

Choose a tag to compare

Documentation
Image: docker.io/amazon/aws-alb-ingress-controller:v1.1.8

Changelog since v1.1.7

Action Required:

N/A

Other notable changes

v1.1.7

18 Apr 04:18
8694851

Choose a tag to compare

Documentation
Image: docker.io/amazon/aws-alb-ingress-controller:v1.1.7

Changelog since v1.1.6

Action Required:

  • This version of controller needs new IAM permissions
    Note:
    • New IAM permission is required even no wafv2 annotation is used
    • WAFV2 support can be disabled by controller flags--feature-gates=wafv2=false

New Features

Other notable changes

v1.1.6

23 Mar 07:34
95ee2ac

Choose a tag to compare

Documentation
Image: docker.io/amazon/aws-alb-ingress-controller:v1.1.6

Changelog since v1.1.5

Action Required:

  • This version of controller needs new IAM permissions (Note: only needed when shield related annotation is used)

New Features

Other notable changes

v1.1.5

14 Jan 11:33
2560c81

Choose a tag to compare

Documentation
Image: docker.io/amazon/aws-alb-ingress-controller:v1.1.5

Changelog since v1.1.4

New Features

32587b3 advanced_routing/weighted_routing support

Other notable changes

25b9705 Rewrite GetClusterSubnets() using EC2 specific API (This enables the controller to run in pure-private VPC with privateLink. Note: this is not complete, there is still a dependency on RGT, so clean up in PurePrivate VPC don't work)
b58bba7 ignore fargate nodes for instance type (This allows instance target-type when both EC2 node and fargate node presents)
3226ff2 adding cache around wafAPI usage (This fix WAF throttling issues when there are frequently pod/node changes)
acdc3b2 docs(echoserver.md): fix typos
27884d4 docs: update example for ExternalDNS