2.9 KiB
| slug | title | author | date | draft | featured | thumbnail | tags | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| announcing-conduit-0-3-conduit-roadmap | Announcing Conduit 0.3 and the Conduit Roadmap | william | Wed, 21 Feb 2018 20:47:41 +0000 | false | false | /uploads/version_conduit_030.png |
|
Conduit is now part of Linkerd! [Read more >]({{< ref "conduit-0-5-and-the-future" >}})
Today we’re very happy to announce the release of Conduit 0.3! With this release, Conduit moves from experimental to alpha---meaning that we’re ready for some serious testing and vetting from you. Full release notes are here.
Conduit 0.3 focuses heavily on production hardening of Conduit’s telemetry system, which automatically measures and aggregates service-level success rates, latency distributions, and request volumes. Conduit should “just work” for most apps on Kubernetes 1.8 or 1.9 without configuration, and should support Kubernetes clusters with hundreds of services, thousands of instances, and hundreds of RPS per instance. Conduit publishes top-line metrics for most HTTP/1.x and gRPC services without any configuration, and if you have your own Prometheus cluster, you can now also export those metrics to it directly.
Conduit 0.3 also features load aware request-level load balancing, by which Conduit automatically sends requests to service instances with the fewest pending requests. This should improve application performance compared to the default layer 4 load balancing in Kubernetes, especially for applications under load.
Most importantly, as of 0.3, we’re opening up Conduit development and planning. We’ve published the much-requested Conduit roadmap, and we’re tracking upcoming issues and milestones in GitHub. We’ve also launched new mailing lists: conduit-users, conduit-dev, and conduit-announce, which we’ll be using to plan and coordinate Conduit development.
We hope these changes will make it even easier to get involved. If you want to participate, please subscribe to the mailing lists above, get familiar with the Conduit README, and check out the GitHub issues marked “help wanted”!
Finally, while Conduit is now in alpha, we don’t expect it to stay that way for long. We’re making a concerted effort to make Conduit production-ready as rapidly as possible. Of course, this all depends on you. Try Conduit on your own Kubernetes apps, give us feedback, and help us get there!