51e230017e
During code review of another change I noticed that a lot of types seem to derive `Hash` (and `Eq`, `PartialEq`) even though the types should never (for performance reasons) be used as keys of a hash table, and where it is kind of questionable what equality should mean for those types. Then I noticed that similarly many types implement `Clone` even though I expect we should never be cloning them, again because of our performance goals. Because these types derive these traits, then whenever we add a field to them, that field also has to implement these traits. That means we then have to expand the problem, deriving implementations of these traits for types that don't otherwise want/need to implement these traits. This makes review complicated, because, for example, we have to decide whether something should be compared case-insensitively or case-sensitively when really we don't want to compare those things at all. To prove that we can get by by doing less, to speed up code review (particularly related to some stuff related to TLS), stop deriving `Clone`, `Eq`, `PartialEq`, and `Hash` for these types. I believe that, in particular, the change to key the Tap hash table based on request ID, instead of the whole request, should speed up the tap feature since we don't hash and/or compare every field, recursively, of requests. Later more such cleanup of this sort should be done. Signed-off-by: Brian Smith <brian@briansmith.org> |
||
|---|---|---|
| .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/binto 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.