DNS resolution fails on GCE VMs
- Dominant language
- Go
- Stars
- 25
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
## Summary
DNS resolution fails on a vanilla GCE VM (related to https://github.com/coder/boundary/issues/89, https://github.com/coder/boundary/issues/108)
## Expected behavior
- [ ] Boundary should support handling DNS resolution on GCE VMs and other Google Cloud workloads (eg. GKE Pods)
- [ ] Documentation should provide a guideline how to configure the above
## Technical analysis
The metadata server's link-local IP `169.254.169.254` isn't routable from the dedicated network namespace
The solution implemented in https://github.com/coder/boundary/pull/105 isn't sufficient since it only handles following default `/etc/resolv.conf` entries:
`nameserver 127.0.0.53`
Reference:
https://docs.cloud.google.com/compute/docs/troubleshooting/troubleshoot-metadata-server#failed-request
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.