-
Bug
-
Resolution: Done
-
Minor
-
4.13.z, 4.12.z, 4.14.z, 4.15.z, 4.17.z, 4.16.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
5
-
None
-
None
-
None
-
None
-
None
-
OSDOCS Sprint 266
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
An Ingress Controller can use three sharding methods:
Adding only a namespace selector to the Ingress Controller, so that all routes in a namespace with labels that match the namespace selector are in the Ingress shard.
Adding only a route selector to the Ingress Controller, so that all routes with labels that match the route selector are in the Ingress shard.
Adding both a namespace selector and route selector to the Ingress Controller, so that routes with labels that match the route selector in a namespace with labels that match the namespace selector are in the Ingress shard.
The last sentence is very hard to understand for the customers. That means that there is an "AND" function between router and namespace labels for sharding.
Request you to add a table with examples of how the router sharding is working?
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
- links to
(3 links to)