Understanding isolatedAgents in Kubernetes Deployments

The `isolatedAgents` setting affects how run termination is handled in Kubernetes deployments. When disabled (default), the agent triggers termination requests through the Kubernetes API. When enabled, runs check for termination themselves using a background thread.

To enable isolated agents: 1. Configure your deployment to set `isolatedAgents: true` 2. Set up separate resource allocations for each agent 3. Configure routing for multiple agents if needed

Key considerations: - The default setting (disabled) is recommended for simpler deployments - Background thread termination is generally reliable but could be affected if the process becomes completely locked - Normal operations like slow web requests won't impact the background thread's ability to terminate - Using isolated agents adds complexity in managing multiple agents within the same cluster

Related topics: - Agent Queue Configuration - Kubernetes Resource Management - Multi-agent Deployments