This is the planned roadmap for Conduit. Of course, as with any software project (especially open source) even the best of plans change rapidly as development progresses.
Our goal is to get Conduit to production-readiness as rapidly as possible with a minimal featureset, then to build functionality out from there. We’ll make alpha / beta / GA designations based on actual community usage, and generally will err on the side of being overly conservative.
Late February 2018
- Stable, automatic top-line metrics for small-scale clusters.
- Routing to external DNS names
- Least-loaded L7 load balancing
- Improved error handling
- Improved egress support
- Published (this) public roadmap
- All milestones, issues, PRs, & mailing lists made public
Late March 2018
- Helm integration
- Mutating webhook admission controller
- Self-bootstrapping Certificate Authority
- Secured communication to and within the Conduit control plane
- Automatically provide all meshed services with cryptographic identity
- Automatically secure all meshed communication
- Enhanced server-side metrics, including per-path and per-status-code counts & latencies.
- Client-side metrics to surface egress traffic, etc.
- Latency-aware load balancing
Early April 2018
- Controllable latency objectives to configure timeouts
- Controllable response classes to inform circuit breaking, retryability, & success rate calculation
- High-availability controller
- OpenTracing integration
- Mutual authentication
- Key rotation
Late April 2018
- Automatic alerting for latency & success objectives
- Controllable retry policies
- Rich ingress routing
- Contextual route overrides
- Authorization policy
- Controller policy plugins
- Support for non-Kubernetes services
- Failure injection (aka “chaos chihuahua”)
- Speculative retries
- Dark traffic
- gRPC payload-aware
- Automated red-line testing