Skip to content

[enterprise-4.17]OSDOCS-16361: Added new verification command to k8s-nmstate-deploying… #100271

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

Merged
merged 1 commit into from
Oct 9, 2025
Merged

[enterprise-4.17]OSDOCS-16361: Added new verification command to k8s-nmstate-deploying… #100271

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
35 changes: 33 additions & 2 deletions modules/k8s-nmstate-deploying-nmstate-CLI.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,6 @@ You can install the Kubernetes NMState Operator by using the OpenShift CLI (`oc)
.Prerequisites

* You have installed the OpenShift CLI (`oc`).

* You are logged in as a user with `cluster-admin` privileges.

.Procedure
Expand Down Expand Up @@ -46,6 +45,7 @@ spec:
- openshift-nmstate
EOF
----

. Subscribe to the `nmstate` Operator:
+
[source,terminal]
Expand Down Expand Up @@ -85,7 +85,38 @@ metadata:
EOF
----

. Verify that all pods for the NMState Operator are in a `Running` state by entering the following command:
. If your cluster has problems with the DNS health check probe because of DNS connectivity issues, you can add the following DNS host name configuration to the `NMState` CRD to build in health checks that can resolve these issues:
+
[source,terminal]
----
apiVersion: nmstate.io/v1
kind: NMState
metadata:
name: nmstate
spec:
probeConfiguration:
dns:
host: redhat.com
# ...
----
+
.. 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.
+
[source,yaml]
----
$ oc apply -f <filename>.yaml
----
+
.. Monitor the `nmstate` CRD until the resource reaches the `Available` condition by running the following command. Ensure that you set a value for the `--timeout` option so that if the `Available` condition is not met within this set maximum waiting time, the command times out and generates an error message.
+
[source,yaml]
----
$ oc wait --for=condition=Available nmstate/nmstate --timeout=600s
----

.Verification

. Verify that all pods for the NMState Operator have the `Running` status by entering the following command:
+
[source,terminal]
----
Expand Down