1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 15:46:57 +01:00

Clarifying that you do not need RHACM to use HCP

This commit is contained in:
Laura Hinson
2025-09-11 13:13:51 -04:00
committed by openshift-cherrypick-robot
parent 95d2d58995
commit 81eaf1450d
2 changed files with 11 additions and 1 deletions

View File

@@ -6,7 +6,12 @@
[id="hcp-mce-acm-relationship-intro_{context}"]
= Relationship between {hcp}, {mce-short}, and {rh-rhacm}
You can configure {hcp} by using the {mce}. The multicluster engine is an integral part of {rh-rhacm-first} and is enabled by default with {rh-rhacm}. The {mce-short} cluster lifecycle defines the process of creating, importing, managing, and destroying Kubernetes clusters across various infrastructure cloud providers, private clouds, and on-premises data centers.
You can configure {hcp} by using the {mce}. The {mce-short} cluster lifecycle defines the process of creating, importing, managing, and destroying Kubernetes clusters across various infrastructure cloud providers, private clouds, and on-premises data centers.
[NOTE]
====
The {mce-short} is an integral part of {rh-rhacm-first} and is enabled by default with {rh-rhacm}. However, you do not need {rh-rhacm} in order to use {hcp}.
====
The {mce-short} is the cluster lifecycle Operator that provides cluster management capabilities for {product-title} and {rh-rhacm} hub clusters. The {mce-short} enhances cluster fleet management and supports {product-title} cluster lifecycle management across clouds and data centers.

View File

@@ -20,6 +20,11 @@
The {hcp} feature is enabled by default.
[NOTE]
====
The {mce-short} is an integral part of {rh-rhacm-first} and is enabled by default with {rh-rhacm}. However, you do not need {rh-rhacm} in order to use {hcp}.
====
[id="hosted-control-planes-architecture_{context}"]
== Architecture of {hcp}