From 629ae64464594974b907069b4f5a679879a9fbee Mon Sep 17 00:00:00 2001 From: oafischer Date: Thu, 9 Jan 2025 11:26:34 +0100 Subject: [PATCH 1/3] https://issues.redhat.com/browse/ACM-15868 Add External platform --- .../create_cluster_on_prem.adoc | 26 ++++++++++++++++--- 1 file changed, 23 insertions(+), 3 deletions(-) diff --git a/clusters/cluster_lifecycle/create_cluster_on_prem.adoc b/clusters/cluster_lifecycle/create_cluster_on_prem.adoc index d2e592dc7a..b594aec33d 100644 --- a/clusters/cluster_lifecycle/create_cluster_on_prem.adoc +++ b/clusters/cluster_lifecycle/create_cluster_on_prem.adoc @@ -1,9 +1,9 @@ [#creating-a-cluster-on-premises] = Creating a cluster in an on-premises environment -You can use the console to create on-premises {ocp} clusters. The clusters can be {sno} clusters, multi-node clusters, and compact three-node clusters on VMware vSphere, Red Hat OpenStack, Nutanix, or in a bare metal environment. +You can use the console to create on-premises {ocp} clusters. The clusters can be {sno} clusters, multi-node clusters, and compact three-node clusters on VMware vSphere, Red Hat OpenStack, Nutanix, External, or in a bare metal environment. -There is no platform integration with the platform where you install the cluster, as the platform value is set to `platform=none`. A {sno} cluster contains only a single node, which hosts the control plane services and the user workloads. This configuration can be helpful when you want to minimize the resource footprint of the cluster. +There is no platform integration with the platform where you install the cluster, as the platform value is set to `platform=none`. A {sno} cluster has only a single node, which hosts the control plane services and the user workloads. This configuration can be helpful when you want to minimize the resource footprint of the cluster. You can also provision multiple {sno} clusters on edge resources by using the zero touch provisioning feature, which is a feature that is available with {ocp}. For more information about zero touch provisioning, see _Clusters at the network far edge_ in the {ocp-short} documentation. @@ -225,7 +225,27 @@ spec: <1> Specify the platform type of the environment where the cluster is created. Valid values are: `BareMetal`, `None`, `VSphere`, `Nutanix`, or `External`. <2> Use the same name that you used for your `ClusterDeployment` resource. <3> Use the `ClusterImageSet` that you generated in <>. -<4> You can specify your SSH public key, which enables you to access the host after it is installed. +<4> You can specify your SSH public key, which enables you to access the host after it is installed. + +If you set `platformType:` to `External`, you must add the `external` spec. See the following example: + +[source,yaml] +---- +apiVersion: extensions.hive.openshift.io/v1beta1 +kind: AgentClusterInstall +metadata: + name: test-agent-cluster-install + namespace: demo-worker4 +spec: + platformType: External + external: + platformName: "myplatform" <1> + cloudControllerManager: External <2> +---- + +<1> Add your platform name. +<2> Leave empty to disable the Cloud Controller Manager during installation. + [#on-prem-creating-your-cluster-with-the-cli-nmstateconfig] === Optional: Create the NMStateConfig custom resource From cb7692e315fa00e767bed00f627710cb8091b158 Mon Sep 17 00:00:00 2001 From: oafischer Date: Thu, 9 Jan 2025 11:35:26 +0100 Subject: [PATCH 2/3] https://issues.redhat.com/browse/ACM-15868 Add External platform --- clusters/release_notes/mce_whats_new.adoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/clusters/release_notes/mce_whats_new.adoc b/clusters/release_notes/mce_whats_new.adoc index 20d722181d..a1dfd62ab8 100644 --- a/clusters/release_notes/mce_whats_new.adoc +++ b/clusters/release_notes/mce_whats_new.adoc @@ -29,4 +29,6 @@ If you are using {mce-short} 2.6 and earlier, the hosted control planes document [#cluster-management-new] == Cluster management -Learn about new features and enhancements for Cluster lifecycle with {mce-short}. \ No newline at end of file +Learn about new features and enhancements for Cluster lifecycle with {mce-short}. + +You can now use the `External` platform in {ai}, which allows you to use integration components from cloud providers. To learn more, see link:../../clusters/cluster_lifecycle/create_cluster_on_prem.adoc#create-agentclusterinstall-cr[Create the AgentClusterInstall custom resource] \ No newline at end of file From cd6afad9d8dcb04a4b77ea652503290db2e39f17 Mon Sep 17 00:00:00 2001 From: oafischer Date: Thu, 9 Jan 2025 11:44:15 +0100 Subject: [PATCH 3/3] https://issues.redhat.com/browse/ACM-15868 Add External platform --- clusters/cluster_lifecycle/create_cluster_on_prem.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/clusters/cluster_lifecycle/create_cluster_on_prem.adoc b/clusters/cluster_lifecycle/create_cluster_on_prem.adoc index b594aec33d..2eb98dd360 100644 --- a/clusters/cluster_lifecycle/create_cluster_on_prem.adoc +++ b/clusters/cluster_lifecycle/create_cluster_on_prem.adoc @@ -189,7 +189,7 @@ spec: <1> Use the name of your `AgentClusterInstall` resource. <2> Use the pull secret that you downloaded in <>. -[#on-prem-creating-your-cluster-with-the-cli-agentclusterinstall] +[#create-agentclusterinstall-cr] === Create the AgentClusterInstall custom resource In the `AgentClusterInstall` custom resource, you can specify many of the requirements for the clusters. For example, you can specify the cluster network settings, platform, number of control planes, and worker nodes.