Agent Proxy must be able to serve Client Workload traffic throughout the entire lifecycle of the Client Workload.
When both the Client Workload and Agent Proxy receive a termination signal (SIGTERM), the Agent Proxy attempts to
continue operating and serving traffic until the Client Workload exits.
Agent Proxy runs in distinct environments, such as Virtual Machines, Kubernetes, and ECS Fargate, where workload lifecycles can differ. To handle these variations, Agent Proxy uses different termination strategies.
Configuration
Section titled “Configuration”You can configure the termination strategy by setting the AEMBIT_SIGTERM_STRATEGY environment variable.
The supported values are:
immediate– Exits immediately upon receivingSIGTERM.sigkill– Ignores theSIGTERMsignal and waits for aSIGKILL.
Default termination strategies
Section titled “Default termination strategies”The following table lists the default termination strategy for each environment.
You can override the default behavior using the AEMBIT_SIGTERM_STRATEGY environment variable.
| Environment | Default Termination Strategy |
|---|---|
| Kubernetes | sigkill |
| AWS ECS Fargate | sigkill |
| Virtual Machine (Linux) | immediate |
| Virtual Machine (Windows) | N/A |
| Virtual Appliance | immediate |
| Docker-compose on VMs | sigkill |
| AWS Lambda container | immediate |