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.
conduit statworks on many Kubernetes resources.
- Per-authority HTTP stats.
- TCP-level stats
conduit tapworks on many Kubernetes resources, too.
- Grafana dashboards for Kubernetes Pods, Services, & Replication Controllers.
- 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
- Stable Service Discovery semantics.
- Latency-aware load balancing.
conduit wtf: what’s the failure?
Early June 2018
- Explicitly configured TLS for ingress
- Server Name Indication (SNI)
- Scales to many cores.
- High-availability controller
- Helm integration
- Mutual authentication
- Key rotation
- Let’s Encrypt Ingress support
- Automatic alerting for latency & success objectives
- Controllable retry policies
- OpenTracing integration
- Pluggable authorization policy
- Failure injection
- Speculative retries
- Dark traffic
- gRPC payload-aware
- Automated red-line testing