expand/awx-on-k3s
1
0
Fork 0
mirror of https://github.com/Expand-sys/awx-on-k3s synced 2025-12-16 14:02:15 +11:00
Code Issues Projects Releases Packages Wiki Activity Actions

fix: fix tips for name resolution

Browse source
This commit is contained in:
kurokobo 2021-08-29 12:57:30 -04:00
parent c7da8f71e6
commit 7f9bb3b237
1 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
tips/expose-hosts.md
View file

@ -28,7 +28,9 @@ One easy way to do this is to use `dnsmasq`.
3. Create new `resolv.conf` to use K3s. Note that the IP addresses have to be replaced with your K3s host's one. 3. Create new `resolv.conf` to use K3s. Note that the IP addresses have to be replaced with your K3s host's one.
```bash ```bash
sudo echo "nameserver 192.168.0.100" > /etc/rancher/k3s/resolv.conf sudo tee /etc/rancher/k3s/resolv.conf <<EOF
nameserver 192.168.0.100
EOF
``` ```
4. Add `--resolv-conf /etc/rancher/k3s/resolv.conf` as an argument for `k3s server` command. 4. Add `--resolv-conf /etc/rancher/k3s/resolv.conf` as an argument for `k3s server` command.
@ -47,6 +49,7 @@ One easy way to do this is to use `dnsmasq`.
5. Restart K3s and CoreDNS. The K3s service can be safely restarted without affecting the running resources. 5. Restart K3s and CoreDNS. The K3s service can be safely restarted without affecting the running resources.
```bash ```bash
sudo systemctl daemon-reload
sudo systemctl restart k3s sudo systemctl restart k3s
kubectl -n kube-system delete pod -l k8s-app=kube-dns kubectl -n kube-system delete pod -l k8s-app=kube-dns
``` ```