Skip to main content

Routing Web Services

Access to web services over HTTP(S) is provided through local domain names in the domain zone set in the VPC settings. The local domain zone is served by the DNS Server role. If the cluster is public, web services are published under public domain names served by an external DNS server, for example Cloudflare.

Domain Binding Options​

A user's web service can be bound to a domain name in several ways:

  1. To the cluster root domain, consisting of the cluster name and local domain zone, for example: app.lan.shipops.cloud.
  2. To a subdomain, for example: srv2.app.lan.shipops.cloud.
  3. The root domain can be overridden, in which case the user's service can be bound, for example, to mycoolproject.com, srv1.mycoolproject.com, or srv2.mycoolproject.com.

Service Selection and Security​

The service itself is selected from the list of kubes installed in the cluster and the list of services inside the selected kube, if there are several. The list of kubes includes both custom kubes and built-in kubes from the SHIPOPS library.

If necessary, you can set an authentication method for the service. This is convenient if the service itself does not provide authentication.

In the HTTP routing settings, you can also configure TLS so that web services work over HTTPS on port 443. For details, see TLS Settings for HTTPS.