Container Compute Service:ALB Ingress Controller

July 2025

v2.18.0-aliyun.1 — July 4, 2025

Enhancements:

• Instance managed mode is now enabled by default. For ALB instances created via AlbConfig, listeners and forwarding rules cannot be manually modified in the ALB console. This applies only to new ALB instances created after upgrading to this version. Existing and reused instances are unaffected.

• Default certificates can now be specified in AlbConfig via the defaultCertificate field.

• The priority sorting logic for forwarding rules is optimized, and the global uniqueness constraint on order is removed.

• A fixed waiting interval is implemented during readinessGate checks for unready pods.

• Validation logic for forwarding actions without termination types in admission webhooks is optimized.

Fixes:

• Fixed a controller panic caused by flow control during asynchronous task queries.

• Fixed an access control list (ACL) effectiveness conflict when HTTPS and QUIC listeners shared ports.

March 2025

v2.17.2-aliyun.1 — March 31, 2025

Fixes:

• Fixed a "port not found" error during server group reconciliation, which occurred when Ingress rules across multiple namespaces referenced Services with identical names but different ports.

• Fixed incorrect parameter handling for IPv4 address queries in IPv4/IPv6 dual-stack cluster configurations.

Enhancements:

• The maximum number of security groups processed per batch API call for add or remove operations is increased from 4 to 9.

• API calls are now skipped when no new labels require configuration.

v2.17.1-aliyun.1 — March 18, 2025

Enhancements:

• Gateway API v1.1.0 and later are now supported.

v2.16.0-aliyun.1 — March 4, 2025

Enhancements:

• Persistent connections are enabled by default for new server groups.

• Custom labels for listeners are now supported.

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

• The overall tuning performance of Services is optimized.

• ReadinessGate now updates pod status after all server groups are updated.

• Canary release now requires two Ingresses or custom routing rules. Adding a canary annotation to an Ingress causes the system to report an error and retain the original forwarding rule.

January 2025

v2.15.2-aliyun.1 — January 24, 2025

Enhancements:

• XForwardedForProcessingMode can now be set to X-Forwarded-For, and the X-Forwarded-Host request header can be enabled via XForwardedForHostEnabled in the listener's XForwardedForConfig.

• FinalType checking in forwarding rule actions is now supported.

• clientToken calculation is optimized during ALB instance creation.

Fixes:

• Fixed a startup failure when ValidatingWebhookConfiguration does not exist.

• Fixed a webhook verification failure when multiple values are specified for alb.ingress.kubernetes.io/healthcheck-httpcode.

v2.15.0-aliyun.1 — January 6, 2025

Enhancements:

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

• AScript is now supported.

• Traffic throttling now supports fixed responses.

• ssl-redirect and traffic throttling can now be used together.

• Session persistence for backend server groups now supports custom cookies.

• Security groups can now be created for newly created ALB instances. This feature takes effect from 00:00:00 on February 25, 2025 (UTC+8).

• Alerts for listener conflicts are improved.

• Events are now generated when TLS certificate configuration is inconsistent with forwarding rules.

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

• Certificates can now be configured in AlbConfig for gRPC authentication.

Fixes:

• Fixed an issue where tags in AlbConfig could not be used after createdby tags were enabled.

• Fixed continuous Service reconciliation errors in certain scenarios.

• Fixed component crashes caused by AlbConfig configuration errors.

May 2024

v2.13.1-aliyun.1 — May 10, 2024

Enhancements:

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

Fixes:

• Fixed a server group creation failure when the namespace name starts with a number or when the namespace or Service name is excessively long.