-
Epic
-
Resolution: Done
-
Major
-
None
-
Document and test current Gateway API dns feature
-
Product / Portfolio Work
-
-
0% To Do, 0% In Progress, 100% Done
-
False
-
-
False
-
Green
-
M
-
None
-
None
-
5
-
0
Use cases:
- As a customer I would like to understand how and when DNS records are created for my Gateway API resources.
- As a developer I would like to fix any issues that are not acceptable, or document those that cannot be resolved.
See
Enhancement Proposal - new controller to manage dns records for gateway listeners]
Write and run unit test cases to find answers to the following about the current Gateway API DNS reconciliation:
- Does it work with multiple Gateways? Create multiple Gateways that have listeners with same hostname, as well as with differing hostnames and test DNS flow.
- What happens for a Gateway with Listeners that don't have a hostname?
Does it ignore Services that are not associated with the Gateway controller?- What happens if a Gateway listener tries to claim a name (abc.apps.example.com) that would match a *.apps.example.com ingress controller wildcard. Which endpoint tries to serves the request to abc.apps.example.com?
- Other important factors TBD.
Acceptance Criteria: new unit test cases, documentation, and update to enhancement document if needed.
- is related to
-
OCPBUGS-8526 GWAPI doesn't create DNS records for Gateways that are manually linked
-
- Closed
-
- links to