OCPBUGS-21804 update NTO command syntax

sheriff-rh · sheriff-rh · commit c31c588d1d64 · 2023-10-17T09:19:26.000-04:00
diff --git a/modules/accessing-an-example-cluster-node-tuning-operator-specification.adoc b/modules/accessing-an-example-cluster-node-tuning-operator-specification.adoc
@@ -15,7 +15,7 @@ Use this process to access an example Node Tuning Operator specification.
 +
 [source,terminal]
 ----
-$ oc get Tuned/default -o yaml -n openshift-cluster-node-tuning-operator
+oc get tuned.tuned.openshift.io/default -o yaml -n openshift-cluster-node-tuning-operator
 ----
 
 The default CR is meant for delivering standard node-level tuning for the {product-title} platform and it can only be modified to set the Operator Management state. Any other custom changes to the default CR will be overwritten by the Operator. For custom tuning, create your own Tuned CRs. Newly created CRs will be combined with the default CR and custom tuning applied to {product-title} nodes based on node or pod labels and profile priorities.
diff --git a/modules/advanced-node-tuning-hosted-cluster.adoc b/modules/advanced-node-tuning-hosted-cluster.adoc
@@ -111,7 +111,7 @@ After the nodes are available, the containerized TuneD daemon calculates the req
 +
 [source,terminal]
 ----
-$ oc --kubeconfig="$HC_KUBECONFIG" get Tuneds -n openshift-cluster-node-tuning-operator
+$ oc --kubeconfig="$HC_KUBECONFIG" get tuned.tuned.openshift.io -n openshift-cluster-node-tuning-operator
 ----
 +
 .Example output
@@ -127,7 +127,7 @@ rendered             123m
 +
 [source,terminal]
 ----
-$ oc --kubeconfig="$HC_KUBECONFIG" get Profiles -n openshift-cluster-node-tuning-operator
+$ oc --kubeconfig="$HC_KUBECONFIG" get profile.tuned.openshift.io -n openshift-cluster-node-tuning-operator
 ----
 +
 .Example output
diff --git a/modules/cluster-node-tuning-operator-verify-profiles.adoc b/modules/cluster-node-tuning-operator-verify-profiles.adoc
@@ -9,7 +9,7 @@ Verify the TuneD profiles that are applied to your cluster node.
 
 [source,terminal]
 ----
-$ oc get profile -n openshift-cluster-node-tuning-operator
+$ oc get profile.tuned.openshift.io -n openshift-cluster-node-tuning-operator
 ----
 
 .Example output
diff --git a/modules/node-tuning-hosted-cluster.adoc b/modules/node-tuning-hosted-cluster.adoc
@@ -89,7 +89,7 @@ Now that you have created the `ConfigMap` object that contains a `Tuned` manifes
 +
 [source,terminal]
 ----
-$ oc --kubeconfig="$HC_KUBECONFIG" get Tuneds -n openshift-cluster-node-tuning-operator
+$ oc --kubeconfig="$HC_KUBECONFIG" get tuned.tuned.openshift.io -n openshift-cluster-node-tuning-operator
 ----
 +
 .Example output
@@ -105,7 +105,7 @@ tuned-1    65s
 +
 [source,terminal]
 ----
-$ oc --kubeconfig="$HC_KUBECONFIG" get Profiles -n openshift-cluster-node-tuning-operator
+$ oc --kubeconfig="$HC_KUBECONFIG" get profile.tuned.openshift.io -n openshift-cluster-node-tuning-operator
 ----
 +
 .Example output

Original file line number	Diff line number	Diff line change
`@@ -15,7 +15,7 @@ Use this process to access an example Node Tuning Operator specification.`
`15`	`15`	`+`
`16`	`16`	`[source,terminal]`
`17`	`17`	`----`
`18`		`-$ oc get Tuned/default -o yaml -n openshift-cluster-node-tuning-operator`
	`18`	`+oc get tuned.tuned.openshift.io/default -o yaml -n openshift-cluster-node-tuning-operator`
`19`	`19`	`----`
`20`	`20`
`21`	`21`	`The default CR is meant for delivering standard node-level tuning for the {product-title} platform and it can only be modified to set the Operator Management state. Any other custom changes to the default CR will be overwritten by the Operator. For custom tuning, create your own Tuned CRs. Newly created CRs will be combined with the default CR and custom tuning applied to {product-title} nodes based on node or pod labels and profile priorities.`
Original file line number	Diff line number	Diff line change
`@@ -111,7 +111,7 @@ After the nodes are available, the containerized TuneD daemon calculates the req`
`111`	`111`	`+`
`112`	`112`	`[source,terminal]`
`113`	`113`	`----`
`114`		`-$ oc --kubeconfig="$HC_KUBECONFIG" get Tuneds -n openshift-cluster-node-tuning-operator`
	`114`	`+$ oc --kubeconfig="$HC_KUBECONFIG" get tuned.tuned.openshift.io -n openshift-cluster-node-tuning-operator`
`115`	`115`	`----`
`116`	`116`	`+`
`117`	`117`	`.Example output`
`@@ -127,7 +127,7 @@ rendered 123m`
`127`	`127`	`+`
`128`	`128`	`[source,terminal]`
`129`	`129`	`----`
`130`		`-$ oc --kubeconfig="$HC_KUBECONFIG" get Profiles -n openshift-cluster-node-tuning-operator`
	`130`	`+$ oc --kubeconfig="$HC_KUBECONFIG" get profile.tuned.openshift.io -n openshift-cluster-node-tuning-operator`
`131`	`131`	`----`
`132`	`132`	`+`
`133`	`133`	`.Example output`
Original file line number	Diff line number	Diff line change
@@ -89,7 +89,7 @@ Now that you have created the `ConfigMap` object that contains a `Tuned` manifes
`89`	`89`	`+`
`90`	`90`	`[source,terminal]`
`91`	`91`	`----`
`92`		`-$ oc --kubeconfig="$HC_KUBECONFIG" get Tuneds -n openshift-cluster-node-tuning-operator`
	`92`	`+$ oc --kubeconfig="$HC_KUBECONFIG" get tuned.tuned.openshift.io -n openshift-cluster-node-tuning-operator`
`93`	`93`	`----`
`94`	`94`	`+`
`95`	`95`	`.Example output`
`@@ -105,7 +105,7 @@ tuned-1 65s`
`105`	`105`	`+`
`106`	`106`	`[source,terminal]`
`107`	`107`	`----`
`108`		`-$ oc --kubeconfig="$HC_KUBECONFIG" get Profiles -n openshift-cluster-node-tuning-operator`
	`108`	`+$ oc --kubeconfig="$HC_KUBECONFIG" get profile.tuned.openshift.io -n openshift-cluster-node-tuning-operator`
`109`	`109`	`----`
`110`	`110`	`+`
`111`	`111`	`.Example output`