Add noble DNS ops file for warden/bosh-lite deployments#512
Conversation
On warden containers, systemd-resolved has no DHCP-provided upstream DNS because warden does not configure DNS in the container network namespace. With disable_recursors=true (the noble default), all external DNS queries fail with REFUSED or SERVFAIL. Add warden/noble-dns.yml which overrides the bosh-dns-systemd addon to: - set disable_recursors=false so bosh-dns forwards external queries - set recursors=[169.254.169.254] as the explicit upstream (the link-local metadata DNS available on GCP, AWS and Azure) Apply the ops file in virtualbox/create-env.sh and both warden/docker CI tasks which deploy noble stemcells on warden. Co-authored-by: Saumya Dudeja <saumya.dudeja@sap.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (4)
WalkthroughA new ops file, 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
On warden containers, systemd-resolved has no DHCP-provided upstream DNS because warden does not configure DNS in the container network namespace. With disable_recursors=true (the noble default), all external DNS queries fail with REFUSED or SERVFAIL.
Add warden/noble-dns.yml which overrides the bosh-dns-systemd addon to:
Apply the ops file in virtualbox/create-env.sh and both warden/docker CI tasks which deploy noble stemcells on warden.
Note: Please create PR's against the develop branch