feat: Gateway Discovery produce DNS names instead of IP addresses #4044
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
This changes the implementation Gateway Discovery in a way that it now produces DNS names instead of IP address of Kong's pods.
There are 2 formats that this implementation can use:
pod-ip-address.service-name.my-namespace.svc
- when a Kong'sEndpointSlice
that we're trying to convert into an address (that will be used for sending the configuration) contains an owner reference of typeService
then we use that reference to build the DNS namepod-ip-address.my-namespace.pod
when thatService
owner reference is missingRef: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/
Which issue this PR fixes:
Closes: #3934
Special notes for your reviewer:
This will be required for Kong Gateway Operator to use TLS verification.
PR Readiness Checklist:
Complete these before marking the PR as
ready to review
:CHANGELOG.md
release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR