openshift/installer
1
0
Fork 0
mirror of https://github.com/openshift/installer.git synced 2026-02-05 06:46:36 +01:00
Code Issues Releases Activity

Merge pull request #5132 from cfergeau/libvirt-resolved

Browse Source 
libvirt docs update when systemd-resolved is in use
This commit is contained in:
OpenShift Merge Robot
2021-09-06 12:12:39 +02:00
committed by GitHub
parent 43cb6fc3bf 13d95bec67
commit a80b1ff94c
1 changed files with 19 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/dev/libvirt/README.md
View File

@@ -227,10 +227,28 @@ NOTE: When the firewall rules are no longer needed, `sudo firewall-cmd --reload`
will remove the changes made as they were not permanently added. For persistence,
add `--permanent` to the `firewall-cmd` commands and run them a second time.
### Set up NetworkManager DNS overlay
### Set up DNS
This step allows installer and users to resolve cluster-internal hostnames from your host.
#### Using systemd-resolved
If your system is using `systemd-resolved` (the default since Fedora 33), then you can setup DNS without using `dnsmasq`.
Just point `resovectl` to use `192.168.126.1` for your `baseDomain`. Replace `baseDomain` in the example accordingly.
```sh
sudo resolvectl dns tt0 192.168.126.1
sudo resolvectl domain tt0 ~<baseDomain>
```
Your cluster might run on a different network interface. To find which one it is, either check your `install-config.yaml`
or run `nmcli` and find the interface that's running the `192.168.126.0/24` net.
Please note that this is not persistent across libvirt network creation/deletion of the tt0 interface. Once the tt0 interface is deleted and recreated, it will need to be updated again with the proper resolver.
#### Using NetworkManager DNS overlay
1. Tell NetworkManager to use `dnsmasq`:
```sh