Home / Project management / The project / Create a project

Create a project

Before your project team starts working, you can create a project for your team based on the existing cluster resources on the platform, according to the project scale and actual business resource needs, which is isolated from the resources and personnel of other projects (tenants).

The resources of the new project can come from multiple clusters on the platform. When creating a project, to avoid resource waste or shortage affecting business, you can allocate resources to the project reasonably based on the project scale and the resource usage of clusters on the platform.

Cautions

When creating a project, the platform will create a namespace with the same name as the project in the associated clusters to isolate platform-level resources. Please do not operate this namespace and its resources.

Procedure

In the Project Management view, click Create Project.

On the Basic information page, refer to the following instructions to configure the relevant parameters.

Parameter	Description
Name	The name of the project, which cannot be the same as the name of an existing project or the names in the project name blacklist. Otherwise, the project cannot be created. Note: The names in the project name blacklist are the names of special namespaces under the platform clusters, including: cpaas-system, cert-manager, default, global-credentials, kube-ovn, kube-public, kube-system, nsx-system, alauda-system, kube-federation-system, ALL-ALL, and true.
Cluster	The cluster associated with the project, which the administrator can allocate resource quotas for. Click the drop-down selection box to select one or more clusters. Note: The cluster cannot be selected when it is abnormal.

Parameter

Description

Name

The name of the project, which cannot be the same as the name of an existing project or the names in the project name blacklist. Otherwise, the project cannot be created.
Note: The names in the project name blacklist are the names of special namespaces under the platform clusters, including: cpaas-system, cert-manager, default, global-credentials, kube-ovn, kube-public, kube-system, nsx-system, alauda-system, kube-federation-system, ALL-ALL, and true.

Cluster

The cluster associated with the project, which the administrator can allocate resource quotas for. Click the drop-down selection box to select one or more clusters.
Note: The cluster cannot be selected when it is abnormal.

Click Next and in the project quota setting step, set the resource quotas to be allocated to the current project for the selected clusters.
This includes CPU (cores), memory (Gi), storage (Gi), PVC count (number), Pods (number), virtual GPU (GPU-Manager/MPS), pGPU (physical GPU, cores), and GPU memory.

Note:
- GPU resource quotas can only be configured when GPU plugin are deployed in the cluster. When the GPU resource is a GPU-Manager or MPS GPU, the vMemory quota can also be configured.
  
  GPU Units: 100 units of virtual cores are equivalent to 1 physical core (1 pGPU = 1 core = 100 GPU-Manager core = 100 MPS core), and pGPU units can only be allocated in whole numbers. GPU-Manager 1 unit of memory is equal to 256 Mi, MPS GPU 1 unit of memory is equal to 1 Gi, and 1024 Mi = 1 Gi.
- If no quota is set for a certain type of resource, it defaults to Unlimited. This means that the project can use the available resources of the corresponding type in the cluster as needed, without a maximum limit.
- The project quota values set should be within the quota range displayed on the page. Under each resource quota input box, the allocated quota and total information for that resource will be displayed for reference.
Click Create Project.