Outbound connections
For: cluster operators and plugin authors.
Use this inventory to review every connection that can leave a cluster. Each entry identifies the component that connects, the trigger and the setting that controls it.
Nothing phones home. Orchestrator Zero sends no telemetry, usage statistics, crash reports or update checks, to us or to anyone else, and neither does the Temporal server inside it. If telemetry is ever added, it will be opt-in: off until an operator turns it on, and documented on this page first.
Every other connection to a host outside the cluster happens because you configured something or used a feature that needs it. This page lists them all, for the server, the node, the runtime on the node and the official plugins.
make e2e-egress checks that its dev server, node, quickstart and basic plugin job make no outside connections. It also checks a cluster on PostgreSQL when OZ0_TEST_POSTGRES_URL is set. The test records outbound attempts in a network namespace and fails on any. It does not exercise every optional integration in this inventory.
Connections inside the cluster are not listed here: nodes to the edge (ports 7233 and 7443), edges to management and PostgreSQL, servers to each other, and anything on loopback. See Ports.
Related tasks and reference
Previous section links
check it yourself: Read the section.
the node: Read the section.
the official plugins: Read the section.
the runtime on the node: Read the section.
the server: Read the section.
what a provider reaches on a calls behalf: Read the section.