Usage Guide

1. Cluster

1. You are required to authenticate your identity before using the UK8S service.
2. The master node in the cluster serves as the management node; it is not recommended to schedule services on this node.
3. A single UK8S cluster can support up to 5,000 nodes, but it is recommended not to exceed 1,000 nodes in a production environment.
4. The supported Kubernetes version may lag behind the community version by two releases. Please refer to the console for specifics.
5. If the API whitelist is enabled for your cloud account, please add the subnet 10.10.10.10/32 to the list allowed for API access, in the Access Restriction column on the Account Security page in the console.

2. Node

1. The default cloud host image used for Node nodes is CentOS 7.6. If the system is reinstalled or system configurations are modified without permission, the cluster may become unavailable.
2. The cloud host system disk for Node nodes is SSD by default and supports the addition of data disks. After a data disk is added, containers will run on the data disk by default upon startup.
3. The cloud host uses the N type by default and you can also choose other types (such as O type, C type).
4. The node label UhostID=xxx is used for host management. Please do not delete or modify this label to avoid disrupting cluster data.

3. Storage Volume

Supported Types

Currently, the following storage types are supported: SATA, SSD UDisk, UFS, and UFile

Use UDisk in UK8S

Use UFS in UK8S

Use UFile in UK8S

Supported Regions

Please refer to [the storage documentation](/docs/uk8s/udisk/intro#UK8S supported regions for storage mounting)

4. Resource Naming Standards

Once you’ve created a UK8S cluster, UK8S will create resources such as UHost, ULB, UDisk, EIP etc., in the current project on your behalf. Changing the configuration or deleting it may cause the cluster to become unavailable, so please be careful. The main resources involved are as follows:

1. Resources created by the UK8S management service follow this naming convention:

• uk8s-xxxxxxxx-master-m is the name of the Master node, serving as the Master node of the cluster;
• uk8s-xxxxxxxx-n-xxxxx is the name of the Node node, serving as the Node node of the cluster;
• uk8s-xxxxxxxx-master-ulb4 is the name of the cluster’s ApiServer internal network ULB, serving as the internal entrance of the cluster;
• uk8s-xxxxxxxx-master-ulb4-external is the name of the ApiServer external network ULB, serving as the external entrance of the cluster;
• system_udisk_uk8s-xxxxxxxx-n-xxxxx is the name of the UDisk resource, serving as the system disk of the cluster node;
• data_udisk_uk8s-xxxxxxxx-n-xxxxx is the name of the UDisk resource, serving as the data disk of the cluster node.

2. Resources created by the UK8S plugin follow this naming convention:

• ingress-nginx.ingress.svc.uk8s-xxxx is the name of the ULB resource, created by the UK8S ULB plugin, used for LoadBalancer type Service, and its note is UID-xx-xxx, which is actually the uuid of Service in UK8S. Its naming convention is svc-name.namespace.svc.uk8s-id.

• TCP_443_xxx-xxxxx is the name of the Vserver, created by the UK8S ULB plugin, corresponding to the different ports in the LoadBalancer type of Service. Its naming convention is service-protocol_service-port_service_uuid.

• pvc-9393f66f-c0b5-11e9-bd6d-5254001935f2 is the name of the UDisk, created by the UK8S storage plugin, corresponding to the PVC in UK8S. Its naming convention is pvc-pvc_uuid.