Skip to content

Commit 35cb392

Browse files
authored
Merge pull request #82536 from xenolinux/hcp-mce-acm-rel
OSDOCS#10999: HCP introducing MCE and a relationship between HCP, MCE, and ACM
2 parents 211e80d + 7af40d9 commit 35cb392

File tree

4 files changed

+28
-1
lines changed

4 files changed

+28
-1
lines changed

hosted_control_planes/index.adoc

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,7 @@ You can deploy {product-title} clusters by using two different control plane con
99
toc::[]
1010

1111
include::modules/hosted-control-planes-overview.adoc[leveloffset=+1]
12+
include::modules/hcp-mce-acm-relationship-intro.adoc[leveloffset=+1]
1213
include::modules/hosted-control-planes-version-support.adoc[leveloffset=+1]
1314

1415
[role="_additional-resources"]
@@ -17,4 +18,4 @@ include::modules/hosted-control-planes-version-support.adoc[leveloffset=+1]
1718
* xref:../scalability_and_performance/using-node-tuning-operator.adoc#node-tuning-hosted-cluster_node-tuning-operator[Configuring node tuning in a hosted cluster]
1819
* xref:../scalability_and_performance/using-node-tuning-operator.adoc#advanced-node-tuning-hosted-cluster_node-tuning-operator[Advanced node tuning for hosted clusters by setting kernel boot parameters]
1920
20-
include::modules/hosted-control-planes-concepts-personas.adoc[leveloffset=+1]
21+
include::modules/hosted-control-planes-concepts-personas.adoc[leveloffset=+1]

images/acm-mce-intro-diagram.png

160 KB
Loading

images/rhacm-flow.png

170 KB
Loading
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * hosted_control_planes/index.adoc
4+
5+
:_mod-docs-content-type: CONCEPT
6+
[id="hcp-mce-acm-relationship-intro_{context}"]
7+
= Relationship between {hcp}, {mce-short}, and {rh-rhacm}
8+
9+
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.
10+
11+
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.
12+
13+
.Cluster life cycle and foundation
14+
image::acm-mce-intro-diagram.png[Cluster life cycle and foundation]
15+
16+
You can use the {mce-short} with {product-title} as a standalone cluster manager or as part of a {rh-rhacm} hub cluster.
17+
18+
[TIP]
19+
====
20+
A management cluster is also known as the hosting cluster.
21+
====
22+
23+
You can deploy {product-title} clusters by using two different control plane configurations: standalone or hosted control planes. The standalone configuration uses dedicated virtual machines or physical machines to host the control plane. With {hcp} for {product-title}, you create control planes as pods on a management cluster without the need for dedicated virtual or physical machines for each control plane.
24+
25+
.{rh-rhacm} and the {mce-short} introduction diagram
26+
image::rhacm-flow.png[{rh-rhacm} and the {mce-short} introduction diagram]

0 commit comments

Comments
 (0)