Domains and HTTPS - Kool Cloud

Managing domains and HTTPS

All deployed environments will run under HTTPS. Cloud will automatically generate certificates for your environment the first time it is deployed using the Let'sEncrypt engine (via K8S certmanager).

You always need to provide the environment domain when running a deploy. The domain is going to be the key identifier of your environment when accessing it via the Kool CLI.

kool cloud --token="<my token>" deploy --domain=""

You can provide those values via environment variables as well if that's easier for you:

  • KOOL_API_TOKEN for the access token.
  • KOOL_DEPLOY_DOMAIN for the domain environment you want to deploy to.

Important to notice: if you deploy to a new domain that doesn't currently exist in your Cloud panel, that is totally fine and will just create a very new environment for that domain.

Some applications may require serving more than just one domain. This can be easily achieve with Cloud.

When deploying via the CLI, you can specify any number of extra domains that should point to your application:

kool cloud --token="<my token>" deploy --domain="" --domain-extra=""

You are welcome to use a subdomain like on your staging or development environments. By using that, you will have HTTPS certificates up and running instantly for that environment after the first deploy.

When you create an environment to be deployed using your own custom domain name, you will need to check out in the Cloud panel for that environment the instructions to where to point your A/CNAME DNS records for that domain.

HTTPS certificates will only be successfully generated once the DNS is correctly pointing your domain to Cloud.

As stated above for all environments Cloud will trigger LetsEncrypt routines to generate a valid TLS certificate for your environment domain. All that is required for that to succeed is that the used domain points properly to Cloud IP addresses.

That is why it's important to notice that when deploying a custom domain (not a * your will only work properly after the DNS records point properly to Cloud and the LetsEncrypt process had time to perform the HTTP01 Acme challenge process.
By choosing "Accept all cookies" you agree to the use of cookies to help us provide you with a better user experience and to analyse website usage. Only the essential cookies are necessary for the proper functioning of our website and cannot be refused.
Check out our Cookie Policy and Privacy Policy for more information.