linkerd
/
linkerd2
mirror of https://github.com/linkerd/linkerd2.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc update to remove extra configurations for websockets (#1180) 

* doc update to remove extra configurations for websockets and HTTP tunneling:
- remove instructions from readme and docs to set extra configs for websockets and  HTTP tunneling, since proxy upgrades automatically

Signed-off-by: Franziska von der Goltz <franziska@vdgoltz.eu>
This commit is contained in:
Franziska von der Goltz 2018-07-05 10:20:35 -07:00 committed by GitHub
parent a17177f73d
commit 9bf549b5ff
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@ -10,10 +10,9 @@ 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][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.
Conduit is **alpha**. It is capable of proxying all TCP traffic, including
websockets and HTTP tunneling, and reporting top-line metrics (success rates,
latencies, etc) for all HTTP, HTTP/2, and gRPC traffic.
## Get involved

16
doc/adding-your-service.md
View File

@ -43,22 +43,6 @@ part. To accomplish this, Conduit automatically detects the protocol used on
each connection. In some cases, however, Conduit's protocol detection can't be
fully automated and requires some configuration from you.
### HTTP Tunneling and WebSockets
Most HTTP traffic (including HTTP/2) will be handled automatically and
transparently by Conduit without any configuration on your part. However,
non-HTTPS WebSockets and HTTP tunneling/proxying (use of the HTTP `CONNECT`
method) currently require manual configuration to disable the layer 7 features
for those connections. For pods that accept incoming `CONNECT` requests and/or
incoming WebSocket connections, use the `--skip-inbound-ports` flag when running
`conduit inject`. For pods that make outgoing `CONNECT` requests and/or outgoing
WebSocket connections, use the `--skip-outbound-ports` flag when running
`conduit inject`. (Automatic transparent proxying of WebSockets will be
implemented in a [future release](https://github.com/runconduit/conduit/issues/195).)
### For example, to allow inbound traffic on ports 80 and 7777 to bypass the proxy, use the command:
#### `conduit inject deployment.yml --skip-inbound-ports=80,7777 | kubectl apply -f -`
### MySQL and SMTP
Most non-HTTP traffic will also be handled automatically and transparently by