Skip to content

Commit 0ade351

Browse files
committed
Address comments
Signed-off-by: Zhonghu Xu <[email protected]>
1 parent 3c4c1ea commit 0ade351

File tree

1 file changed

+5
-10
lines changed

1 file changed

+5
-10
lines changed

content/en/docs/userguide/install_waypoint.md

Lines changed: 5 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ type: docs
1111

1212
---
1313

14-
If you want to make use of kmesh L7 features, this is the prerequisites to install waypoint.
14+
If you want to make use of Kmesh L7 features, this is the prerequisites to install waypoint.
1515

1616
### Preparation
1717

@@ -69,15 +69,15 @@ sleep-9454cc476-86vgb 1/1 Running 0 62s
6969
Waypoints can be used at three granularity: namespace, service and pod. And you could also install multiple waypoints at different granularity within a namespace.
7070
Below we will learn how to deploy different waypoints for different granularity. We can use `kmeshctl waypoint` subcommands to generate or apply waypoint.
7171

72-
To enable a namespace, service or Pod to use a waypoint, add the `istio.io/use-waypoint` label with a value of the waypoint name.
72+
To enable a namespace, service or pod to use a waypoint, add the `istio.io/use-waypoint` label with a value of the waypoint name.
7373
We can also specify a customized waypoint image with `--image`, by default this default to `ghcr.io/kmesh-net/waypoint:{VERSION}`
7474

7575
#### Configure a waypoint for a specific service:
7676

77-
Deploy a waypoint `reviews-svc-waypoint` for service `reviews`, so any traffic to `reviews` from a client managed by kmesh will be mediated by the waypoint proxy
77+
Deploy a waypoint `reviews-svc-waypoint` for service `reviews`, so any traffic to `reviews` from a client managed by Kmesh will be mediated by the waypoint proxy
7878

7979
```bash
80-
[root@ ~]# kmeshctl waypoint generate --for service -n default --name=reviews-svc-waypoint
80+
[root@ ~]# kmeshctl waypoint apply --for service -n default --name=reviews-svc-waypoint
8181

8282
waypoint default/reviews-svc-waypoint applied
8383
```
@@ -108,7 +108,7 @@ sleep-5577c64d7c-n7rxp 1/1 Running 0 30m
108108

109109
#### Configure waypoint for a specific namespace:
110110

111-
Deploy a waypoint for the `default` with default name `waypoint`. By specifying `--enroll-namespace`, the namespace will be labeled with `istio.io/use-waypoint=waypoint`
111+
Deploy a waypoint for the `default` namespace with default name `waypoint`. By specifying `--enroll-namespace`, the namespace will be labeled with `istio.io/use-waypoint=waypoint`
112112

113113
```bash
114114
[root@ ~]# kmeshctl waypoint apply -n default --enroll-namespace
@@ -128,11 +128,6 @@ waypoint default/reviews-v2-pod-waypoint applied
128128
pod/reviews-v2-5b667bcbf8-spnnh labeled
129129
```
130130

131-
***NOTE: If you need to replace the original image of waypoint with the Kmesh customized image.***
132-
133-
```bash
134-
[root@ ~]# kubectl annotate gateway reviews-v2-pod-waypoint sidecar.istio.io/proxyImage=ghcr.io/kmesh-net/waypoint:latest
135-
```
136131
Now any requests from pods in the Kmesh to the `reviews-v2` pod IP will be routed through `reviews-v2-pod-waypoint` waypoint for L7 processing and policy enforcement.
137132

138133
### Cleanup

0 commit comments

Comments
 (0)