OSDOCS#11133: Hosted control planes release notes

This PR adds release notes for hosted control planes for its asynchronous releases.

Version(s): 4.17+

Issue: https://issues.redhat.com/browse/OSDOCS-11133

Link to docs preview: https://83594--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hosted_control_planes/hosted-control-planes-release-notes

QE review:

• [ ] QE has approved this change.

Additional information:

🤖 Fri Nov 08 09:53:22 - Prow CI generated the docs preview:

https://83594--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hosted_control_planes/hosted-control-planes-release-notes.html

/lgtm

FYI @xenolinux - We'll need to add some of the known issues for hosted control planes from the ACM 2.11 docs: https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html-single/clusters/index#hosted-control-plane-mce. I'm waiting for confirmation from Roke and David to see which known issues still apply.

New changes are detected. LGTM label has been removed.

FYI @xenolinux - We'll need to add some of the known issues for hosted control planes from the ACM 2.11 docs: https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html-single/clusters/index#hosted-control-plane-mce. I'm waiting for confirmation from Roke and David to see which known issues still apply.

Added known issues as per the slack thread.

Addressed all of the comments

LGTM!

The formatting looks great now, @xenolinux. Thanks!

Overall it looks great! Thank you @xenolinux @lahinson

If we're listing bugfixes related to HCP, is this one we want to add? It's more related to the UI via MCE/ACM:

This issue was fixed in MCE 2.7 / ACM 2.12 via https://issues.redhat.com/browse/ACM-10165

Bulk destroy option on KubeVirt hosted cluster does not destroy hosted cluster
- Using the bulk destroy option in the console on KubeVirt hosted clusters does not destroy the KubeVirt hosted clusters.
- Workaround: Use the row action drop-down menu to destroy the KubeVirt hosted cluster instead.

Overall it looks great! Thank you @xenolinux @lahinson

If we're listing bugfixes related to HCP, is this one we want to add? It's more related to the UI via MCE/ACM:

This issue was fixed in MCE 2.7 / ACM 2.12 via https://issues.redhat.com/browse/ACM-10165

Bulk destroy option on KubeVirt hosted cluster does not destroy hosted cluster
- Using the bulk destroy option in the console on KubeVirt hosted clusters does not destroy the KubeVirt hosted clusters.
- Workaround: Use the row action drop-down menu to destroy the KubeVirt hosted cluster instead.

Added this issue in bug fixes.

@xenolinux I received the following known issue from @rokej on the ACM/MCE team. This needs to be added to the known issues for HCP:

* If you have a hosted cluster in the same namespace as its managed cluster, detaching the managed hosted cluster deletes the hosted cluster as well. A hosted cluster can be in the same namespace as its managed cluster in the following situations:

** You created a hosted cluster on the Host Inventory (agent) platform by using the {mce-short} console, and the console defaults the hosted cluster namespace to be the same as managed cluster.
** You created a hosted cluster by using the UI or CLI and specify the namespace to be the same as the hosted cluster name.

Detaching a managed cluster removes the managed cluster namespace so it also deletes everything in the namespace. This causes the hosted cluster to be deleted if it is in the managed cluster's namespace.

Roke added the known issue in this Jira: https://issues.redhat.com/browse/ACM-15088

@xenolinux I received the following known issue from @rokej on the ACM/MCE team. This needs to be added to the known issues for HCP:

* If you have a hosted cluster in the same namespace as its managed cluster, detaching the managed hosted cluster deletes the hosted cluster as well. A hosted cluster can be in the same namespace as its managed cluster in the following situations:

** You created a hosted cluster on the Host Inventory (agent) platform by using the {mce-short} console, and the console defaults the hosted cluster namespace to be the same as managed cluster.
** You created a hosted cluster by using the UI or CLI and specify the namespace to be the same as the hosted cluster name.

Detaching a managed cluster removes the managed cluster namespace so it also deletes everything in the namespace. This causes the hosted cluster to be deleted if it is in the managed cluster's namespace.

Roke added the known issue in this Jira: https://issues.redhat.com/browse/ACM-15088

Thank you!! Added this one I will debug the portal check failure once I fix links.

@xenolinux: all tests passed!

Full PR test history. Your PR dashboard.

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.

/cherrypick enterprise-4.17

/cherrypick enterprise-4.18

@xenolinux: new pull request created: #84662

In response to this:

/cherrypick enterprise-4.17

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.

@xenolinux: new pull request created: #84663

In response to this:

/cherrypick enterprise-4.18

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.