Infrastructure Resources for Huawei DCS
TOC
OverviewCloud CredentialsUsing the Web UIPrerequisitesCreating a Cloud CredentialManaging Cloud CredentialsUsing YAMLIP PoolsUsing the Web UIPrerequisitesCreating an IP PoolManaging IP PoolsUsing YAMLMachine TemplatesUsing the Web UIPrerequisitesCreating a Machine TemplateManaging Machine TemplatesUsing YAMLResource RelationshipsNext StepsOverview
Before creating clusters on Huawei DCS, you need to configure infrastructure resources including cloud credentials, IP pools, and machine templates.
You can manage infrastructure resources using either the web UI or YAML manifests. The web UI provides a guided interface with validation, while YAML offers automation capabilities.
Namespace Requirement
All infrastructure resources must be deployed in the cpaas-system namespace to ensure proper integration with the platform as business clusters.
Cloud Credentials
Cloud credentials store the DCS platform access information required for cluster operations.
Using the Web UI
Prerequisites
Before creating a cloud credential, verify the following DCS platform requirements:
User Configuration:
- User Type: Must be
Interface interconnection user - Role: Must be
administrator
Password Policy: Navigate to System Management → Rights Management → Rights Management Policy and verify:
- Policy:
Whether to modify the password of an interface interconnection user upon password resetting and first login - Value: Must be set to No
If set to Yes, the user's password will be forced to change upon first login, breaking authentication and causing cluster creation failures.
Creating a Cloud Credential
Navigation: Clusters → Cloud Credentials → Create Cloud Credential → Select Huawei DCS
Form Fields:
Validation Rules:
- Name must be 1-63 characters, containing only lowercase letters, numbers, and hyphens, and must start and end with a letter or number
- DCS Endpoint must be a valid URL format starting with
http://orhttps://
Managing Cloud Credentials
Viewing Credentials: Navigate to Clusters → Cloud Credentials to view all configured credentials with their type, creation time, and creator.
Updating Credentials: Click Update on a credential to modify the Display Name. Password updates are not supported in the current version (planned for a future release).
Deleting Credentials: Click Delete to remove a credential. Confirm the deletion in the dialog.
Using YAML
Create a Secret resource to store DCS authentication information:
Parameter Descriptions:
Example:
IP Pools
IP pools define the network configuration (IP addresses, subnet masks, gateways, DNS) for cluster nodes. Each pool can contain multiple node entries, and each node can have multiple network interface configurations.
Using the Web UI
Prerequisites
- Cloud Credential has been created
Creating an IP Pool
Navigation: Clusters → Virtual Machine → IP Pools → Create IP Pool → Select Credential
Form Structure:
The IP Pool form consists of a list of Pools. Each Pool represents one node and contains:
- Node IP (required, exactly one per Pool)
- Additional NIC IPs (optional, multiple per Pool)
Node IP Fields:
Additional NIC IPs Fields:
Validation Rules:
- IP addresses must be unique within the same IP Pool
- IP addresses must be valid IPv4 format
- Subnet mask must be valid format
- IP address must be within the configured subnet range
- Gateway must be a valid IPv4 address within the subnet range
Tips:
- At least one node entry is required
- Exactly one Node IP configuration is required per node
- Additional NIC IPs are optional for multi-NIC scenarios (e.g., storage network separation)
Managing IP Pools
Viewing Pools: Navigate to Clusters → Virtual Machine → IP Pools to view all configured pools with their node IPs and creation time.
Updating Pools: Click Update to add or remove node entries and modify network configurations.
Deleting Pools: Click Delete to remove a pool. Confirm the deletion in the dialog.
Using YAML
Create a DCSIpHostnamePool resource:
Parameter Descriptions:
You must configure machine information for a number of machines greater than or equal to the number of nodes you plan to deploy. Insufficient entries will prevent node deployment.
Machine Templates
Machine templates define the virtual machine specifications (VM template, CPU, memory, disk, network) for cluster nodes. Each machine template has a Type that determines its usage:
- Control Plane: For control plane nodes
- Worker Node: For worker nodes
Using the Web UI
Prerequisites
- IP Pool has been created
- VM Template has been created in the DCS platform using MicroOS image
- ConfigMap YAML has been applied to the global cluster
VM Template and ConfigMap:
Each MicroOS release includes a ConfigMap YAML that maps VM templates to Kubernetes versions. Apply this YAML before creating machine templates:
Important: The cpaas.io/dcs-vm-template label value must match the VM template name in the DCS platform.
Creating a Machine Template
Navigation: Clusters → Virtual Machine → Machine Templates → Create Machine Template → Select Credential
Form Fields:
Disk Configuration:
The disk configuration varies by template type.
Control Plane Required Disks:
Worker Node Required Disks:
You may add additional disks, but must retain all mandatory disks listed above.
Disk Field Descriptions:
VM Template Selection Tip:
If multiple VM templates have the same Kubernetes version, select the template with the most recent OS version to benefit from the latest security updates and system improvements.
Managing Machine Templates
Viewing Templates: Navigate to Clusters → Virtual Machine → Machine Templates to view all templates with their VM Template Name, Resource, Location, Specs, and IP Pool.
Updating Templates: Click Update to modify specifications. Note that the Name field cannot be changed after creation.
Deleting Templates: Click Delete to remove a template. Confirm the deletion in the dialog.
Using YAML
Create a DCSMachineTemplate resource:
Parameter Descriptions:
*Required when parent object is specified
Storage Requirements
Datastore Cross-Host Access
The datastore clusters (datastoreClusterName) must support cross-host access across all physical machines in the DCS platform. If a datastore is only available on specific hosts, VM creation will fail when the DCS platform attempts to schedule the VM on a different host.
Shared Storage for Ignition If your datastore does not support direct file uploads (required for Ignition configs), you must provide a shared storage solution (e.g., NFS) that supports multi-host mounting.
Disk Configuration Rules
You may add custom disks, but must retain the mandatory system and data disks shown in the example (systemVolume, /var/lib/kubelet, /var/lib/containerd, /var/cpaas).
Resource Relationships
Infrastructure resources have the following dependency relationships:
Resource Reusability:
- One Cloud Credential can be used for multiple clusters
- Multiple IP Pools can be created for different network segments
- Multiple Machine Templates can be created for different node types and specifications
Next Steps
After configuring infrastructure resources: