Causes of ALB Ingress controller component update precheck failures-Container Compute Service(ACS)-阿里云帮助中心

This topic describes error messages for precheck failures during an ALB Ingress controller component update and explains how to resolve them.

Before you begin

Before the component update

Note

Before updating the component, review its new features. For more information, see ALB Ingress controller.

Before you run the precheck, run the kubectl get event command to check for any reconciliation failure events in the cluster. If any such events exist, resolve the failures to ensure a successful reconciliation. If you cannot identify the cause of the reconciliation failure, submit a ticket to contact technical support.
Ensure that the configurations on the ALB console are consistent with your AlbConfig and Ingress resources. If a discrepancy exists, you must align the configurations before you start the component update. Manually modifying resources such as Application Load Balancer (ALB) instances, listeners, forwarding rules, network ACLs, or server groups on the ALB console before the precheck causes configuration drift between the console and your AlbConfig or Ingress resources, which results in a precheck failure.
- If the ALB console configuration is correct, modify your AlbConfig or Ingress resources to match it.
- If the AlbConfig or Ingress configuration is correct, trigger a reconciliation to update the ALB console. To do this, run the kubectl edit command and modify a non-critical field in the AlbConfig or Ingress manifest. Alternatively, you can directly modify the configuration on the ALB console to match your AlbConfig or Ingress. After doing so, you must enable the configuration read-only mode for the ALB instance. For more information, see Enable or disable the configuration read-only mode.

During the component update

During the precheck, do not modify your AlbConfig or Ingress resources. Modifications during this period can cause inaccurate precheck results. If you have made any changes, rerun the precheck. If the precheck fails repeatedly, submit a ticket for assistance.

Precheck errors and solutions

ALB instance-related errors

Error message	Cause	Solution
Error message	Cause	Scenario 1: No manual changes	Scenario 2: Manual changes
CreateALB	Configuration mismatch between the ALB instance and the AlbConfig resource.	Rerun the precheck. Do not modify the AlbConfig resource during the precheck.	Align the configuration of the ALB instance with the AlbConfig resource, then rerun the precheck.
ReuseALB
UnReuseALB
DeleteALB
UpdateALBAttribute	The attributes of the ALB instance, such as the instance name or configuration read-only mode, are inconsistent with the AlbConfig resource.	Rerun the precheck. Do not modify the AlbConfig resource during the precheck.	Run `kubectl describe albconfig [$Albconfig_Name]` to identify the attribute mismatch. On the ALB console, align the ALB instance attributes with the AlbConfig resource, then rerun the precheck.
UpdateALBDeletionProtection	The deletion protection configuration of the ALB instance is inconsistent with the AlbConfig resource.	Rerun the precheck. Do not modify the AlbConfig resource during the precheck.	Run `kubectl describe albconfig [$Albconfig_Name]` to check the deletion protection status. On the ALB console, align the deletion protection configuration with the AlbConfig resource, then rerun the precheck.
UpdateALBAccessLog	The access log configuration of the ALB instance is inconsistent with the AlbConfig resource.	Rerun the precheck. Do not modify the AlbConfig resource during the precheck.	Ensure the access log configurations of the ALB instance and the AlbConfig resource are consistent. If the console's configuration is correct, run `kubectl edit albconfig [$Albconfig_Name]` to update the AlbConfig resource, then rerun the precheck.
UpdateALBEdition	The edition of the ALB instance (Standard or WAF Enabled) is inconsistent with the AlbConfig resource.	Rerun the precheck. Do not modify the AlbConfig resource during the precheck.	Align the edition of the ALB instance with the AlbConfig resource, then rerun the precheck.
UpdateALBResourceGroup	The resource group of the ALB instance is inconsistent with the AlbConfig resource.	Rerun the precheck. Do not modify the AlbConfig resource during the precheck.	Align the resource group of the ALB instance with the AlbConfig resource, then rerun the precheck.
UpdateALBTag	The tag configuration of the ALB instance is inconsistent with the AlbConfig resource.	Rerun the precheck. Do not modify the AlbConfig resource during the precheck.	Align the tag configuration of the ALB instance with the AlbConfig resource, then rerun the precheck.
UpdateALBAddressType	The network type of the ALB instance is inconsistent with the AlbConfig resource.	Rerun the precheck. Do not modify the AlbConfig resource during the precheck.	Align the network type of the ALB instance with the AlbConfig resource. If the console's network type is correct, run `kubectl edit albconfig [$Albconfig_Name]` to modify the AlbConfig resource, then rerun the precheck. Important Changing the network type from private network to public network involves changes to the elastic IP address and may incur fees. Proceed with caution. Changing the network type from public network to private network disassociates all elastic IP addresses and modifies domain name resolution. Proceed with caution.
UpdateALBBandWidthPackage	The shared bandwidth configuration of the ALB instance is inconsistent with the AlbConfig resource.	Rerun the precheck. Do not modify the AlbConfig resource during the precheck.	Align the shared bandwidth configuration of the ALB instance with the AlbConfig resource. If the console's configuration is correct, run `kubectl edit albconfig [$Albconfig_Name]` to modify the AlbConfig resource, then rerun the precheck.

