1464470487
Problem If you navigate directly to (or do a hard refresh on) a path with more than one segment, e.g. http://localhost:8084/namespaces/conduit, the dashboard js is not served. Pages with two paths have to be accessed by loading the dashboard on a different path and then clicking through. When accessing the dashboard via conduit dashboard we append a path prefix so that we can connect using the k8s proxy. This means that moving the dashboard to serve images off relative paths won't work, because we need to serve images whether the dashboard is loaded from http://localhost:8084/namespaces/conduit or from http://localhost:8084/namespaces. Solution Check whether we're serving the dashboard with the proxy url, and if we are, adjust the url at which we serve the index bundle from. I've also added a very manual override if the conduit logo can't be found at the usual url. |
||
|---|---|---|
| .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.