v0.2.0
v0.2.0
This is a big milestone! With this release, Conduit adds support for HTTP/1.x and raw TCP traffic, meaning it should "just work" for most applications that are running on Kubernetes without additional configuration.
- Data plane
- Conduit now transparently proxies all TCP traffic, including HTTP/1.x and HTTP/2.
(See caveats below.)
- Conduit now transparently proxies all TCP traffic, including HTTP/1.x and HTTP/2.
- Command-line interface
- Improved error handling for the
tap
command tap
also now works with HTTP/1.x traffic
- Improved error handling for the
- Dashboard
- Minor UI appearance tweaks
- Deployments now searchable from the dashboard sidebar
Caveats:
- Conduit will automatically work for most protocols. However, applications that use WebSockets, HTTP tunneling/proxying, or protocols such as MySQL and SMTP, will require some additional configuration. See the documentation for details.
- Conduit doesn't yet support external DNS lookups. These will be addressed in an upcoming release.
- There are known issues with Conduit's telemetry pipeline that prevent it from scaling beyond a few nodes. These will be addressed in an upcoming release.
- Conduit is still experimental! Please help us by filing issues and contributing pull requests.