-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Fix DNS port mapping in localstack.dev.kubernetes #13361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 2h 40m 43s ⏱️ Results for commit e384768. |
cloutierMat
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am curious to know where you experienced the issue? I don't see an issue with it, but I was able to start the cluster and pass the tests with both. Is it OS dependant?
Could be OS dependant. The dns resolution in tests was hanging for me in the double mapping scenario. |
Thanks for the extra context. Glad you found a mapping that works for everyone 👍 |
Motivation
Fixes a bug with
localstack.dev.kubernetesnot exposing the DNS port properly.K3d was failing to map both ports, resulting in failures with DNS resolution.
Changes
Replaces two protocol-specific DNS port entries with a single one.
Tests
Following the instructions of this script
python -m localstack.dev.kubernetes --pro --write --expose-dnsAnd then running pro tests that require DNS should be successful
Related