All Products
Search

This Product

    Container Service for Kubernetes:ALB Ingress Controller component upgrade pre-check failures

    Document Center

    Container Service for Kubernetes:ALB Ingress Controller component upgrade pre-check failures

    Last Updated:Nov 20, 2025

    This topic describes error messages for pre-check failures that may occur when you upgrade the ALB Ingress Controller component and provides solutions.

    Contents

    Precautions

    Before the upgrade

    Note

    Before you upgrade the component, learn about its new features. For more information, see ALB Ingress Controller.

    1. Before the pre-check, run the kubectl get event command to check for reconciliation failures in the cluster. If any failures exist, resolve the issues and complete the reconciliation.

    2. Ensure that the configuration in the ALB console is consistent with the Albconfig configuration. If they are inconsistent, make them consistent before you upgrade. Before the pre-check, do not modify the configurations of ALB instances, listeners, forwarding rules, ACLs, or server groups in the ALB console. Otherwise, the configuration in the ALB console becomes inconsistent with the Albconfig or Ingress configuration, which causes the upgrade pre-check to fail.

      • If you want to use the configuration from the ALB console, modify the Albconfig or Ingress configuration to match the configuration in the ALB console.

      • If you want to use the Albconfig or Ingress configuration, run the kubectl edit command to modify a non-key field in the Albconfig or Ingress configuration file to trigger a reconciliation update. The configuration in the ALB console is then updated. Alternatively, you can directly modify the configuration in the ALB console to match the Albconfig or Ingress configuration. After you perform this operation, enable the configuration read-only mode for the ALB instance. For more information, see Enable or disable the configuration read-only mode.

    During the upgrade

    During the pre-check, do not modify the Albconfig or Ingress configuration to prevent incorrect results. If you make changes, rerun the pre-check.

    Error messages and solutions for ALB Ingress Controller upgrade precheck failures

    Note

    If the precheck fails, log on to the Container Service Management Console. Click Precheck and then View Details to view the Report and identify the cause of the failure.

    Error messages related to ALB instances

    Error message

    Cause

    Solutions

    Scenario 1: You have not modified the backend server configuration of the ALB instance in the ALB console

    Scenario 2: You have manually modified the backend server configuration of the ALB instance in the ALB console

    CreateALB

    The ALB instance configuration is inconsistent with the Albconfig configuration.

    Rerun the pre-check. Do not change the Albconfig during the upgrade pre-check.

    Make the ALB instance configuration consistent with the Albconfig configuration. Then, rerun the pre-check.

    ReuseALB

    UnReuseALB

    DeleteALB

    UpdateALBAttribute

    The attributes of the ALB instance, such as instance name and configuration read-only mode status, are inconsistent with the Albconfig settings.

    Rerun the pre-check. Do not change the Albconfig during the upgrade pre-check.

    Run the kubectl describe albconfig [$Albconfig_Name] command to compare the attribute configurations of the ALB instance and the Albconfig. In the console, restore the attribute configuration of the ALB instance to match the Albconfig. Then, rerun the pre-check.

    UpdateALBDeletionProtection

    The deletion protection status of the ALB instance is inconsistent with the Albconfig configuration.

    Rerun the pre-check. Do not change the Albconfig during the upgrade pre-check.

    Run the kubectl describe albconfig [$Albconfig_Name] command to check the deletion protection status in the Albconfig. In the ALB console, restore the deletion protection configuration of the ALB instance to match the Albconfig. Then, rerun the pre-check.

    UpdateALBAccessLog

    The access log configuration of the ALB instance is inconsistent with the Albconfig configuration.

    Rerun the pre-check. Do not change the Albconfig during the upgrade pre-check.

    Make the access log configuration of the ALB instance consistent with the Albconfig configuration. If you want to use the access log configuration from the ALB console, run the kubectl edit albconfig [$Albconfig_Name] command to update the access log configuration in the Albconfig. Then, rerun the pre-check.

    UpdateALBEdition

    The edition of the ALB instance (Standard or WAF-enabled) is inconsistent with the Albconfig configuration.

    Rerun the pre-check. Do not change the Albconfig during the upgrade pre-check.

    Make the edition of the ALB instance consistent with the Albconfig configuration. Then, rerun the pre-check.

    UpdateALBResourceGroup

    The resource group of the ALB instance is inconsistent with the Albconfig configuration.

    Rerun the pre-check. Do not change the Albconfig during the upgrade pre-check.

    Make the resource group of the ALB instance consistent with the Albconfig configuration. Then, rerun the pre-check.

    UpdateALBTag

    The tags of the ALB instance are inconsistent with the Albconfig configuration.

    Rerun the pre-check. Do not change the Albconfig during the upgrade pre-check.

    Make the tags of the ALB instance consistent with the Albconfig configuration. Then, rerun the pre-check.

    UpdateALBAddressType

    The network type of the ALB instance is inconsistent with the Albconfig configuration.

    Rerun the pre-check. Do not change the Albconfig during the upgrade pre-check.

    Make the network type of the ALB instance consistent with the network type in the Albconfig. If you want to use the network type from the ALB console, run the kubectl edit albconfig [$Albconfig_Name] command to modify the Albconfig. Then, rerun the pre-check.

    Important

    • Changing the network type from private to public involves changes to elastic IP addresses (EIPs) and incurs fees. Proceed with caution.

    • Changing the network type from public to private removes all EIPs and modifies the domain name resolution. Proceed with caution.

    UpdateALBBandWidthPackage

    The Internet Shared Bandwidth package of the ALB instance is inconsistent with the Albconfig configuration.

    Rerun the pre-check. Do not change the Albconfig during the upgrade pre-check.

    Make the Internet Shared Bandwidth package of the ALB instance consistent with the Albconfig configuration. If you want to use the Internet Shared Bandwidth package configuration from the ALB console, run the kubectl edit albconfig [$Albconfig_Name] command to modify the Albconfig. Then, rerun the pre-check.

    Error messages related to listeners

    Error message

    Cause

    Solutions

    Scenario 1: You have not modified the backend server configuration of the ALB instance in the ALB console

    Scenario 2: You have manually modified the backend server configuration of the ALB instance in the ALB console

    CreateALBListener

    The listener configuration of the ALB instance is inconsistent with the Albconfig.

    Rerun the pre-check. Do not modify the listener during the pre-check.

    • Add the deleted listener to the ALB instance. Then, rerun the pre-check.

    • If you want to use the listener configuration from the ALB instance, run the kubectl edit albconfig [$Albconfig_Name] command to delete the listener from the Albconfig. Then, rerun the pre-check.

    UpdateALBListenerExtraCertificates

    The additional certificate configuration for the listener is inconsistent between the ALB instance and the Albconfig.

    Rerun the pre-check. Do not modify the listener during the pre-check.

    Make the additional certificate configurations for the listener consistent between the ALB instance and the Albconfig. If you want to use the configuration from the ALB console, run the kubectl edit albconfig [$Albconfig_Name] command to modify the Albconfig. Then, rerun the pre-check.

    UpdateALBListenerAttribute

    The listener attribute configuration is inconsistent between the ALB instance and the Albconfig.

    Rerun the pre-check. Do not modify the listener during the pre-check.

    • Check for inconsistent listener attributes, such as certificates, compression algorithms, access control policies, idle connection timeout, and XForwardConfig.

    • If you want to use the listener configuration from the ALB instance, run the kubectl edit albconfig [$Albconfig_Name] command to modify the listener configuration in the Albconfig. Then, rerun the pre-check.

    DeleteALBListener

    The listener configuration is inconsistent between the ALB instance and the Albconfig.

    Rerun the pre-check. Do not modify the listener during the pre-check.

    • In the ALB console, delete the added listener. Then, rerun the pre-check.

    • If you want to use the listener configuration from the ALB instance, run the kubectl edit albconfig [$Albconfig_Name] command to add the listener to the Albconfig. Then, rerun the pre-check.

    Error messages related to network ACLs

    Error message

    Cause

    Solutions

    Case 1: You have not modified the backend server configuration of the ACL in the ALB console

    Case 2: You have manually modified the backend server configuration of the ACL in the ALB console

    CreateAcl

    The Access Control List (ACL) configuration is inconsistent with the access policy in the Albconfig.

    Run the precheck again. Do not modify the ACL during the upgrade check.

    Ensure the Albconfig and the ALB console have the same ACL configuration. To adopt the configuration from the console, run the kubectl edit albconfig [$Albconfig_Name] command to update the corresponding access control policy group in the Albconfig. Then, run the precheck again.

    DeleteAcl

    AddEntriesToAcl

    RemoveEntriesFromAcl

    AssociateAclWithListener

    DisassociateAclWithListener

    Error messages related to forwarding rules

    Error message

    Cause

    Solutions

    Scenario 1: You have not modified the backend server configuration of the ALB instance in the ALB console.

    Scenario 2: You have manually modified the backend server configuration of the ALB instance in the ALB console.

    CreateALBListenerRules

    The forwarding rules of the ALB instance are inconsistent with the Ingress configuration.

    Rerun the pre-check. Do not change the listener rules during the pre-check.

    Add the deleted forwarding rules, and then rerun the pre-check.

    UpdateALBListenerRules

    The forwarding rules of the ALB instance are inconsistent with the Ingress configuration.

    Rerun the pre-check. Do not change the listener rules during the pre-check.

    Ensure that the forwarding rules for the ALB instance and the Ingress match. If you want to use the rules from the ALB console, run the kubectl -n [$Namespace] edit ingress [$Ingress_Name] command to update the rules for the corresponding Ingress. Then, rerun the pre-check.

    DeleteALBListenerRules

    The forwarding rules of the ALB instance are inconsistent with the Ingress configuration.

    Rerun the pre-check. Do not change the listener rules during the pre-check.

    Delete the added forwarding rules, and then rerun the pre-check.

    Error messages related to server groups

    Error message

    Cause

    Solutions

    Scenario 1: You have not modified the backend server configuration of the ALB instance in the ALB console

    Scenario 2: You have manually modified the backend server configuration of the ALB instance in the ALB console

    CreateALBServerGroup

    The server group configuration of the ALB instance is inconsistent with the Ingress configuration.

    Rerun the pre-check. Do not modify the ServerGroup during the upgrade pre-check.

    Add the deleted server group. Then, rerun the pre-check.

    UpdateALBServerGroup

    The server group configuration of the ALB instance is inconsistent with the Ingress configuration.

    Rerun the pre-check. Do not modify the ServerGroup during the upgrade pre-check.

    Make the server group configurations for the ALB instance and the Ingress consistent. If you want to use the server group configuration from the ALB console, run the kubectl -n [$Namespace] edit ingress [$Ingress_Name] command to update the Ingress server group configuration. Then, rerun the pre-check.

    DeleteALBServerGroup

    The server group configuration of the ALB instance is inconsistent with the Ingress configuration.

    Rerun the pre-check. Do not modify the ServerGroup during the upgrade pre-check.

    Delete the added server group. Then, rerun the pre-check.

    Error messages related to backend servers

    Error message

    Cause

    Solution

    Case 1: The backend server configuration of the ALB instance was not modified in the ALB console.

    Case 2: The backend server configuration of the ALB instance was manually modified in the ALB console.

    RegisterALBServers

    The cluster and the ALB instance use different backend servers.

    Perform the precheck again. Do not modify the backend servers during the precheck.

    Restore the backend server configuration of the ALB instance to match the server nodes of the ACK or ACK Serverless cluster. Then, perform the precheck again.

    DeregisterALBServers

    ReplaceALBServers

    References