Skip to content
Ownkube

Public hostnames and TLS

A web app with Public hostname on is reachable at https://<subdomain>.ownkube.app the moment its first rollout is healthy. Ownkube allocates the hostname, issues and renews the TLS certificate, and routes requests to your container’s port. There is nothing to configure.

How the hostname is chosen

Section titled “How the hostname is chosen”
  • The subdomain is derived from the deployment name. If it is taken, Ownkube suggests a free variant.
  • It has to be a valid DNS label: lowercase letters, digits and hyphens, up to 63 characters, no leading or trailing hyphen.
  • Workers, jobs, databases and caches have no public hostname of their own. A database or cache gets a separate hostname when you turn on Public access; see Postgres.

Change the hostname

Section titled “Change the hostname”
  1. Open the deployment’s Overview tab and click Edit next to the hostname.
  2. Type a new subdomain. Ownkube checks availability as you type.
  3. Save. The new hostname is live within a minute. The old one stops resolving: update anything that linked to it.

From the terminal:

Terminal window
okctl deploy subdomain check my-app        # is it free?
okctl deploy subdomain suggest <id>        # suggestions near the current name
okctl deploy subdomain set <id> my-app     # change it

What the edge does for you

Section titled “What the edge does for you”
  • TLS: a certificate for *.ownkube.app terminates HTTPS at the region edge. Your container speaks plain HTTP on its port.
  • Routing: the edge routes to the healthy replicas of your app. During a rollout only replicas that pass their health checks receive traffic.
  • Wake on request: if the app is asleep, the edge holds the request while it starts.
  • Access protection (own cloud only): put a password in front of the hostname. See Access protection.

Metrics on the hostname

Section titled “Metrics on the hostname”

Because requests pass through the edge, Ownkube can show request rate by status class, p95 latency and network in and out for any app with a public hostname. See Metrics.

Bandwidth

Section titled “Bandwidth”

Traffic leaving the region to the internet is billed per GB at the region’s rate; inbound traffic and traffic inside the region are free. See Regions and Understanding your bill.

Your own domain

Section titled “Your own domain”

On Ownkube Compute, apps are served on *.ownkube.app only. If you need app.example.com, run the app on a Starter cluster in your own AWS account, where Ownkube manages a certificate for your domain, including the root domain. See Custom domains.

Private networking How services in an environment reach each other without going through the edge.
Health checks Decide when a replica is ready to receive traffic.
Custom domains Your own domain on a Starter cluster.