Skip to main content
Feature toggles flip optional or experimental behaviors. Manage them with 2501 infra feature. Operational rules and host facts are always checked before proposed task actions run when either is available. This verification has no feature toggle.

Reference

Integration

Security & Logging

Jobs

Experimental

When to flip what

  • enableElasticSearch if you have an Elasticsearch instance and want the engine + Command Center to ship logs to it.
  • enableSecureLogs for tenants with strict log-encryption requirements.
  • enableSlowInference if your tenant runs on a self-hosted model with low throughput - reduces task concurrency to avoid queue starvation.
  • enableSatelliteClusters to reach hosts from inside a customer Kubernetes cluster instead of dialing them from the engine. It adds the Clusters page and a host’s executor placement fields. Turning it back off hides that surface without changing where anything executes: a host already placed on a cluster keeps running through it, and placement stays writable through the API, so the toggle governs the surface rather than the capability.
    • While it is off, two states have no way back through the Command Center: a host cannot be returned to a direct dial, and a credential held by a cluster cannot be deleted. Turn the toggle on to unwind either.
  • Anything labeled experimental: open a support ticket before enabling in production.