CNV-11201: RN Roll out of node network configuration policy

[sjhala-ccs]

CNV-11201

Preview: https://deploy-preview-42355--osdocs.netlify.app/openshift-enterprise/latest/virt/virt-4-10-release-notes.html#virt-4-10-networking-new

[netlify]

✔️ Deploy Preview for osdocs ready!

🔨 Explore the source changes: 72938c4

🔍 Inspect the deploy log: https://app.netlify.com/sites/osdocs/deploys/62179dd714c0a5000866526a

😎 Browse the preview: https://deploy-preview-42355--osdocs.netlify.app/openshift-enterprise/latest/virt/virt-4-10-release-notes

[sjhala-ccs]

@rhrazdil Can you please review? Thank you.

[rhrazdil]

@sjhala-ccs The release note looks good.

But I also read the section that the release note refers to and one thing that's odd there is the Example Output at the end of this section: https://deploy-preview-42355--osdocs.netlify.app/openshift-enterprise/latest/virt/node_network/virt-updating-node-network-config.html#virt-creating-interface-on-nodes_virt-updating-node-network-config

There is:
2. Create the node network policy:

$ oc apply -f br1-eth1_policy.yaml

Example output

NAME                     STATUS
node01.br1-eth1-policy   Pending
node02.br1-eth1-policy   Progressing
node03.br1-eth1-policy   Available
node04.br1-eth1-policy   Progressing
node05.br1-eth1-policy   Progressing
node06.br1-eth1-policy   Pending

I'n not sure the user know at this moment, how to get to the example output? From the article, is appears as if the output would be produced by the oc apply command, but it is actually obtained by running oc get nnce, but IIUC, that is explained only in the following section.

[sjhala-ccs]

@rhrazdil I would have to create a separate PR against the main branch to update the section that the release note refers to. For tracking purposes, can you please open a documentation BZ for this? Do you want me to move the Example output code block to the Confirming node network policy updates on nodes section or remove it completely from the documentation?

[rhrazdil]

Thanks @sjhala-ccs let's move forward with this and address that in a separate PR
/lgtm

[rhrazdil]

@sjhala-ccs link to the issue: #42560

[ousleyp]

LGTM!

[bobfuru]

In preparation for OCP 4.10 GA, I'm moving the Milestone to "Next Release" as this PR did not make the merge by the 4.10 GA date. Post-GA, any open 4.10 PRs fall under the "Next Release" bucket in the same way that 4.6-4.9 PRs are already there. This change does not have any impact on the work in this PR; it's a housekeeping task to keep account of all PRs that had already merged by the 4.10 GA date. 😁