Alauda Container Platform

Installation Troubleshooting

Use this page when the installer does not progress, an installation resource fails, or post-install validation reports an image or artifact problem.

TOC

Common Stalls and Where to LookImage Pull and Artifact FailuresInstaller CleanupCollect Evidence Before Escalation

Common Stalls and Where to Look

Collect the signal in the second column before changing the environment or opening a support ticket.

SymptomFirst place to lookWhat you are looking for
Web UI does not loadTerminal output of setup.sh and nerdctl ps on the installation nodeThe minialauda-control-plane container is Running and port 8080 is reachable from the browser.
Installer log stops advancingtail -f /var/cpaas/data/installer.logThe last completed phase and the first repeated or failed operation.
Stuck on control plane provisioningkubectl get machines -A and kubectl describe on a machine that is not ReadyThe Bootstrap and Infrastructure conditions and the node address in status.addresses.
Stuck on network and Core add-onskubectl -n kube-system get pods on the new clusterKube-OVN, CoreDNS, and kube-proxy Pods are Running; image-pull failures usually identify a registry path problem.
AppRelease shows Failedkubectl describe apprelease <name> -n <namespace>Status conditions and recent Events that identify the chart or dependency failure.
ClusterModule/global does not become healthykubectl describe clustermodule globalThe status condition that identifies the blocking Core or Aligned module.

Image Pull and Artifact Failures

SymptomChecksRecovery
Pod is ImagePullBackOff or ErrImagePullRun kubectl describe pod <pod> -n <namespace> and test the configured registry from the failing node.Correct the reported DNS, route, firewall, CA trust, pull credential, registry availability, or missing-manifest problem.
A required Core or Aligned application is unavailable after installationInspect the corresponding AppRelease, ModuleInfo, ModulePlugin, and Pod Events. If package availability is still unclear, inspect the matching entry in kubectl get productbase base -o yaml and the exact repository:tag in the registry.If the registry confirms that the required manifest is missing, upload the matching installation-version package. For authorization, CA, DNS, routing, or connectivity errors, correct the reported registry problem instead of republishing the package. Ignore unrelated Absent entries for optional or uninstalled catalog packages.
A recovered or replacement node cannot pull an installed-version imageInspect the failing Pod and registry retention records.Restore the referenced digest, then correct registry availability, backup, or retention policy before retrying recovery.

For upload-command failures that occur before the installer starts, use External Platform Image Registry Troubleshooting.

Installer Cleanup

The installer normally removes itself after installation. If the installer container remains 30 minutes after installation completes, run this command on the installation node:

nerdctl rm -f minialauda-control-plane

Collect Evidence Before Escalation

Capture /var/cpaas/data/installer.log, the relevant kubectl describe output, failing resource conditions, and the exact Core Package version and architecture. Do not include registry passwords or Secret contents.