Observe changing inventory
Secret and managed HTTP sources, bounded refresh with protected cache, destination-specific probes, and SQLite observation history.
EgressFox is an open-source adaptive egress control plane for reliable external connectivity.
For DevOps and platform engineers managing changing proxy gateways. Discover endpoints, observe destination-specific health, and publish validated configurations for Mihomo and sing-box.
Core implemented. First public release in preparation.
01 / Why EgressFox
External integrations can depend on gateways that rotate credentials, disappear, slow down, or fail only for particular destinations. A static endpoint list cannot distinguish stale evidence from a confirmed failure. Manually replacing gateways makes decisions difficult to reproduce.
EgressFox turns endpoint descriptions and historical observations into reproducible selection decisions. Stability controls reduce unnecessary switches, and invalid candidate configurations never replace the last known good output.
02 / How it works
Read endpoint subscriptions from Secrets or managed HTTP sources. Normalize connections and retain source provenance.
Probe through gateways for specific destinations. Keep revision-aware history and account for the freshness of evidence.
Choose an eligible set using static, lowest-latency, or adaptive Top-N strategies, with hysteresis, cooldown, and failure replacement.
Render engine-native configuration, validate it, and safely publish the new generation. Preserve the last known good output on failure.
EgressFox decides which validated configuration should exist. Mihomo and sing-box are the data plane: they implement protocols and move traffic. Adaptive selection uses a deterministic policy over observations.
03 / Kubernetes configuration
A ProxyPool reads an endpoint subscription and a probe target
from Secrets. Adaptive selection maintains up to two eligible endpoints.
An EgressGateway references the pool and opts into managed
mode. The namespace-scoped operator creates one authenticated SOCKS5
ClusterIP Service. Applications explicitly configure that proxy.
Create the referenced Secrets through your own secret management workflow. This example is an API illustration; it requires an installed operator and a qualified runtime build.
Explore the samplesapiVersion: egressfox.io/v1alpha1
kind: ProxyPool
metadata:
name: external-api
spec:
sources:
- id: primary
secretRef: {name: endpoint-subscription, key: nodes}
format: URIList
probe:
targetSecretRef: {name: external-api-probe, key: url}
expectedStatus: 204
selection: {strategy: Adaptive, topN: 2}
refreshInterval: 5m
---
apiVersion: egressfox.io/v1alpha1
kind: EgressGateway
metadata:
name: external-api
spec:
poolRef: {name: external-api}
engine: SingBox
runtime:
managed: {}
04 / Project status
Core functionality is implemented. Public releases, API stability, and production readiness are not yet guaranteed. Breaking changes may occur.
Secret and managed HTTP sources, bounded refresh with protected cache, destination-specific probes, and SQLite observation history.
Static, lowest-latency, and adaptive Top-N selection. Named target profiles share one inventory while keeping their own evidence and selected sets.
Exact Mihomo 1.19.31 and sing-box-compatible 1.14.1 profiles, native validation, and last-known-good preservation.
Namespace-scoped operator and Helm chart, managed or bring-your-own runtimes, scoped RBAC, and distinct published and active generations.
M1–M6 core and BYO operator, M7 managed gateway and activation, M8 resilient HTTP refresh, M8.5 bounded protocol compatibility, and M9 target-aware selection profiles are complete for their documented scope.
M10 bounded routing policy is next, followed by M11 operational metrics and M12 explainability and P1 acceptance.
Follow the roadmap05 / Documentation
Kubernetes setup, managed gateways, and BYO operation.
Completed milestones, current priorities, and later horizons.
The contracts and tradeoffs behind the control plane.
Trust boundaries, implemented controls, and residual risks.
Supported versions and confidential vulnerability reporting.
Artifact verification, checksums, SBOMs, and provenance.
06 / About & contact
EgressFox combines a Kubernetes-independent Go core with a namespace-scoped operator.
I maintain EgressFox and its technical direction, from architecture and compatibility decisions to contribution reviews, release preparation, and documentation. The code and design decisions are developed in the open under the EgressFox GitHub organization.
Maintainer responsibilitiesFor reproducible bugs and feature proposals, use GitHub Issues. For sensitive reports, follow the security policy.