Follow the steps below to configure your org with a custom domain name. Domains are scoped to an org and available to be used by all GVCs within the org. Workloads created within a GVC will automatically use the configured domain name for their endpoint URL's.
This quick start will demonstrate how to:
Create a new domain resource by using one of the following methods:
Domainsin the left menu and click
Createdropdown in the upper right corner and select
The console will prompt for the desired subdomain (e.g., sub.example.com). Click
The required DNS entries will be displayed. These entries will need to be added by the person who is responsible
for maintaining the DNS for the domain. Once the DNS entries are added
and the changes have propagated across the Internet, click on the acceptance checkbox and click
GVCin the left menu. If you have multiple GVCs, verify that you are on the desired GVC.
Domaincontrol. The list of available domains will be shown. Select the domain that was configured and click
Save. All workloads associated with this GVC will now be deployed using this domain.
Workloadsin the left menu and choose a workload.
Global EndpointURL is now using your domain and the workload name is the subdomain. This URL is secured with TLS, is load balanced and geo-routed is the nearest healthy location. Clicking the
Openlink will load the workload in a new tab.
Canonical Endpoint uses the default Control Plane domain
cpln.app and behaves the same as the
Global Endpoint. This URL can be
used for troubleshooting.
A workload can be configured to resolve directly to the subdomain by explicitly naming the workload
index. Refer to the
domain reference page for details.
Deployments. This page shows the locations this workload is deployed to. Next to each location is the location specific URL for your workload. Clicking the
Openlink will load the workload only in that location. This is used for troubleshooting.
Configuring your custom domain name with Control Plane allows your workload to be called using your branding in only a few steps. Once configured and associated with a GVC, the domain is used by all the workloads within a GVC.