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

Grammar improvements (#4703) (#4707) 

* Cross-namespace config

* clarifications

* Fix spelling

* tweaks

* improvements

* more details

* Reference the problem from egress gateway task

* tweak

* review comments and remove broken link

* broken link

* Grammar improvements

(cherry picked from commit 8a2bcce4b8)
This commit is contained in:
mergify[bot] 2019-07-24 10:08:30 -04:00 committed by Frank Budinsky
parent 0f51f9c8a9
commit b4e3a6b17f
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
content/docs/ops/traffic-management/deploy-guidelines/index.md
View File

@ -10,12 +10,12 @@ This section provides specific deployment or configuration guidelines to avoid n
## Cross-namespace configuration sharing
A `VirtualService`, `DestinationRule`, or `ServiceEntry` configuration resource
can be defined in one namespace and then reused in other namespaces, if it is exported.
All traffic management resources are exported to all namespaces by default,
but the visibility can be overridden using the `exportTo` field.
For example, the following virtual service can only be used by clients in the same namespace
as the configuration:
You can define virtual services, destination rules, or service entries
in one namespace and then reuse them in other namespaces, if they are exported
to those namespaces.
Istio exports all traffic management resources to all namespaces by default,
but you can override the visibility with the `exportTo` field.
For example, only clients in the same namespace can use the following virtual service:
{{< text yaml >}}
apiVersion: networking.istio.io/v1alpha3
@ -34,11 +34,11 @@ spec:
{{< /text >}}
{{< tip >}}
Visibility of a Kubernetes `Service` can similarly be controlled using the `networking.istio.io/exportTo` annotation.
You can similarly control the visibility of a Kubernetes `Service` using the `networking.istio.io/exportTo` annotation.
{{< /tip >}}
The visibility of a `DestinationRule` resource in a particular namespace does not
guarantee it will be used. Exporting a destination rule to other namespaces enables it to be used
Setting the visibility of destination rules in a particular namespace doesn't
guarantee the rule is used. Exporting a destination rule to other namespaces enables you to use it
in those namespaces, but to actually be applied during a request the namespace also needs to be
on the destination rule lookup path: