Publish a service

Publish one hostname through Clearplane and confirm that requests reach the intended upstream.

Before you start

  • Use a working Clearplane deployment.
  • Point the hostname at the deployment.
  • Make the application reachable from Clearplane.
  • Know the application's scheme and listening port.

Choose UI ownership or Docker-label ownership for the route. Keep later changes in the same source.

UI

  1. Open Upstream destinations and create the application destination with its reachable address, scheme, and port.
  2. Open Upstream clusters and create a cluster that contains the destination.
  3. Open Proxy routes and create a route for the public hostname using that cluster.
  4. Save the route and apply configuration if the UI reports that an apply is required.

UI-created resources remain UI-owned.

Docker labels

Add labels to the application container:

services:
  app:
    image: example/app:latest
    labels:
      clearplane.proxy.enabled: "true"
      clearplane.proxy.host: "app.example.com"
      clearplane.proxy.port: "8080"

Clearplane creates the destination, cluster, and route from the discovered container. Change label-owned resources at the container definition, not in the UI.

See the proxy directives for paths, path rewrites, alternate hosts, route order, and the upstream activity timeout.

Verify

Open the public hostname and confirm the expected application responds. In Clearplane, confirm the route names the intended cluster and destination. If the request fails, filter Logs to that route before changing configuration.