Add DNS support to local workstation #558
Merged
Conversation
This file contains hidden or 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
Contributor
Author
|
Task linked: ENG-200 Add dns support to local workstation |
rmvangun
added a commit
that referenced
this pull request
Feb 7, 2025
* Refactor * Passing tests but lacks coverage * Fix * Test coverage * Everything works Add back network cidr block
rmvangun
added a commit
that referenced
this pull request
Apr 23, 2025
* Refactor * Passing tests but lacks coverage * Fix * Test coverage * Everything works Add back network cidr block
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.
Adds a few features to make it possible to work with DNS locally across both docker-desktop and Colima VM drivers. This includes:
nodeports=>hostportsin cluster config. This is more accurate, and reflects the forwarding of DNS ports to the hostforwardin the dns configuration. This permits pointing to upstream DNS on a cluster or leveraging private DNSLOADBALANCER_IP_STARTandLOADBALANCER_IP_END. The former is always used as the primary ingress to the cluster and is where DNS is hosteddocker-desktopandcolimaas they require different default DNS configurations