Skip to content

Conversation

@rmvangun
Copy link
Contributor

@rmvangun rmvangun commented Apr 9, 2025

Since we operate CoreDNS amongst our local development services, it seems reasonable to use it as our docker network DNS. This will eventually allow us to define hostnames and domain routing independently.

The code changes to make this possible are co-dependent on how we generate and template values in our default blueprints. As such, we now also use DNS names instead of IPs for looking up our nodes.

@rmvangun rmvangun added the enhancement New feature or request label Apr 9, 2025
@rmvangun
Copy link
Contributor Author

rmvangun commented Apr 9, 2025

Task linked: ENG-309 Use local coredns in docker network

@rmvangun rmvangun merged commit d5da8bd into main Apr 9, 2025
12 checks passed
@rmvangun rmvangun deleted the ENG-309_Use-local-coredns-in-docker-network branch April 9, 2025 15:17
rmvangun added a commit that referenced this pull request Apr 23, 2025
* Use coredns for docker network

* Don't assign localhost IPs to services

* Always assign IP addresses to services

* isLocalhost => isLocalhostMode

* Use localhost IPs for corefile entries

* Handles DNS appropriately

* Fix linux test

* Attempt linux fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants