fix: use bastion nameserver in /etc/resolv.conf

Bastion's /etc/resolv.conf file should use its own nameserver variables instead of the cluster nameserver variables. Which are sometimes different.
IBM · Feb 10, 2023 · 94166bc · 94166bc
1 parent cbaf162
commit 94166bc
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/roles/dns/templates/resolv.conf.j2 b/roles/dns/templates/resolv.conf.j2
@@ -1,3 +1,3 @@
 search {{ env.cluster.networking.metadata_name }}.{{ env.cluster.networking.base_domain }}
-nameserver {{ env.cluster.networking.nameserver1 }}
-{{ ('nameserver ' + env.cluster.networking.nameserver2) if env.cluster.networking.nameserver2 is defined else '' }}
+nameserver {{ env.bastion.networking.nameserver1 }}
+{{ ('nameserver ' + env.bastion.networking.nameserver2) if env.bastion.networking.nameserver2 is defined else '' }}