Service Availability
Every Hosted Service and Connected Service instance has a "Where can this service be used" section on its detail page (and, optionally, at creation time) that controls which environments can connect to it via Connect Services. The rules aren't entirely intuitive, so this page spells them out explicitly instead of leaving them to be inferred from the UI.
The three axes
Availability is controlled by up to three independent axes:
| Axis | What it does | Hosted | Connected |
|---|---|---|---|
| Environments | Directly lists which environments can use this service | ✓ | ✓ |
| Labels | Allows environments that carry the selected labels | ✓ | ✓ |
| Clusters | Allows all environments on the selected clusters | — | ✓ |
Hosted Services don't offer a Clusters axis: a hosted instance already runs on a single, fixed cluster, so choosing a cluster for it would be meaningless.
Each axis can be set to "Not used", which is a deliberate choice, not an empty selection — an axis in this state doesn't contribute to and doesn't restrict the result at all.
Evaluation order
The axes are evaluated in this order:
- Environments = "nowhere" ⇒ the service is not available anywhere, regardless of the other axes.
- Environments or Clusters = "all" ⇒ all reachable environments.
- All three axes are "Not used" ⇒ all reachable environments (this is the default state of a new service).
- Otherwise ⇒ the union of the axes' selected values, restricted to reachable environments.
"Reachable environments" means all environments of the account for a Connected Service, or the environments of the instance's own cluster for a Hosted Service.
It evaluates live
The result isn't computed once and stored — it's evaluated live against the current state of environments, labels, and clusters.
Reference example: to make a Connected Service available in all environments of cluster X, set Clusters to [X] and leave Environments and Labels as "Not used". Because this evaluates live, an environment added to cluster X later is automatically in scope — no further action needed.
Setting it up
Availability can be configured at creation time, not only after the fact on the service detail page — see the relevant create page for Hosted Services or Connected Services.