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

review comments (#9882)

This commit is contained in:
Ram Vennam 2021-06-04 11:49:15 -04:00 committed by GitHub
parent fef1fac4be
commit b815c41816
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/en/blog/2021/external-locality-failover/index.md
View File

@ -19,7 +19,7 @@ Similar to services running inside the service mesh, you can configure Istio to
## Define external endpoints using a ServiceEntry
First, determine the location of your workloads.
[Locality load balancing](/docs/tasks/traffic-management/locality-load-balancing/) works based on `region` or `zone`, which are usually inferred from labels set on the Kubernetes nodes. First, determine the location of your workloads:
{{< text bash >}}
$ kubectl describe node | grep failure-domain.beta.kubernetes.io/region
@ -29,7 +29,7 @@ $ kubectl describe node | grep failure-domain.beta.kubernetes.io/region
In this example, the GKE cluster nodes are running in `us-east1`.
Next, apply a `ServiceEntry` to create a `mydb.com` service that’s backed by the two DynamoDB endpoints. Set the `locality` of your primary endpoint to the same region as your workload.
Next, create a `ServiceEntry` which aggregates the endpoints you want to use. In this example, we have selected `mydb.com` as the host. This is the address your application should be configured to connect to. Set the `locality` of the primary endpoint to the same region as your workload:
{{< text yaml >}}
apiVersion: networking.istio.io/v1beta1