Skip to content
This repository has been archived by the owner on Mar 16, 2024. It is now read-only.

Latest commit

 

History

History
141 lines (88 loc) · 6.39 KB

domain.md

File metadata and controls

141 lines (88 loc) · 6.39 KB

In this step we will show how to use a custom domain to expose the VotingApp Acorn application.

About Acorn default domain

When you run the VotingApp in the previous steps, you probably noticed the http endpoints returned use the oss-acorn.io domain, similar to the following ones:

By default, the http endpoints have the following format:

CONTAINER_NAME-APPLICATION_NAME-UNIQUE_HASH-CLUSTER_DOMAIN

In the current example, this can be splitted as follows:

  • container: voteui
  • application name: vote
  • unique hash: c7bc34b6
  • cluster domain: 8eovu9.oss-acorn.io

Acorn allows to define a custom cluster domain as well as a custom format as we will see below.

In the following we will consider 2 cases to setup your custom domain:

  • first case: you are running Acorn on your own cluster
  • second case: you are using Acorn Saas platform

Using a custom domain in Acorn Saas

To use a custom domain when running an application in Acorn Saas you just need to provide the domain using the -p flag in the acorn run command and to create a CNAME in your DNS provider.

Note: I will illustrate the usage of the custom domain luc.run, you'll need to replace it with your own domain name.

Running the following command will expose the voteui and resultui respectively on vote.luc.run and result.luc.run (on top of automatically on-acorn.io domains)

acorn run -n vote -p vote.luc.run:voteui:80 -p result.luc.run:resultui:80 .

Below is the output showing the domains used:

┌───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
| STATUS: ENDPOINTS[https://result.luc.run, https://vote-027d5876.zvgz4d.on-acorn.io, https://vote-8bc9eaf7.zvgz4d.on-acorn.io, https://vote.luc.run] HEALTHY[7] UPTODATE[7] OK |
└───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

In order for vote.luc.run and result.luc.run to be available we need to add CNAME in the DNS provider as follows:

Cloudflare

We can then access the vote and result UI

Vote

Result

Also, as you can see the subdomains are directly served over TLS !

Using a custom domain in your own Acorn installation

Defining a custom domain during Acorn installation

When installing Acorn we can specify our own cluster domain instead of the default one (oss-acorn.io) using the --custom-domain flag. At the same time we can also disabled the dns managed by Acorn as we don't need it with our custom domain.

First configure Acorn with the following command (you can replace the example domain k8sapps.xyz by your own domain name):

acorn install --cluster-domain k8sapps.xyz --acorn-dns disabled

Next update the application:

acorn run -n vote --update .

This time you should be returned endpoints with the following format:

Endpoints still have the format CONTAINER_NAME-APPLICATION_NAME-UNIQUE_HASH-CLUSTER_DOMAIN but this time the cluster domain is k8sapps.xyz (or the one you used) instead of the default one.

Using the --http-endpoint-pattern flag in the Acorn installation command, we could define our own format for the http endpoints as well (this is described in the endpoint patterns documentation).
To illustrate this, let's update the Acorn installation adding the following flag:

acorn install --http-endpoint-pattern="{{.Container}}.{{.App}}.{{.ClusterDomain}}"

Note: running the install command once again only sets the flag specified and keeps the values of the previously configured flags.

Update the Acorn app one more time:

acorn run -n vote --update .

The changes made above will cause the application to be exposed on the following endpoints:

On top of this approach, we can also define a domain at launch time as we will see below.

Defining a domain at runtime

Acorn allows to specify the domain name of a given container directly from the command line. For instance, the following command update the app using the -p / --publish flag to define the domains for both voteui and resultui containers:

acorn run -n vote -p vote.k8sapps.xyz:voteui -p result.k8sapps.xyz:resultui --update .

On top of the endpoints generated above we also get the ones defined in the run command:

To access the application using the endpoints http://vote.k8sapps.xyz and http://result.k8sapps.xyz, you can either:

  • change the /etc/hosts of your machine ensuring both domains (vote.k8sapps.xyz and result.k8sapps.xyz) resolve to the IP address of your Ingress Controller

Example of changes that can be done to the /etc/hosts (your IP address will be different):

192.168.205.2 vote.k8sapps.xyz
192.168.205.2 result.k8sapps.xyz
  • change the setting of your own DNS if you have access to it

We can then access both frontend using the custom domains.

Vote UI Result UI

Note: changing the setting of your DNS only makes sense if our cluster can be reached from the internet

Previous
Next