Skip to content

Commit 929ac8c

Browse files
committed
Fix lints
Signed-off-by: Mikhail Krinkin <[email protected]>
1 parent 7f41ec6 commit 929ac8c

File tree

2 files changed

+5
-4
lines changed

2 files changed

+5
-4
lines changed

content/en/docs/ambient/install/multicluster/_index.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,8 @@ the current state and limitations of this feature.
6464
#### Load Distribution on Remote Network
6565

6666
**Traffic going to a remote network is not equally distributed between endpoints**
67-
- This can lead to "lasering" an endpoint when failing over to a remote network
67+
- When failover to a remote network due to multiplexing of HTTP requests and connection pooling a single endpoint
68+
on remote network may get a disproportionate number of requests
6869
- The solution to this issue is tracked [here](https://github.com/istio/istio/issues/58039)
6970

7071
#### Gateway Limitations

content/en/docs/ambient/install/multicluster/failover/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ prev: /docs/ambient/install/multicluster/verify
99
---
1010
Follow this guide to customize failover behavior in your ambient multicluster Istio installation using waypoint proxies.
1111

12-
Before proceeding, be sure to complete ambient multicluster Istio installtion following one of the
12+
Before proceeding, be sure to complete ambient multicluster Istio installation following one of the
1313
[multicluster installation guides](/docs/ambient/install/multicluster) and verify that the installation is working properly.
1414

1515
In this guide, we will build on top of the `HelloWorld` application used to verify the multicluster installation. We will
@@ -131,7 +131,7 @@ Send request from the `curl` pods on `cluster1` to the `HelloWorld` service:
131131

132132
{{< text bash >}}
133133
$ kubectl exec --context "${CTX_CLUSTER1}" -n sample -c curl \
134-
"$(kubectl get pod --context "{CTX_CLUSTER1}" -n sample -l \
134+
"$(kubectl get pod --context "${CTX_CLUSTER1}" -n sample -l \
135135
app=curl -o jsonpath='{.items[0].metadata.name}')" \
136136
-- curl -sS helloworld.sample:5000/hello
137137
{{< /text >}}
@@ -149,7 +149,7 @@ Similarly, send request from `curl` pods on `cluster2` several times:
149149

150150
{{< text bash >}}
151151
$ kubectl exec --context "${CTX_CLUSTER2}" -n sample -c curl \
152-
"$(kubectl get pod --context "{CTX_CLUSTER2}" -n sample -l \
152+
"$(kubectl get pod --context "${CTX_CLUSTER2}" -n sample -l \
153153
app=curl -o jsonpath='{.items[0].metadata.name}')" \
154154
-- curl -sS helloworld.sample:5000/hello
155155
{{< /text >}}

0 commit comments

Comments
 (0)