From 898768a2892478ce1d7fde7189983b9b07cb20a6 Mon Sep 17 00:00:00 2001 From: Carlos Salas Date: Fri, 9 Feb 2024 12:41:06 +0100 Subject: [PATCH] docs: link to installation instructions when capi operator already installed Signed-off-by: Carlos Salas --- docs/getting-started/install_capi_operator.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/getting-started/install_capi_operator.md b/docs/getting-started/install_capi_operator.md index a57c1204..4bedaf7e 100644 --- a/docs/getting-started/install_capi_operator.md +++ b/docs/getting-started/install_capi_operator.md @@ -73,6 +73,8 @@ helm install ... --set infrastructure="docker:v1.4.6;azure:v1.4.6" The `infrastructure` flag is set to `docker:v1.4.6;azure:v1.4.6`, representing the desired provider names. This means that the `Cluster API Operator` will install and manage multiple providers, `Docker` and `Azure` respectively, with versions `v1.4.6` specified in this example. +The cluster is now ready to install Rancher Turtles. The default behavior when installing the chart is to install Cluster API Operator as a Helm dependency. Since we decided to install it manually before installing Rancher Turtles, the feature `cluster-api-operator.enabled` must be explicitly disabled as otherwise it would conflict with the existing installation. You can refer to [Install Rancher Turtles Operator without Cluster API Operator](./install_turtles_operator.md#install-rancher-turtles-operator-without-cluster-api-operator-as-a-helm-dependency) to see next steps. + :::tip For more fine-grained control of the providers and other components installed with CAPI, see the [Add the infrastructure provider](../tasks/capi-operator/add_infrastructure_provider.md) section. :::