-
Notifications
You must be signed in to change notification settings - Fork 574
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: add support for custom search domains #9844
Conversation
2e68dab
to
1af1f81
Compare
1af1f81
to
c09ef85
Compare
New config field `machine.network.searchDomains` supports specifying custom search domains. For the node it will look something like this: ``` nameserver 127.0.0.53 search my-custom-search-name.com my-custom-search-name2.com ``` For the pods it will look something like this: ``` search default.svc.cluster.local svc.cluster.local cluster.local my-custom-search-name.com my-custom-search-name2.com nameserver 10.96.0.10 options ndots:5 ``` Signed-off-by: Dmitriy Matrenichev <dmitry.matrenichev@siderolabs.com>
c09ef85
to
60e4561
Compare
/m |
Hi @DmitriyMV, We have the same problem with our Currently we are running our clusters in So please, is it possible to backport this feature in Thank you so much. |
@flpajany greetings! Thanks for the request. Unfortunately we do not backport changes that modify machine config or proto resources. Those backports leaves a big chance of accidentally breaking things. |
I understand. Is there a way to change the seach path for DNS resolution manually ? |
This PR is mostly about host search path in the See #9342 for discussion for K8s pods and others. |
It is exactly what I am talking about : a way to change /etc/resolv.conf and add other domains to the search path to the host. I was thinking about changing machineconfig to add something like this :
Edit : tested and not working :-( |
this won't work most probably. you can achieve the same by setting the hostname to the fqdn as well. |
I understand but unfortunatly it is complicated to do that for some applications. We'll try nonetheless to change it that way and I'll be back here to tell you the result. |
Also keep in mind that k8s pod search path is totally independent of this change. |
That would mean to rebuild container images, thing we are not able to do :-( |
Please read #9342 carefully. If you have any specific question - create a GitHub discussion with all relevant information. |
OK we'll try this too. Thx |
New config field
machine.network.searchDomains
supports specifying custom search domains.For the node it will look something like this:
For the pods it will look something like this:
Fixes #9342