ALB Ingress controller

Version number

Release date

Description

Impact

v2.17.1-aliyun.1

2025-03-18

Gateway API v1.1.0 and later are supported.

No impact on workloads.

v2.16.0-aliyun.1

2025-03-04

• By default, persistent connections are enabled for new server groups.

• Custom labels for listeners are supported.

• The cross-zone capability for server groups can be disabled.

• The overall tuning performance of Services is optimized.

• The time when the ReadinessGate feature updates the status of pods is optimized. ReadinessGate updates the status of pods after all server groups are updated.

• In canary release, you must configure two Ingresses or use custom routing rules. If you add a canary annotation to an Ingress, the system reports an error and retains the original forwarding rule.

No impact on workloads.

Version number

Release date

Description

Impact

v2.15.2-aliyun.1

2025-01-24

• XForwardedForProcessingMode can be set to X-Forwarded-For and the X-Forwarded-Host request header can be enabled in XForwardedForHostEnabled in the XForwardedForConfig of a listener.

• The issue that the ALB Ingress controller fails to start up when the ValidatingWebhookConfiguration does not exist is fixed.

• The issue that webhook verification fails when multiple values are specified for alb.ingress.kubernetes.io/healthcheck-httpcode is fixed.

• Check for FinalType in the actions of forwarding rules is supported.

• The calculation of clientToken is optimized during the creation of an ALB instance.

No impact on workloads.

v2.15.0-aliyun.1

2025-01-06

• ValidatingWebhook is enabled by default to precheck the AlbConfig and Ingresses.

• AScript is supported.

• Fixed responses are supported by traffic throttling.

• ssl-redirect and traffic throttling can be used at the same time.

• Custom cookies are supported by session persistence for backend server groups.

• Security groups can be configured on ALB instances created after 00:00:00 (UTC+8) on February 25, 2025.

• Alerts that indicate listener conflicts are optimized.

• Events are generated when the TLS certification configuration is inconsistent with the forwarding rules.

• The validity of associated resources, such as bandwidth plans, can be checked.

• Certificates can be configured in AlbConfigs for gRPC authentication.

• The issue that tags in AlbConfigs cannot be used after createdby tags are enabled is fixed.

• The issue that Service reconciliation continuously throws errors in specific scenarios is fixed.

• Component crashes caused by AlbConfig configuration errors are fixed.

No impact on workloads.

Version number

Release date

Description

Impact

v2.14.1-aliyun.1

2024-10-12

• The issue that occurs when HTTPS health check is enabled is fixed.

No impact on workloads.

Version number

Release date

Description

Impact

v2.14.0-aliyun.1

2024-09-10

• The Google Remote Procedure Call (gRPC) protocol is supported for health checks in server groups.

• Slow start is supported.

• Connection draining is supported.

• Session persistence between server groups is supported.

• The issue that the status of ReadinessGate cannot be updated correctly in certain scenarios is fixed.

• Error messages for Secrets are optimized.

• The reconciliation logic for the Configuring state in server groups is optimized.

• AlbConfig fields are case-insensitive.

No impact on workloads.

Version number

Release date

Description

Impact

v2.13.2-aliyun.1

2024-07-23

• The issue that the ALB Ingress controller may crash due to an invalid AlbConfig format is fixed.

• The issue that weights may be incorrectly specified when the cluster uses Elastic Compute Service (ECS) instances and elastic container instances is fixed for the Flannel network plug-in.

No impact on workloads.

Version number

Release date

Description

Impact

v2.13.1-aliyun.1

2024-05-10

• A new event is supported. The event is generated when an AlbConfig is not associated with an Ingress.

• The issue that weights may be incorrectly specified after endpoint updates is fixed for the Flannel network plug-in.

• The issue that server group creation fails when the namespace name starts with a number or when the namespace or Service name is excessively long is fixed.

No impact on workloads.

Version number

Release date

Description

Impact

v2.12.0-aliyun.1

2024-02-05

• The alb.ingress.kubernetes.io/server-group-type: Ip annotation can be used to specify IP type server groups.

• The alb.ingress.kubernetes.io/server-group-resource-group-id annotation can be used to specify the resource group used by a server group.

• The Flannel plug-in can automatically specify the weight of a node based on the number of pods on the node.

• Queries per second (QPS) throttling is supported by custom forwarding rules.

• ALB instances can be created without specifying an IP address allocation mode (addressAllocateMode).

• Trusted IP addresses can be configured for the X-Forwarded-For request header.

• The issue that specific fields in an AlbConfig do not take effect after their values change from NULL to false is fixed.

No impact on workloads.

Version number

Release date

Description

Impact

v2.11.1-aliyun.1

2023-11-20

The issue that the ALB Ingress controller may crash when no IngressClass is specified is fixed.

No impact on workloads.

Version number

Release date

Description

Impact

v2.11.0-aliyun.1

2023-10-31

• Rate limiting for source IP addresses is supported.

• Managed Service for OpenTelemetry is supported.

• Custom headers are supported by access logs.

• Mutual authentication is supported.

• The AlbConfig is no longer automatically updated when Ingress rules are updated.

• You cannot remove listeners that are configured with Ingress rules from the AlbConfig.

• Resource deletion is optimized in scenarios in which the ALB instance is reused.

• The certificate association logic is optimized and multiple certificates are supported.

• The error that occurs when you enable HTTP/2 is fixed.

