Automated backport of #3220: Add TCP port to Lighthouse CoreDNS ClusterIP service #3229
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Define TCP port in ClusterIP service to allow k8s DNS server to forward TCP connection requests. Lighthouse CoreDNS pods already support TCP on port 53. This is needed to support TCP retries after truncation per RFC1035 and RFC2181. Signed-off-by: Tony Le <[email protected]>
tpantelis
requested review from
skitt,
sridhargaddam and
vthapar
as code owners
|
🤖 Created branch: z_pr3229/tpantelis/automated-backport-of-#3220-upstream-release-0.17 |
aswinsuryan
approved these changes
Sep 17, 2024
4 tasks
yboaron
approved these changes
Sep 23, 2024
|
🤖 Closed branches: [z_pr3229/tpantelis/automated-backport-of-#3220-upstream-release-0.17] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport of #3220 on release-0.17.
#3220: Add TCP port to Lighthouse CoreDNS ClusterIP service
For details on the backport process, see the backport requests page.