Skip to content
Buddy Cluster
buddy-cluster.dev

Publish a service

What this gets you

Any service running in your cluster — not only a just-deployed app — reachable from the Internet on a domain name of your choosing, served over valid HTTPS.

Before you start

  • The service must already be running in your cluster.
  • A domain (or subdomain) you want to use for it, e.g. blog.example.com.
  • If you haven’t already, Buddy walks you through Get your connection ready as part of this wizard — you don’t need to do it separately first.

The steps

  1. Start the wizard from one of two places: an installed app’s Store → Installed tab has a “Publish on the Internet…” action that pre-fills that app’s own service, or open Exposure → Published services and choose Publish a service to pick any service in the cluster.

  2. Pick the service and, if it offers more than one, the port. Buddy shows how many pods are ready behind each option.

    If Buddy can’t tell what a port speaks from its name, it runs a quick check inside the cluster before you can continue — you’re never asked to just guess. A port it recognises as a non-HTTP protocol can’t be published this way.

  3. Enter the public domain name you want, e.g. blog.example.com.

  4. Review — TLS is always Buddy-managed, so there’s nothing to configure there — and confirm to publish.

How you know it worked

The service appears under Exposure → Published services with its certificate issued and its domain resolving to your cluster.

What can go wrong

  • A Route shows a DNS sync error
  • A certificate stays “not issued” or shows an ACME error
  • A Route shows “no pods running”
  • Publish is stuck on “Continue” / the service picker

See these symptoms in Troubleshooting.