Bridge v2.3.0: Kubernetes deployment updates

What’s new

Bridge v2.3.0 adds Kubernetes deployment options and fixes session handling and image dependencies. Use Helm chart 2.1.0 for this release.

• Kubernetes workers report readiness during startup and retirement, so draining proxies stop receiving new Service traffic. The chart adds shared and per-role worker customization, configurable health probes, and optional orchestrator init containers for broker tools. See the Kubernetes guide.
• Argo CD integration provides a versioned worker health check for an existing Argo CD installation. This integration is optional.
• Cluster proxies no longer impose per-IP connection or connection-rate limits, avoiding rejected connections when users share a NAT or gateway address. Configure any required traffic limits at a load balancer or gateway that supports them. See the network guide.
• Bridge reports recording-write and finalization failures across session protocols. Session relays stop on failed writes, including failures while refusing blocked commands.
• Updated SSH dependencies address connection deadlocks and permission handling. The image also removes an unnecessary Python packaging dependency.

Upgrade

Use image britive/bridge:v2.3.0, or its equivalent in your private registry. Kubernetes deployments use chart 2.1.0. Follow the Kubernetes deployment guide or the AWS cluster update instructions. The dependency fixes require no configuration changes.

Verify

Confirm that the deployment uses the v2.3.0 image. Complete the checks in the Kubernetes guide or the AWS guide. Open a test session and confirm that its recording appears in the review UI.