Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions linkerd.io/content/2-edge/tasks/managing-egress-traffic.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ Now SSH into the client container and start generating some external traffic:

```bash
kubectl -n egress-test exec -it client -c client -- sh
$ while sleep 1; do curl -s http://httpbin.org/get ; done
$ while sleep 1; do curl -s https://httpbin.org/get ; done
```

In a separate shell, you can use the Linkerd diagnostics command to visualize
Expand Down Expand Up @@ -458,7 +458,7 @@ Now let's verify all works as expected:

```bash
# plaintext traffic goes as expected to the /get path
$ curl http://httpbin.org/get
$ curl https://httpbin.org/get
{
"args": {},
"headers": {
Expand All @@ -468,7 +468,7 @@ $ curl http://httpbin.org/get
"X-Amzn-Trace-Id": "Root=1-674599d4-77a473943844e9e31844b48e"
},
"origin": "51.116.126.217",
"url": "http://httpbin.org/get"
"url": "https://httpbin.org/get"
}

# encrypted traffic can target all paths and hosts
Expand All @@ -479,7 +479,7 @@ $ curl https://httpbin.org/ip


# arbitrary unencrypted traffic goes to the internal service
$ curl http://google.com
$ curl https://google.com
{
"requestUID": "in:http-sid:terminus-grpc:-1-h1:80-190120723",
"payload": "You cannot go there right now"}
Expand Down
8 changes: 4 additions & 4 deletions linkerd.io/content/2.17/tasks/managing-egress-traffic.md
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ Now SSH into the client container and start generating some external traffic:

```bash
kubectl -n egress-test exec -it client-xxx -c client -- sh
$ while sleep 1; do curl -s http://httpbin.org/get ; done
$ while sleep 1; do curl -s https://httpbin.org/get ; done
```

In a separate shell, you can use the Linkerd diagnostics command to visualize
Expand Down Expand Up @@ -413,7 +413,7 @@ Now let's verify all works as expected:

```bash
# plaintext traffic goes as expected to the /get path
$ curl http://httpbin.org/get
$ curl https://httpbin.org/get
{
"args": {},
"headers": {
Expand All @@ -423,7 +423,7 @@ $ curl http://httpbin.org/get
"X-Amzn-Trace-Id": "Root=1-674599d4-77a473943844e9e31844b48e"
},
"origin": "51.116.126.217",
"url": "http://httpbin.org/get"
"url": "https://httpbin.org/get"
}

# encrypted traffic can target all paths and hosts
Expand All @@ -434,7 +434,7 @@ $ curl https://httpbin.org/ip


# arbitrary unencrypted traffic goes to the internal service
$ curl http://google.com
$ curl https://google.com
{
"requestUID": "in:http-sid:terminus-grpc:-1-h1:80-190120723",
"payload": "You cannot go there right now"}
Expand Down
8 changes: 4 additions & 4 deletions linkerd.io/content/2.18/tasks/managing-egress-traffic.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ Now SSH into the client container and start generating some external traffic:

```bash
kubectl -n egress-test exec -it client -c client -- sh
$ while sleep 1; do curl -s http://httpbin.org/get ; done
$ while sleep 1; do curl -s https://httpbin.org/get ; done
```

In a separate shell, you can use the Linkerd diagnostics command to visualize
Expand Down Expand Up @@ -458,7 +458,7 @@ Now let's verify all works as expected:

```bash
# plaintext traffic goes as expected to the /get path
$ curl http://httpbin.org/get
$ curl https://httpbin.org/get
{
"args": {},
"headers": {
Expand All @@ -468,7 +468,7 @@ $ curl http://httpbin.org/get
"X-Amzn-Trace-Id": "Root=1-674599d4-77a473943844e9e31844b48e"
},
"origin": "51.116.126.217",
"url": "http://httpbin.org/get"
"url": "https://httpbin.org/get"
}

# encrypted traffic can target all paths and hosts
Expand All @@ -479,7 +479,7 @@ $ curl https://httpbin.org/ip


# arbitrary unencrypted traffic goes to the internal service
$ curl http://google.com
$ curl https://google.com
{
"requestUID": "in:http-sid:terminus-grpc:-1-h1:80-190120723",
"payload": "You cannot go there right now"}
Expand Down
8 changes: 4 additions & 4 deletions linkerd.io/content/2.19/tasks/managing-egress-traffic.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ Now SSH into the client container and start generating some external traffic:

```bash
kubectl -n egress-test exec -it client -c client -- sh
$ while sleep 1; do curl -s http://httpbin.org/get ; done
$ while sleep 1; do curl -s https://httpbin.org/get ; done
```

In a separate shell, you can use the Linkerd diagnostics command to visualize
Expand Down Expand Up @@ -458,7 +458,7 @@ Now let's verify all works as expected:

```bash
# plaintext traffic goes as expected to the /get path
$ curl http://httpbin.org/get
$ curl https://httpbin.org/get
{
"args": {},
"headers": {
Expand All @@ -468,7 +468,7 @@ $ curl http://httpbin.org/get
"X-Amzn-Trace-Id": "Root=1-674599d4-77a473943844e9e31844b48e"
},
"origin": "51.116.126.217",
"url": "http://httpbin.org/get"
"url": "https://httpbin.org/get"
}

# encrypted traffic can target all paths and hosts
Expand All @@ -479,7 +479,7 @@ $ curl https://httpbin.org/ip


# arbitrary unencrypted traffic goes to the internal service
$ curl http://google.com
$ curl https://google.com
{
"requestUID": "in:http-sid:terminus-grpc:-1-h1:80-190120723",
"payload": "You cannot go there right now"}
Expand Down