Create a Cluster on Huawei DCS
ACP CLI (ac) renders the Cluster API and DCS objects from one install-config.yaml, applies them to the global cluster, and reports the creation stages. Every object lives in the cpaas-system namespace of the global cluster.
TOC
PrerequisitesProcedure1. Writeinstall-config.yaml2. Create the Cluster3. Monitor the Creation4. Verify the ClusterSelf-built VIPControl Plane HAAdditional NICsRun create AgainNext StepsPrerequisites
- You meet the Huawei DCS prerequisites.
acis logged in to the platform as a platform administrator (ac login https://<platform-address> --name <session-name>).
Procedure
1. Write install-config.yaml
Create an installation directory for the cluster and write install-config.yaml in it. ac writes manifests/ and logs/ac.log next to it. From that file, ac renders one DCSIpHostnamePool and one DCSMachineTemplate for each node group. You therefore do not create IP pools or machine templates.
Copy the following template and fill in the placeholders. The table below the template describes the numbered lines, which are specific to Huawei DCS. For the other fields, see Common install-config.yaml Fields. For the objects that ac renders from this file, see Parameters.
2. Create the Cluster
Before you run create, make sure that the password in the credential Secret is correct, because DCS locks the account after repeated failed sign-ins.
Run the following command from a machine where ac is logged in to the platform:
ac first checks the credential Secret, the DCS objects named in install-config.yaml, the ConfigMap of the VM template, and the registry. If a check fails, nothing is changed and the error names the item.
create returns once the objects are applied, and the cluster keeps building. To wait until all stages are ready, add --wait. --timeout (default 2h) limits only the wait. To render without applying, run ac adm alpha cluster manifests with the same flags.
3. Monitor the Creation
Continue when all four stages are ready; otherwise see Troubleshooting.
4. Verify the Cluster
Run the following commands from a machine where ac is logged in to the platform:
Continue when every node is Ready; otherwise see Troubleshooting.
Self-built VIP
Applies to: cluster.network.loadBalancer.type: internal. Skip it for an external load balancer.
Continue when the output shows internal with your VIP and port, an alive ModuleInfo, a synced and healthy alive AppRelease, and a Ready alive Pod on every control plane node; otherwise see Self-built VIP in Troubleshooting.
Then log in to a control plane node of the cluster as the boot user (ssh boot@<control-plane-node-ip>). Use the private key of one of the SSH public keys in cluster.sshKeys. Only root can read the cluster CA file, so run curl with sudo:
Continue when it prints ok; otherwise see Self-built VIP in Troubleshooting.
Control Plane HA
Applies to: provider.dcs.controlPlaneHA: true. Skip it when it is false.
Continue when the status is True; otherwise see Control Plane HA in Troubleshooting.
Additional NICs
Applies to: node groups with network.additions. Skip it otherwise.
Continue when each DCSMachine lists one additional NIC per address in its host's additionalIps; otherwise contact technical support.
Run create Again
create only creates the cluster. Do not run it on a cluster that already exists. To change a running cluster, see Manage Nodes.
If create stops before the cluster is created, run the same command again. Completed work is skipped. When you run create again on the same directory:
- It recreates objects that were deleted. The exception is a Secret:
accreates Secrets once and then leaves them as they are. - It does not overwrite a field that you changed with another tool. When the rendered value differs,
createreports that the fields are owned by another manager and stops. Do not delete the object that the error names. - When
manifests/already exists,createasks whether to reuse it. Press Enter to reuse it, or answernto render again after you changeinstall-config.yaml. When standard input is not a terminal, pass--reuse-manifests=trueor--reuse-manifests=falseinstead. - Reusing
manifests/ignoresinstall-config.yamland skips every check.
Do not edit the files in manifests/.
Keep <install-dir>/manifests/, or set cluster.encryptionProviderConfig. A generated encryption key is kept only in manifests/. If you render again without doing either, a new key is generated, and manifests/ then no longer records the key that the cluster uses.