[OKD] OSDOCS Incorrect link

[mburke5678]

#96704

4.17: The about-installing-oc-mirror-v2.adoc file is at: https://docs.okd.io/4.17/disconnected/mirroring/about-installing-oc-mirror-v2.html
4.18+: The about-installing-oc-mirror-v2.adoc file was moved up one level in 4.18. It is now: https://docs.okd.io/latest/disconnected/about-installing-oc-mirror-v2.html

Link to docs preview:

QE review:

• QE has approved this change.

[mburke5678]

@kenjpais: Dennis Gilmore suggested you can review OKD doc changes. Can you PTAL at this updated link? Thank you in advance.

[ocpdocs-previewbot]

🤖 Mon Jun 01 17:35:03 - Prow CI generated the docs preview:

https://105714--ocpdocs-pr.netlify.app/openshift-enterprise/latest/disconnected/about-installing-oc-mirror-v2.html

[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

[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.

[jeana-redhat]

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

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

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