• The issue that the ALB Ingress controller may crash when forwarding actions are not properly configured is fixed.

• The issue that backend server groups may not be updated promptly when the ALB Ingress controller restarts is fixed.

No impact on workloads.

Version number

Release date

Description

Impact

v2.10.0-aliyun.1

2023-08-15

• Hash values can be added to Ingresses and the AlbConfig to prevent unexpected changes when the ALB Ingress controller restarts.

• The exposure of abnormal events is optimized.

• The reconciliation process is optimized for scenarios in which reserved fields are used.

• The issue that the cache is not synchronized after Ingress resources are deleted is fixed.

• The issue that node event handling is interrupted is fixed.

• The synchronization logic of server groups is optimized.

No impact on workloads.

Version number

Release date

Description

Impact

v2.9.0-aliyun.1

2023-07-11

• API throttling can be avoided when multiple server groups are reconciled with a Service.

• Service reconciliation events are exposed.

• The use of the ssl-redirect annotation is optimized.

• ShangMi (SM) certificates can be automatically discovered and filtered.

• The issue related to the reconciliation of CookieConfig in custom forwarding rules is fixed.

• The issue that the ALB Ingress controller crashes if the http field of an Ingress is not configured is fixed.

• The issue that configuration updates fail if multiple actions are specified in the Ingress configuration is fixed.

No impact on workloads.

Version number

Release date

Description

Impact

v2.8.3-aliyun.1

2023-06-05

• The issue that server reconciliations are not retried is fixed.

• The issue that keys in custom forwarding rules do not take effect is fixed.

No impact on workloads.

Version number

Release date

Description

Impact

v2.8.2-aliyun.1

2023-05-25

• The issue that forwarding rules may be deleted when the pods of the component are restarted is fixed.

• Internet Shared Bandwidth instances are no longer deleted during the reconciliation process.

• The network type of the ALB instance used by the component cannot be changed. This is a temporary change.

No impact on workloads.

v2.8.1-aliyun.1

2023-05-09

• By default, the managed ALB Ingress controller is deployed in multiple replicated pods to ensure high availability.

• Resource groups can be specified when you create ALB instances.

• Multiple status codes are supported by health checks.

• Consistent hashing is supported for distributing traffic to backend server groups.

• The use-regex annotation is supported.

• The ALB Ingress controller can be deployed in a single zone.

• The network types of ALB instances can be changed.

• Internet Shared Bandwidth instances can be associated with ALB instances.

• Asynchronous API operations are optimized.

• Error messages are optimized.

• The issue that the default certificates displayed in the console are different from the actual default certificates used by ALB instances and the issue that the default certificates used by ALB instances are repeatedly specified are fixed.

No impact on workloads.

Version number

Release date

Description

Impact

v2.7.0-aliyun.1

2023-03-14

• The reconciliation process and rule priorities are optimized to accelerate rule synchronization.

• Event notifications are optimized.

• Services can be reconciled with backend server groups.

• Network access control lists (ACLs) can be associated with ALB instances by specifying the IDs of the network ACLs.

• HTTPS and QUIC services can be deployed on the same port.

• Multiple server groups, rewrites, and uppercase and lowercase letters are supported by custom actions.

• Certificates that are configured by using Secrets have higher priorities than AlbConfigs.

• Hard-coded timeout values are removed.

• Configuration errors of Gzip compression are fixed.

No impact on workloads.

Version number

Release date

Description

Impact

v2.6.0-aliyun.1

2022-12-23

• Custom tags can be added to ALB instances.

• Event notifications are optimized.

• The issue that Ingresses are stuck when they are deleted is fixed. No finalizers are configured for Ingress deletions.

• Issues that occur when you switch the network type of an ALB instance to IPv6 are fixed.

• The issue that Ingress certificates are repeatedly discovered is fixed.

• The issue that the tags of backend server groups become invalid during canary releases is fixed.

No impact on workloads.

Version number

Release date

Description

Impact

v2.5.0-aliyun.1

2022-11-23

• Secret certificates can be uploaded.

• Custom headers and cookies are supported.

• Network ACLs can be configured as whitelists.

• The processing logic of listeners is optimized. Errors on listening port 443 do not affect reconciliations of port 80.

No impact on workloads.

Version number

Release date

Description

Impact

v2.4.0-aliyun.1

2022-08-10

• Cross-origin resource sharing (CORS) is supported.

• Persistent connections to backend servers are supported.

• The processing logic of listener deletion is optimized.

No impact on workloads.

Version number

Release date

Description

Impact

v2.3.0-aliyun.1

2022-06-23

• Annotations that are used to replace the load balancing algorithms of backend server groups are supported. For more information, see Configure the load balancing algorithms of backend server groups.

• Issues related to listening protocols are fixed.

No impact on workloads.

Version number

Release date

Description

Impact

v2.2.0-aliyun.1

2022-04-13

• Rewrite rules are supported. Annotations to configure rewrite rules are supported. For more information, see Configure rewrite rules.

• TCP can be specified as the health check protocol. The ALB instance sends TCP SYN packets to a backend server to check whether the port of the backend server is available to receive requests. For more information, see Configure health checks.

• TLS security policies are supported. When you use an AlbConfig object to configure an HTTPS listener, you can specify a TLS security policy. For more information, see Customize TLS security policies.

No impact on workloads.