1. Helm App Installed Successfully, but Why Can'T the Pod Pull the Image in the Workload?
Deploying Cloud Applications to regions such as Beijing, Shanghai, Guangzhou, Nanjing, and Chengdu allows container images to be pulled through the VPC. For other regions, the application repository is accessed via the public network. Therefore, the target VPC for software installation must have public network access capability. If the customer's VPC lacks a public egress IP address, you can guide them to temporarily add a NAT Gateway and the corresponding routing configuration as a solution. For specific operations, refer to the NAT Gateway documentation. 2. Workloads Are Up, but Why Does the Helm Application Prompt an Installation Failure?
If there is a post_install script, it might be that the script has timed out. Please check whether there are processes that have not exited in the post_install job.
3. the Image Architecture Is Inconsistent with the Node Cvm Architecture, Causing a Startup Failure. the Error Information Is "Exec User Process Caused: Exec Format Error". How to Handle?
When building an image, select a platform. If it is TKE, generally select `linux/amd64`. For details, see Documentation. 4. Installation Failure Due to Insufficient Resource Inventory. How to Resolve?