docker/egress/v1.1.3

parruda/swarmdocker/egress/v1.1.3Jun 29, 2026by Pangjiping

AI Summary

Enhances MITM proxy capabilities by supporting multiple user addon scripts and clarifies deployment constraints regarding service mesh sidecars.

Key Highlights

Supports multiple user MITM addon scripts via comma-separated paths.
Added documentation warnings about service mesh sidecar conflicts with egress features.
Fully backward compatible with previous single-path configuration.

New Features

Multiple user MITM addon scripts support.
Enhanced documentation regarding service mesh sidecar conflicts.

Full Release Notes

## What's New

### ✨ Features

- **Multiple user MITM addon scripts** — `OPENSANDBOX_EGRESS_MITMPROXY_SCRIPT` now accepts comma-separated paths (e.g. `/scripts/a.py,/scripts/b.py`), with each script passed as a separate `-s` flag to mitmdump after the built-in system addon. Previously only a single addon path was supported. Empty or whitespace-only entries are silently skipped. Fully backward compatible — single-path values and empty values behave exactly as before. (#1126)

### 📖 Documentation

- **Service mesh sidecar conflict documented** — Added explicit warnings that egress-sidecar features (per-sandbox network policy, transparent MITM, Credential Vault) are not supported when a transparent service-mesh sidecar such as Istio or Envoy is injected into the same sandbox pod. The docs now explain the shared-network-namespace interception conflict and point operators to safe deployment patterns. (#1118)

## 👥 Contributors

Thanks to these contributors ❤️

- @Pangjiping
- @Gujiassh

---
- Docker Hub: opensandbox/egress:v1.1.3
- Aliyun Registry: sandbox-registry.cn-zhangjiakou.cr.aliyuncs.com/opensandbox/egress:v1.1.3