As a developer using NKG in a cluster with many subdomains
I want to specify a hostname using a wildcard label for my Gateway Listener
So that I can use a single entry to listen for all my subdomains without needing configuration changes when I add another.
Acceptance
"Hostnames that are prefixed with a wildcard label (.) are interpreted as a suffix match. That means that a match for .example.com would match both test.example.com, and foo.test.example.com, but not example.com."
Wildcard hostname matching should exactly match the implementation for hostname matching under HTTP Route.
mpstefan
commented
1 year ago
As a developer using NKG in a cluster with many subdomains I want to specify a hostname using a wildcard label for my Gateway Listener So that I can use a single entry to listen for all my subdomains without needing configuration changes when I add another.
Acceptance
Wildcard story for HTTP Route Kubernetes Gateway specification for Listener