Skip to content
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

[feat] automatic pre-seeding of resolver-addresses pointing to system nameservers #6975

Open
defanator opened this issue Dec 12, 2024 · 2 comments
Labels
proposal An issue that proposes a feature request

Comments

@defanator
Copy link
Contributor

Is your feature request related to a problem? Please describe.

Specifying resolver-addresses manually for every NIC deployment could be challenging in modern containerized world.

Describe the solution you'd like

A way to populate resolver directive with nameservers from system/pod, as it's done e.g. in official nginx docker images: https://github.com/nginxinc/docker-nginx/blob/master/entrypoint/15-local-resolvers.envsh

(something like resolver-addresses: auto ?)

Describe alternatives you've considered

Adding resolver-addresses to corresponding ConfigMaps after initial deploying of NIC, once all deployments + pods are created and nameservers could be pulled from /etc/resolv.conf of a corresponding installation.

Additional context

N/A

@defanator defanator added the proposal An issue that proposes a feature request label Dec 12, 2024
Copy link

Hi @defanator thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!

@defanator
Copy link
Contributor Author

Also, with recent auto re-resolving support in nginx/foss, the resolver-addresses should be supported for NIC with nginx/foss installations as well: https://blog.nginx.org/blog/dynamic-dns-resolution-open-sourced-in-nginx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal An issue that proposes a feature request
Projects
Status: Todo ☑
Development

No branches or pull requests

1 participant