OCPBUGS 67311 MachineConfiguration nodeDisruptionPolicy can override mirror-removal policy

[mburke5678]

https://issues.redhat.com/browse/OCPBUGS-67311

Link to docs preview:

• Machine configuration -> Using node disruption policies to minimize disruption from machine config changes -- Added link (before Example node disruption policies)
• Images -> Image configuration resources -> Understanding image registry repository mirroring -- Added to the If you delete an ITMS, IDMS, or ICSP CR object bullet
• Disconnected environments -> Updating a cluster in a disconnected environment -> Updating a cluster in a disconnected environment without OSUS -> Understanding image registry repository mirroring -- Added to the If you delete an ITMS, IDMS, or ICSP CR object bullet.
• Windows Container Support for OpenShift -> Enabling Windows container workloads -> Understanding image registry repository mirroring -- Added to the If you delete an ITMS, IDMS, or ICSP CR object bullet.
• Machine configuration -> Machine configuration overview -> Understanding the Machine Config Operator node drain behavior -- Added link (before Configuring image registry repository mirroring).
• Machine configuration -> Machine configuration overview -> About the Machine Config Operator -> What can you change with machine configs? -- Updated For information reference in penultimate paragraph.
• Machine configuration -> Machine configuration overview -> About the Machine Config Operator -- Updated For information reference in Important note. Added final sentence in Important note.
• Images -> Image configuration resources -- Added link (before Configuring image registry repository mirroring)

QE review:

• QE has approved this change.

[ocpdocs-previewbot]

🤖 Tue Dec 23 23:05:27 - Prow CI generated the docs preview:

https://104292--ocpdocs-pr.netlify.app/
https://104292--ocpdocs-pr.netlify.app/openshift-dedicated/latest/openshift_images/image-configuration.html
https://104292--ocpdocs-pr.netlify.app/openshift-enterprise/latest/disconnected/updating/disconnected-update.html
https://104292--ocpdocs-pr.netlify.app/openshift-enterprise/latest/machine_configuration/index.html
https://104292--ocpdocs-pr.netlify.app/openshift-enterprise/latest/machine_configuration/machine-config-node-disruption.html
https://104292--ocpdocs-pr.netlify.app/openshift-enterprise/latest/openshift_images/image-configuration.html
https://104292--ocpdocs-pr.netlify.app/openshift-enterprise/latest/windows_containers/enabling-windows-container-workloads.html
https://104292--ocpdocs-pr.netlify.app/openshift-rosa/latest/openshift_images/image-configuration.html

[ocpdocs-vale-bot]

🤖 [error] AsciiDocDITA.ShortDescription: Assign [role="_abstract"] to a paragraph to use it as in DITA.

[ocpdocs-vale-bot]

🤖 [error] AsciiDocDITA.ShortDescription: Assign [role="_abstract"] to a paragraph to use it as in DITA.

[ocpdocs-vale-bot]

🤖 [error] AsciiDocDITA.ShortDescription: Assign [role="_abstract"] to a paragraph to use it as in DITA.

[ocpdocs-vale-bot]

🤖 [error] AsciiDocDITA.ShortDescription: Assign [role="_abstract"] to a paragraph to use it as in DITA.

[ocpdocs-vale-bot]

🤖 [error] AsciiDocDITA.ShortDescription: Assign [role="_abstract"] to a paragraph to use it as in DITA.

[ocpdocs-vale-bot]

🤖 [error] AsciiDocDITA.ShortDescription: Assign [role="_abstract"] to a paragraph to use it as in DITA.

[openshift-ci]

@mburke5678: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[mburke5678]

@wking PTAL

[bergerhoffer]

The branch/enterprise-4.22 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.21. And any PR going into main must also target the latest version branch (enterprise-4.22).

If the update in your PR does NOT apply to version 4.22 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale