Merge pull request #63616 from apinnick/hco-hyperconverged

Change hco to hyperconverged

Author: apinnick

modules/virt-autoupdate-custom-bootsource.adoc

@@ -17,9 +17,9 @@
 
 . Open the `HyperConverged` CR in your default editor by running the following command:
 +
-[source,terminal]
+[source,terminal,subs="attributes+"]
 ----
-$ oc edit hyperconverged kubevirt-hyperconverged -n openshift-cnv
+$ oc edit hyperconverged kubevirt-hyperconverged -n {CNVNamespace}
 ----
 
 . Edit the `HyperConverged` CR, adding the appropriate template and boot source in the `dataImportCronTemplates` section. For example:

modules/virt-configuring-certificate-rotation.adoc

@@ -12,21 +12,21 @@ You can do this during {VirtProductName} installation in the web console or afte
 
 . Open the `HyperConverged` CR by running the following command:
 +
-[source,terminal]
+[source,terminal,subs="attributes+"]
 ----
-$ oc edit hco -n openshift-cnv kubevirt-hyperconverged
+$ oc edit hyperconverged kubevirt-hyperconverged -n {CNVNamespace}
 ----
 
 . Edit the `spec.certConfig` fields as shown in the following example. To avoid overloading the system, ensure that all values are greater than or equal to 10 minutes. Express all values as strings that comply with the link:https://golang.org/pkg/time/#ParseDuration[golang `ParseDuration` format].
 
 +
-[source,yaml]
+[source,yaml,subs="attributes+"]
 ----
 apiVersion: hco.kubevirt.io/v1beta1
 kind: HyperConverged
 metadata:
- name: kubevirt-hyperconverged
- namespace: openshift-cnv
+  name: kubevirt-hyperconverged
+  namespace: {CNVNamespace}
 spec:
   certConfig:
     ca:

modules/virt-configuring-cluster-dpdk.adoc

@@ -88,9 +88,9 @@ $ oc get performanceprofiles.performance.openshift.io profile-1 -o=jsonpath='{.s
 
 . Set the previously obtained `RuntimeClass` name as the default container runtime class for the `virt-launcher` pods by editing the `HyperConverged` custom resource (CR):
 +
-[source,terminal]
+[source,terminal,subs="attributes+"]
 ----
-$ oc patch -n openshift-cnv hco kubevirt-hyperconverged \
+$ oc patch hyperconverged kubevirt-hyperconverged -n {CNVNamespace} \
     --type='json' -p='[{"op": "add", "path": "/spec/defaultRuntimeClass", "value":"<runtimeclass-name>"}]'
 ----
 +

modules/virt-configuring-default-cpu-model.adoc

@@ -21,21 +21,21 @@ The `defaultCPUModel` is case sensitive.
 
 . Open the `HyperConverged` CR by running the following command:
 +
-[source,terminal]
+[source,terminal,subs="attributes+"]
 ----
-$ oc edit hco -n openshift-cnv kubevirt-hyperconverged
+$ oc edit hyperconverged kubevirt-hyperconverged -n {CNVNamespace}
 ----
 
 . Add the `defaultCPUModel` field to the CR and set the value to the name of a CPU model that exists in the cluster:
 
 +
-[source,yaml]
+[source,yaml,subs="attributes+"]
 ----
 apiVersion: hco.kubevirt.io/v1beta1
 kind: HyperConverged
 metadata:
  name: kubevirt-hyperconverged
- namespace: openshift-cnv
+ namespace: {CNVNamespace}
 spec:
   defaultCPUModel: "EPYC"
 ----

modules/virt-configuring-highburst-profile.adoc

@@ -13,23 +13,22 @@ Use the `highBurst` profile to create and maintain a large number of virtual mac
 
 * Apply the following patch to enable the `highBurst` tuning policy profile:
 +
-[source,terminal]
+[source,terminal,subs="attributes+"]
 ----
-$ oc patch -n openshift-cnv hco kubevirt-hyperconverged \
---type=json -p='[{"op": "add", "path": "/spec/tuningPolicy", \
-"value": "highBurst"}]'
+$ oc patch hyperconverged kubevirt-hyperconverged -n {CNVNamespace} \
+  --type=json -p='[{"op": "add", "path": "/spec/tuningPolicy", \
+  "value": "highBurst"}]'
 ----
 
 .Verification
 
 * Run the following command to verify the `highBurst` tuning policy profile is enabled:
-
 +
-[source,terminal]
+[source,terminal,subs="attributes+"]
 ----
 $ oc get kubevirt.kubevirt.io/kubevirt-kubevirt-hyperconverged \
--n openshift-cnv -o go-template --template='{{range $config, \
-$value := .spec.configuration}} {{if eq $config "apiConfiguration" \
-"webhookConfiguration" "controllerConfiguration" "handlerConfiguration"}} \
-{{"\n"}} {{$config}} = {{$value}} {{end}} {{end}} {{"\n"}}
+  -n {CNVNamespace} -o go-template --template='{{range $config, \
+  $value := .spec.configuration}} {{if eq $config "apiConfiguration" \
+  "webhookConfiguration" "controllerConfiguration" "handlerConfiguration"}} \
+  {{"\n"}} {{$config}} = {{$value}} {{end}} {{end}} {{"\n"}}
 ----

modules/virt-configuring-live-migration-limits.adoc

@@ -14,19 +14,19 @@ Configure live migration limits and timeouts for the cluster by updating the `Hy
 
 * Edit the `HyperConverged` CR and add the necessary live migration parameters.
 +
-[source,terminal]
+[source,terminal,subs="attributes+"]
 ----
-$ oc edit hco -n openshift-cnv kubevirt-hyperconverged
+$ oc edit hyperconverged kubevirt-hyperconverged -n {CNVNamespace}
 ----
 +
 .Example configuration file
-[source,yaml]
+[source,yaml,subs="attributes+"]
 ----
 apiVersion: hco.kubevirt.io/v1beta1
 kind: HyperConverged
 metadata:
   name: kubevirt-hyperconverged
-  namespace: openshift-cnv
+  namespace: {CNVNamespace}
 spec:
   liveMigrationConfig: <1>
     bandwidthPerMigration: 64Mi

modules/virt-configuring-obsolete-cpu-models.adoc

@@ -12,13 +12,13 @@ You can configure a list of obsolete CPU models by editing the `HyperConverged`
 
 * Edit the `HyperConverged` custom resource, specifying the obsolete CPU models in the `obsoleteCPUs` array. For example:
 +
-[source,yaml]
+[source,yaml,subs="attributes+"]
 ----
 apiVersion: hco.kubevirt.io/v1beta1
 kind: HyperConverged
 metadata:
   name: kubevirt-hyperconverged
-  namespace: openshift-cnv
+  namespace: {CNVNamespace}
 spec:
   obsoleteCPUs:
     cpuModels: <1>

modules/virt-configuring-pod-log-verbosity.adoc

@@ -12,9 +12,9 @@ You can configure the verbosity level of {VirtProductName} pod logs by editing t
 
 . To set log verbosity for specific components, open the `HyperConverged` CR in your default text editor by running the following command:
 +
-[source,terminal]
+[source,terminal,subs="attributes+"]
 ----
-$ oc edit hyperconverged kubevirt-hyperconverged -n openshift-cnv
+$ oc edit hyperconverged kubevirt-hyperconverged -n {CNVNamespace}
 ----
 
 . Set the log level for one or more components by editing the `spec.logVerbosityConfig` stanza. For example:

modules/virt-configuring-secondary-dns-server.adoc

@@ -18,16 +18,17 @@ The Cluster Network Addons Operator (CNAO) deploys a Domain Name Server (DNS) se
 
 . Create a load balancer service to expose the DNS server outside the cluster by running the `oc expose` command according to the following example:
 +
-[source,terminal]
+[source,terminal,subs="attributes+"]
 ----
-$ oc expose -n openshift-cnv deployment/secondary-dns --name=dns-lb --type=LoadBalancer --port=53 --target-port=5353 --protocol='UDP'
+$ oc expose -n {CNVNamespace} deployment/secondary-dns --name=dns-lb \
+  --type=LoadBalancer --port=53 --target-port=5353 --protocol='UDP'
 ----
 
 . Retrieve the external IP address by running the following command:
 +
-[source,terminal]
+[source,terminal,subs="attributes+"]
 ----
-$ oc get service -n openshift-cnv
+$ oc get service -n {CNVNamespace}
 ----
 +
 .Example output
@@ -39,20 +40,20 @@ dns-lb     LoadBalancer     172.30.27.5    10.46.41.94      53:31829/TCP     5s
 
 . Edit the `HyperConverged` CR in your default editor by running the following command:
 +
-[source,terminal]
+[source,terminal,subs="attributes+"]
 ----
-$ oc edit hyperconverged kubevirt-hyperconverged -n openshift-cnv
+$ oc edit hyperconverged kubevirt-hyperconverged -n {CNVNamespace}
 ----
 
 . Enable the DNS server and monitoring components according to the following example:
 +
-[source,yaml]
+[source,yaml,subs="attributes+"]
 ----
 apiVersion: hco.kubevirt.io/v1beta1
 kind: HyperConverged
 metadata:
   name: kubevirt-hyperconverged
-  namespace: openshift-cnv
+  namespace: {CNVNamespace}
 spec:
     featureGates:
       deployKubeSecondaryDNS: true

modules/virt-configuring-secondary-network-vm-live-migration.adoc

@@ -21,13 +21,13 @@ To configure a dedicated secondary network for live migration, you must first cr
 . Create a `NetworkAttachmentDefinition` manifest.
 +
 .Example configuration file
-[source,yaml]
+[source,yaml,subs="attributes+"]
 ----
 apiVersion: "k8s.cni.cncf.io/v1"
 kind: NetworkAttachmentDefinition
 metadata:
   name: my-secondary-network <1>
-  namespace: openshift-cnv <2>
+  namespace: {CNVNamespace} <2>
 spec:
   config: '{
     "cniVersion": "0.3.1",
@@ -49,9 +49,9 @@ spec:
 
 . Open the `HyperConverged` CR in your default editor by running the following command:
 +
-[source,terminal]
+[source,terminal,subs="attributes+"]
 ----
-oc edit hyperconverged kubevirt-hyperconverged -n openshift-cnv
+oc edit hyperconverged kubevirt-hyperconverged -n {CNVNamespace}
 ----
 
 . Add the name of the `NetworkAttachmentDefinition` object to the `spec.liveMigrationConfig` stanza of the `HyperConverged` CR. For example: