From 4e27cd8ff5155f4973cf2b5570898f6dcda74fac Mon Sep 17 00:00:00 2001 From: Chen Chen Date: Fri, 25 Jul 2025 12:42:35 +0800 Subject: [PATCH] [OCPBUGS-59795] Swap the order of troubleshooting nmstate DNS connectivity --- ...e-troubleshooting-dns-disconnected-env-resolv.adoc | 11 ++++++----- .../k8s-nmstate-troubleshooting-node-network.adoc | 6 +++--- 2 files changed, 9 insertions(+), 8 deletions(-) diff --git a/modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc b/modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc index 33e89e019a27..b164f84547fa 100644 --- a/modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc +++ b/modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc @@ -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] ---- @@ -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 `` 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 .yaml +$ oc edit nmstate nmstate ---- diff --git a/networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.adoc b/networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.adoc index aa7d0dc6ec60..68c64b2c2abf 100644 --- a/networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.adoc +++ b/networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.adoc @@ -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] \ No newline at end of file