Skip to content

[OCPBUGS-59795] Swap the order of troubleshooting nmstate DNS connectivity #96689

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.

Sign up for GitHub

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

Closed
cchen666 wants to merge 1 commit into from
Closed

[OCPBUGS-59795] Swap the order of troubleshooting nmstate DNS connectivity #96689

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,11 @@
[id="k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc_{context}"]
= Creating a custom DNS host name to resolve DNS connectivity issues

In a disconnected environment where the external DNS server cannot be reached, you can resolve Kubernetes NMState Operator health probe issues by specifying a custom DNS host name in the `NMState` custom resource definition (CRD).
In a disconnected environment where the external DNS server cannot be configured, you can resolve Kubernetes NMState Operator health probe issues by specifying a custom DNS host name in the `NMState` custom resource definition (CRD).

.Procedure

. Add the DNS host name configuration to the `NMState` CRD of your cluster:
. Replace the DNS host name with your own resolvable hostname in the `NMState` CRD of your cluster:
+
[source,yaml]
----
Expand All @@ -21,15 +21,16 @@ metadata:
spec:
probeConfiguration:
dns:
host: redhat.com
host: redhat.com <1>
# ...
----
<1> The hostname that can be successfully resolved in your own DNS server

. Apply the DNS host name configuration to your cluster network by running the following command. Ensure that you replace `<filename>` with the name of your CRD file.
. To change the hostname, edit the DNS host name configuration to your cluster network by running the following command.
+
[source,yaml]
----
$ oc apply -f <filename>.yaml
$ oc edit nmstate nmstate
----


Expand Down
6 changes: 3 additions & 3 deletions networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,8 +20,8 @@ include::modules/virt-troubleshooting-incorrect-policy-config.adoc[leveloffset=+
// Troubleshooting DNS connectivity issues in a disconnected environment
include::modules/k8s-nmstate-troubleshooting-dns-disconnected-env.adoc[leveloffset=+1]

// Configuring the dnsmasq DNS server
include::modules/k8s-nmstate-troubleshooting-dns-disconnected-env-dnsmasq.adoc[leveloffset=+2]

// Creating a custom DNS host name to resolve DNS connectivity issues
include::modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc[leveloffset=+2]

// Configuring the dnsmasq DNS server
include::modules/k8s-nmstate-troubleshooting-dns-disconnected-env-dnsmasq.adoc[leveloffset=+2]