Durable Executor
The Streamtime Durable Executor runs every operation (creating, updating and deleting fleets and workloads) to completion, retrying through failures and restarts, and hands in-cluster work to each fleet’s agent. You choose where it runs once, in first-time setup:
| Choice | Where it runs | What fleets need |
|---|---|---|
| Built-in Orchestrator (recommended) | Inside your Streamtime installation | A route to Streamtime: the private connection |
| Streamtime Managed (needs a license) | Streamtime provisions a dedicated namespace and credentials for you | No route to your installation: fleets connect to the managed endpoint directly |
| Custom Orchestrator (advanced) | A Temporal service you run, self-hosted or Temporal Cloud | A route to your service. Suited to air-gapped or regulated environments, or where you already operate Temporal |
The console still labels the Durable Executor Orchestrator: the setup step, its options and its fields. The steps below quote those labels as shown.
A custom Durable Executor must be reachable from Streamtime and from every fleet at all times. When it isn’t, no fleet operation can run.
Before you start: custom
- The Orchestrator Endpoint of your Temporal service, as
host:port(for exampletemporal.example.com:7233). - An API Key, if the endpoint requires one (for example Temporal Cloud).