Compliant Kubernetes Service documentation has moved

Please note: You are not reading Kubernetes documentation. If you're looking for Compliant Kubernetes Service documentation, it has moved. Read more here.

How to setup a Site

The Platform concept of a Site represents the mapping of a hostname to a code service. An environment can have more than one code service, so its service proxy needs to know how to route requests.

Creating a New Site

Note: An SSL Certificate needs to be uploaded before a site can be created.

To create a new site entry, three pieces of information are needed.

  1. Hostname (this cannot be a wildcard)
  2. Certificate name
  3. Code service label

The hostname is up to you, and the certificate name is also decided by you when uploaded. The code service label is the name of the code service that you intend traffic for this hostname to go to. If you don’t know what your code service’s name is, you can find it in The Platform dashboard.

The CLI sites create command is used to create the site, taking the form datica -E "<your_env_name>" sites create <hostname> <code service label> <certificate name>. For example, to set up a site mapping to a code service named code-1 using an uploaded cert named example:

datica -E "<your_env_name>" sites create code-1 example

Note the leading . - this is required for apex domains.

If you’ve uploaded a wildcard cert and intend to use it with multiple subdomains, that cert can be used as many times as needed:

datica -E "<your_env_name>" sites create code-1 wildcard-example
datica -E "<your_env_name>" sites create code-2 wildcard-example
datica -E "<your_env_name>" sites create code-3 wildcard-example

In order for your service proxy to pick up the new site, it needs to be redeployed:

datica -E "<your_env_name>" redeploy service_proxy

Listing Sites

To list what sites your environment has configured, use the sites list command. For details about a specific site, use the sites show command.

If a site needs to be removed, use the sites rm command.

How do I setup DNS to point to my Datica environment?

The Platform environments are designed to have CNAMES or ALIAS records pointed at them. We create a public hostname for the environment that functions as the target of your DNS entries. You will receive your public hostname as part of your on-boarding process after we provision your environment. Datica Public

CNAME Records

Use CNAMES for pointing specific subdomains at the Datica public hostname. CNAME CNAME

ALIAS Records

Use ALIAS records for pointing the bare domain at the Datica public hostname. ALIAS ALIAS

Wildcard Redirect

If you wish to redirect non-matched DNS traffic to your Datica public hostname, you can create a wildcard CNAME record with your DNS provider. * CNAME

See also