install-config.yaml Parameters for Huawei DCS
This page describes how the fields of a Huawei DCS workload cluster's install-config.yaml act on DCS: the control plane endpoint, node addresses and placement, disks, and the optional topology. It also lists the objects that ac renders from them. For the fields themselves, see Write install-config.yaml.
TOC
Control Plane Endpoint and HANode Addresses and PlacementDisksChange Persistent DisksOptional TopologySelf-built VIPAdditional NICsRaw Disks for TopoLVMRendered ManifestsWorker ObjectsControl Plane Endpoint and HA
external: your load balancer forwardsTCP/6443to the control plane nodes.internal(Self-built VIP): the provider runs the VIP on the control plane nodes; see Self-built VIP.controlPlaneHA: true: the provider keeps a DRS mutual-exclusion rule for the control plane VMs, and the DCS scheduler keeps them on different hosts. It works with either endpoint mode. The provider does not run DRS itself. For the DCS-side requirements, see DCS Objects, Capacity, and Addresses.
A cluster with a single control plane node still needs one of the endpoint modes.
Node Addresses and Placement
Each node group lists its nodes in hosts, with at least replicas entries. Entries beyond replicas become spare slots in the group's DCSIpHostnamePool. Only when the group has no spare slot is a replacement VM guaranteed to take over the address slot of the node it replaces, and with it the persistent disks; see What Happens on Alauda OS Nodes. Hostnames and addresses must be unique across all node groups and must differ from the control plane endpoint. Every node of a group shares the group's network.
The DCS scheduler picks the host of each VM. With controlPlaneHA: true, the provider also maintains a DRS rule that places the control plane VMs on different hosts; see Control Plane Endpoint and HA. machineFolder groups the VMs on DCS and does not affect placement. A node group can set its own machineFolder under <group>.dcs.
Disks
Every node group must declare the whole standard disk set. ac rejects any other name, and rejects a group that leaves a standard disk out.
- Ephemeral disks go to the
DCSMachineTemplate, next to the system disk, and are recreated with the VM. - Persistent disks and raw disks go to the address slot of each node in the
DCSIpHostnamePool. When a VM is replaced, they are detached and reattached to the replacement, which mounts the existing filesystem instead of formatting it. See Change Persistent Disks and Raw Disks for TopoLVM. - Every mounted disk is formatted
xfs. disks.datastoreapplies to the system disk as well.DatastoreClusterlets DCS pick a member datastore with free space. Prefer it when the platform has one.
Every node group is replaced one node at a time (maxSurge: 0), and so is a control plane of 3 or more replicas.
Change Persistent Disks
Persistent and raw disks are entries in DCSIpHostnamePool.spec.pool[].persistentDisk, as in Worker Objects. slot sets the attach order and the device name in the guest. Each entry names exactly one of datastoreName and datastoreClusterName. When you change the entries of an existing pool:
- An appended entry is attached to the running VM on DCS, but it is formatted and mounted only when the VM is replaced.
- Removing an entry is rejected.
format,options, andpciTypecannot change. - The webhook rejects a change to the size (
quantityGB) or to the datastore of an existing disk.isThinaffects only volumes created later. pathandmountOptionstake effect on replacement VMs.
Optional Topology
Set these in install-config.yaml before the cluster is created.
Self-built VIP
Set cluster.network.loadBalancer.type: internal with the fields described in Write install-config.yaml, and meet the Self-built VIP requirements. controlPlaneHA is not required. type, address, port, vrid, and interface cannot change after the control plane is initialized.
To check it, see Verify the Self-built VIP.
Additional NICs
A node group can attach NICs on secondary networks, such as storage, management, or isolation networks, through <group>.network.additions and hosts[].additionalIps; see Write install-config.yaml. A host may list fewer addresses than there are NICs. Addresses match NICs in order, so the host gets only the first NICs, one for each address. Its VM has no other additional NICs.
- Without
dcs, an additional NIC attaches toprovider.dcs.network, the same network as the primary NIC. - An additional NIC gets no gateway and uses the node's first DNS server. Static routes and route metrics need MachineConfig or guest OS configuration.
- The primary
hosts[].ipstays the Kubernetes Node IP. - The NICs are added when the provider clones a VM. Changing them later does not hot-add NICs to running VMs.
Raw Disks for TopoLVM
<group>.disks.rawDisks attaches unformatted block devices for TopoLVM. Raw disks are rendered as persistent disks without a mount path or filesystem. They come after the standard persistent disks in the slot order of the DCSIpHostnamePool, on the same datastore with the same isThin and pciType. Like /var/cpaas, they are kept when a VM is replaced, and they are deleted with the cluster. Do not remove or reorder entries after the cluster is created, because the slot of a disk follows its position, and removing a persistent disk is rejected.
Rendered Manifests
ac writes the objects it applies to <install-dir>/manifests/, one file per object, all in cpaas-system. For their API fields, see the Huawei DCS API reference.
The credential Secret is yours to manage; ac does not render or delete it.
Worker Objects
hosts, network, and the persistent and raw disks go to the DCSIpHostnamePool. The VM size, the location, and the ephemeral disks go to the DCSMachineTemplate. For one worker host with the defaults:
Additional NICs render as additionNic entries on each pool slot.