Skip to content
Buddy Cluster
buddy-cluster.dev

Manage and remove what's published

What this gets you

A clear view of everything your cluster currently publishes on the Internet, and a clean way to take a service — or your whole exposure setup — back down.

Before you start

The steps

  1. Open Exposure → Published services to see every published service: its target, its certificate status (issuer, days until it expires), how fresh its DNS is, and whether its target currently has pods running — a service with none is flagged so you notice.

    The Published services list, showing each service's certificate and DNS status
    The Published services list, showing each service's certificate and DNS status
    The Published services list, showing each service's certificate and DNS status

  2. To take down one service: either uninstall the app that owns it (Store → Installed), or remove its Route directly from Exposure → Published services. Either way, its DNS record and certificate are released — nothing orphaned is left behind.

  3. To take down your whole exposure setup, open Exposure → Configuration:

    • Remove the tunnel — only available if Buddy created it. Deletes it from your Cloudflare account and stops the connector; every service published through it stops being reachable.
    • Remove the Cloudflare token — forgets the stored credential, tearing down a Buddy-managed tunnel first if there is one.

Both actions in step 3 are destructive and confirm before acting. Removing the tunnel breaks every service published through it; removing the token disconnects your whole exposure setup. You can reconnect anytime by re-running Get your connection ready.

While testing, point the certificate authority at Let’s Encrypt staging (under Exposure → Configuration) to avoid production rate limits, then switch back to production once you’re happy.

How you know it worked

A removed service disappears from Published services and its domain stops resolving to your cluster. After removing the tunnel or token, the Configuration tab shows the corresponding step as not set up.

What can go wrong

  • “Remove the tunnel” shows “tunnel may still exist at Cloudflare”
  • “Remove the Cloudflare token” fails outright

See these symptoms in Troubleshooting.