Support exposing DNS UDP for service #129
Merged
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
alexrashed
approved these changes
Dec 17, 2024
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.
Motivation
Currently enabling
dnsService: trueonly exposes the DNS port to the service with the TCP protocol, whereas both TCP and UDP should be exposed. DNS was originally a UDP-based protocol.Changes
Expose both TCP and UDP ports in the LocalStack deployment, if
dnsService: true.Testing
dnsService: truefrom themainbranchkubectl run -i --tty --rm debug --image ghcr.io/simonrw/docker-debug:main --restart=Never -- dig @<localstack service ip address> example.comdigtoolexample.com