#Configure Domain

Add domain name resources to the platform and allocate domains for use by all projects under a cluster or resources under a specific project. When creating a domain name, binding a certificate is supported.

Successfully created and allocated domain names on the platform can be utilized in the following features of Container Platform:

• Create Inbound Rules: Network Management > Inbound Rules > Create Inbound Rule

• Create Native Applications: Application Management > Native Applications > Create Native Application > Add Inbound Rule

• Add Listening Ports for Load Balancing: Network Management > Load Balancer Details > Add Listening Port

Once the domain name is bound to a certificate, application developers can simply select the domain name when configuring the load balancer and inbound rules, allowing the use of the certificate that comes with the domain name for https support.

#Example Domain custom resource (CR)

# test-domain.yaml
apiVersion: crd.alauda.io/v2
kind: Domain
metadata:
  name: '${random-unique-name}'
  annotations:
    cpaas.io/secret-ref: developer.test.cn-xfd8x
  labels:
    cluster.cpaas.io/name: global
    project.cpaas.io/name: demo
spec:
  name: developer.test.cn
  kind: full

#Creating Domain by using the web console

1. Go to Administrator.

2. In the left navigation bar, click Network Management > Domain Names.

3. Click Create Domain Name.

4. Configure the relevant parameters according to the following instructions.

   Parameter	Description
   Type	Domain: A complete domain name, e.g., developer.test.cn. Wildcard Domain: A wildcard domain with a wildcard (*) character, e.g., *.test.cn, which includes all subdomains under the domain test.cn.
   Domain	Enter a complete domain name or domain suffix based on the selected domain name type.
   Allocate Cluster	If a cluster is allocated, you also need to select a project associated with the allocated cluster, such as all projects associated with the cluster.
   Certificate	Includes the public key (tls.crt) and private key (tls.key) for creating a domain name-bound certificate. The project to which the certificate is allocated is the same as the bound domain name. Notes: Binary file imports are not supported. The bound certificate should meet the conditions of correct format, within the validity period, and signed for the domain name, etc. After creating the bound certificate, the name format of the bound certificate is: domain name - random characters. After creating the bound certificate, the bound certificate can be viewed in the certificate list, but updates and deletions of the bound certificate are only supported on the domain detail page. After creating the bound certificate, updating the certificate content is supported, but replacing other certificates is not supported.

5. Click Create.

#Creating Domain by using the CLI

kubectl apply -f test-domain.yaml

#Use the Same Domain Across Multiple Clusters

You can configure the same domain to be used across multiple clusters by creating separate Domain resources in the global cluster with the identical spec.name value but different cluster.cpaas.io/name labels.

#Configure via Web Console

1. Follow the steps in Creating Domain by using the web console.

2. Create two domain resources with the same domain name (e.g., app.example.com).

3. For each domain, select a different Allocate Cluster (e.g., cluster-a and cluster-b).

#Configure via CLI

Create two Domain custom resources in the global cluster with identical spec.name but different cluster.cpaas.io/name labels:

Domain for Cluster A:

apiVersion: crd.alauda.io/v2
kind: Domain
metadata:
  name: '${random-unique-name}'
  labels:
    cluster.cpaas.io/name: cluster-a
    project.cpaas.io/name: project-a
spec:
  name: app.example.com  # Same domain name
  kind: full

Domain for Cluster B:

apiVersion: crd.alauda.io/v2
kind: Domain
metadata:
  name: '${random-unique-name}'
  labels:
    cluster.cpaas.io/name: cluster-b
    project.cpaas.io/name: project-a
spec:
  name: app.example.com  # Same domain name as Cluster A
  kind: full

#Subsequent Actions

• Domain Registration: Register the domain if the created domain has not been registered.

• Domain Resolution: Perform domain resolution if the domain does not point to the platform cluster's load balancing address.

#Additional resources

• Configure Certificate