Listener-related errors

Error message	Cause	Solution
Error message	Cause	Scenario 1: No manual changes	Scenario 2: Manual changes
CreateALBListener	The listener configuration of the ALB instance is inconsistent with the AlbConfig resource.	Rerun the precheck. Do not modify the listener during the precheck.	Restore the deleted listener to the ALB instance, then rerun the precheck. If the console's listener configuration is correct, run `kubectl edit albconfig [$Albconfig_Name]` to remove the corresponding listener from the AlbConfig resource, then rerun the precheck.
UpdateALBListenerExtraCertificates	The listener's additional certificate configuration is inconsistent between the ALB instance and the AlbConfig resource.	Rerun the precheck. Do not modify the listener during the precheck.	Align the additional certificate configuration for the listener in the ALB instance and the AlbConfig resource. If the console's configuration is correct, run `kubectl edit albconfig [$Albconfig_Name]` to modify the AlbConfig resource, then rerun the precheck.
UpdateALBListenerAttribute	The listener attributes are inconsistent between the ALB instance and the AlbConfig resource.	Rerun the precheck. Do not modify the listener during the precheck.	Identify the inconsistent listener attributes. These may include the certificate, compression algorithm, access control policy, idle timeout, or XForwardedForConfig. If the console's listener configuration is correct, run `kubectl edit albconfig [$Albconfig_Name]` to modify the listener configuration in the AlbConfig resource, then rerun the precheck.
DeleteALBListener	The listener configuration of the ALB instance is inconsistent with the AlbConfig resource.	Rerun the precheck. Do not modify the listener during the precheck.	On the ALB console, delete the listener that was manually added, then rerun the precheck. If the console's listener configuration is correct, run `kubectl edit albconfig [$Albconfig_Name]` to add the corresponding listener to the AlbConfig resource, then rerun the precheck.

Network ACL-related errors

Error message	Cause	Solution
		Scenario 1: No manual changes	Scenario 2: Manual changes
CreateAcl	The network ACL configuration is inconsistent with the access control policy defined in the AlbConfig resource.	Rerun the precheck. Do not modify the network ACL during the precheck.	Align the network ACL configuration on the ALB console with the AlbConfig resource. If the console's configuration is correct, run `kubectl edit albconfig [$Albconfig_Name]` to update the corresponding access control policy in the AlbConfig resource, then rerun the precheck.
DeleteAcl
AddEntriesToAcl
RemoveEntriesFromAcl
AssociateAclWithListener
DisassociateAclWithListener

Forwarding rule-related errors

Error message	Cause	Solution
Error message	Cause	Scenario 1: No manual changes	Scenario 2: Manual changes
CreateALBListenerRules	The forwarding rule configuration on the ALB instance is inconsistent with the Ingress resource.	Rerun the precheck. Do not modify the listener rules during the precheck.	Restore the deleted forwarding rule, then rerun the precheck.
UpdateALBListenerRules	The forwarding rule configuration on the ALB instance is inconsistent with the Ingress resource.	Rerun the precheck. Do not modify the listener rules during the precheck.	Align the forwarding rule configuration on the ALB instance with the Ingress resource. If the console's configuration is correct, run `kubectl -n [$Namespace] edit ingress [$Ingress_Name]` to update the corresponding Ingress resource, then rerun the precheck.
DeleteALBListenerRules	The forwarding rule configuration on the ALB instance is inconsistent with the Ingress resource.	Rerun the precheck. Do not modify the listener rules during the precheck.	Delete the manually added forwarding rule, then rerun the precheck.

Server group-related errors

Error message	Cause	Solution
Error message	Cause	Scenario 1: No manual changes	Scenario 2: Manual changes
CreateALBServerGroup	The server group configuration on the ALB instance is inconsistent with the Ingress resource.	Rerun the precheck. Do not modify the server group during the precheck.	Restore the deleted server group, then rerun the precheck.
UpdateALBServerGroup	The server group configuration on the ALB instance is inconsistent with the Ingress resource.	Rerun the precheck. Do not modify the server group during the precheck.	Align the server group configuration on the ALB instance with the Ingress resource. If the console's configuration is correct, run `kubectl -n [$Namespace] edit ingress [$Ingress_Name]` to update the server group configuration in the corresponding Ingress resource, then rerun the precheck.
DeleteALBServerGroup	The server group configuration on the ALB instance is inconsistent with the Ingress resource.	Rerun the precheck. Do not modify the server group during the precheck.	Delete the manually added server group, then rerun the precheck.

Backend server-related errors

Error message	Cause	Solution
		Scenario 1: No manual changes	Scenario 2: Manual changes
RegisterALBServers	The Endpoint configuration in the cluster is inconsistent with the backend server configuration on the ALB instance.	Rerun the precheck. Do not modify the backend servers during the precheck.	Align the backend server configuration on the ALB instance with the Endpoint configuration in the cluster, then rerun the precheck.
DeregisterALBServers
ReplaceALBServers