This is in preparation for landing the Tokio upgrade. In order to be generic over Tokio's current thread and threadpool executors, a number of types in Conduit which were not previously `Send` are now required to be `Send`. A majority of this work will be done in the main Tokio upgrade PR, as it is in many cases not possible to make these types `Send` _without_ using the new Tokio API (in order to remove `Handle`s, etc.); however, I'm factoring out everything possible and trying to land it in separate PRs. The p2c load balancer constructed in `Outbound` is currently parameterized over a random number generator. We currently construct it by getting the thread-local RNG, and passing it to the load balancer constructor. However, the thread-local RNG is not `Send`. I've fixed this issue by creating a new zero-sized empty struct type which implements `rand::Rng` simply by calling `thread_rng()` every time its' called, and passing that to `choose::power_of_two_choices` instead. Since this is an empty type which contains no data, and the correct thread-local RNG is accessed whenever the methods are called, this new type can trivially be `Send`. According to the `rand` crate's documentation, this is the correct way to use `ThreadRng` anyway: > Retrieve the lazily-initialized thread-local random number generator, seeded > by the system. Intended to be used in method chaining style, e.g. > `thread_rng().gen::<i32>()`. > (from https://docs.rs/rand/0.4.2/rand/fn.thread_rng.html) This shouldn't lead to any functional changes. Signed-off-by: Eliza Weisman <eliza@buoyant.io> |
||
---|---|---|
.github | ||
bin | ||
cli | ||
controller | ||
doc | ||
grafana | ||
pkg | ||
proto | ||
proxy | ||
proxy-init | ||
test | ||
testutil | ||
web | ||
.dockerignore | ||
.editorconfig | ||
.gcp.json.enc | ||
.gitattributes | ||
.gitignore | ||
.prometheus.dev.yml | ||
.travis.yml | ||
BUILD.md | ||
CHANGES.md | ||
CONTRIBUTING.md | ||
Cargo.lock | ||
Cargo.toml | ||
DCO | ||
Dockerfile-base | ||
Dockerfile-go-deps | ||
Gopkg.lock | ||
Gopkg.toml | ||
LICENSE | ||
README.md | ||
TEST.md | ||
docker-compose.yml |
README.md
🎈 Welcome to Conduit! 👋
Conduit is an ultralight service mesh for Kubernetes. It features a minimalist control plane written in Go, and a native proxy data plane written in Rust that boasts the performance of C without the heartbleed.
Conduit is alpha. It is capable of proxying all TCP traffic, and reporting
top-line metrics (success rates, latencies, etc) for all HTTP, HTTP/2, and gRPC traffic.
It currently does not work with websockets or with HTTP tunneling--see the
--skip-outbound-ports
flag for how to exclude these types of traffic.
Get involved
- conduit-users mailing list: Conduit user discussion mailing list.
- conduit-dev mailing list: Conduit development discussion mailing list.
- conduit-announce mailing list: Conduit announcements only (low volume).
- Follow @RunConduit on Twitter.
- Join the #conduit channel on the Linkerd Slack.
Documentation
View Conduit docs for more a more comprehensive guide to getting started, or view the full Conduit roadmap.
Getting started with Conduit
-
Install the Conduit CLI with
curl https://run.conduit.io/install | sh
. -
Add
$HOME/.conduit/bin
to yourPATH
. -
Install Conduit into your Kubernetes cluster with:
conduit install | kubectl apply -f -
. -
Verify that the installation succeeded with
conduit check
. -
Explore the Conduit controller with
conduit dashboard
. -
Optionally, install a demo application to run with Conduit.
-
Add your own service to the Conduit mesh!
Working in this repo
BUILD.md
includes general information on how to work in this repo.
Code of conduct
This project is for everyone. We ask that our users and contributors take a few minutes to review our code of conduct.
License
Conduit is copyright 2018 Buoyant, Inc. All rights reserved.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use these files except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.