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

clarify unmentioned constraint port.name equalness (cherry-pick #11680) (#11891) 

* doc the port name should be same

* namespace sameness, accept craigbox's suggestion
This commit is contained in:
tedli 2022-11-11 11:40:44 +08:00 committed by GitHub
parent 69981b01b1
commit db3731fe20
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/en/docs/reference/glossary/namespace-sameness.md
View File

@ -6,4 +6,6 @@ test: n/a
Within a multicluster mesh, [namespace sameness](https://github.com/kubernetes/community/blob/master/sig-multicluster/namespace-sameness-position-statement.md) Within a multicluster mesh, [namespace sameness](https://github.com/kubernetes/community/blob/master/sig-multicluster/namespace-sameness-position-statement.md)
applies and all namespaces with a given name are considered to be the same namespace. If multiple clusters contain a applies and all namespaces with a given name are considered to be the same namespace. If multiple clusters contain a
`Service` with the same namespaced name, they will be recognized as a single combined service. By default, traffic is `Service` with the same namespaced name, they will be recognized as a single combined service. By default, traffic is
load-balanced across all clusters in the mesh for a given service. load-balanced across all clusters in the mesh for a given service.
Ports that match on _number_ must also have the same port _name_ to be considered as a combined `service port`.