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
Ingress DNS documentation lacks instruction for Linux OS systemd-resolved (relevant to Ubuntu) #18727
Comments
Bare in mind that will not work for for everyone, for example on MacOSX you need to create a resolver for the domain you want. On top I think configuring the systemd-resolve tool to add entries is straightforward. I think what requires update is the fact that still it's referencing on the documentation to edit /etc/resolve.conf and in no *nix based system that file is now self managed. Is automatically generated. That needs to be maybe remarked. |
you need to restart systemd-resolved after that . |
if this step is required for the linux users, we should consider to add this to the Addon itself, maybe to add this step automatically, what do you think ? |
@medyagh: this step is not required for all linux users, but depends on the system's DNS configuration. Here are the steps one should follow to address step 3 "Add the
The current documentation does not explain clearly that one needs (1) to identify the DNS config, and (2) only apply the instructions for this config. Automation sounds difficult and risk having unexpected consequences, as it would need correctly to handle any possible DNS configuration. (There is a related TODO on the same page.) I think it outside of the scope o this issue. I will update the PR with @medyagh's comments and clarify the issues raised above (identify the right setup, and start minikube before applying the modifications). |
The Ingress DNS documentation has instruction for adding the
minikube ip
as a DNS server ("Installlation", step 3). Under the Linux tab, it provides instructions to do so for systems usingresolvconf
andNetwork Manager
, but notsystemd-resolved
. This is relevant because it seems to be used by Ubuntu>=22.04 (/etc/resolv.conf
starts with# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
)On systems using
systemd-resolved
, the minikube IP can be added by running:I propose to create a PR to add this to the documentation.
The text was updated successfully, but these errors were encountered: