Merge pull request #352 from anmazzotti/revert_rancher_2-12

Revert "Bump Rancher to v2.12.0 (#348)"

Author: alexander-demicev

docs/next/modules/en/pages/operator/certificationsuite.adoc

@@ -77,7 +77,7 @@ variables:
   SKIP_RESOURCE_CLEANUP: "false"
   ARTIFACTS_FOLDER: "_artifacts"
   MANAGEMENT_CLUSTER_ENVIRONMENT: "kind" # supported options are eks, isolated-kind, kind
-  RANCHER_VERSION: "v2.12.0"
+  RANCHER_VERSION: "v2.11.0"
   KUBERNETES_VERSION: "{kubernetes-version}"
   KUBERNETES_MANAGEMENT_VERSION: "{kubernetes-version}"
   KUBERNETES_MANAGEMENT_AWS_REGION: "eu-west-2"

docs/next/modules/en/pages/overview/features.adoc

@@ -22,7 +22,7 @@ This section describes features and feature stages in {product_name}.
 |===
 
 === Add-on Provider for Fleet
-This feature installs Cluster API Add-on Provider for Fleet (CAAPF) to provide integration with link:https://github.com/rancher/fleet[Fleet] and enable the easy deployment of applications to CAPI provisioned clusters. CAAPF automatically installs Fleet in the management cluster and registers newly provisioned CAPI clusters with Fleet, so that applications can be deployed to these clusters via GitOps, `Bundle` or `HelmOp` resources. CAAPF also includes support for grouping CAPI clusters that reference the same ClusterClass through Fleet's ClusterGroup, essentially simplifying application deployments to large groups of clusters. This feature is in GA stage and enabled by default.
+This feature installs Cluster API Add-on Provider for Fleet (CAAPF) to provide integration with link:https://github.com/rancher/fleet[Fleet] and enable the easy deployment of applications to CAPI provisioned clusters. CAAPF automatically installs Fleet in the management cluster and registers newly provisioned CAPI clusters with Fleet, so that applications can be deployed to these clusters via GitOps, `Bundle` or `HelmApp` resources. CAAPF also includes support for grouping CAPI clusters that reference the same ClusterClass through Fleet's ClusterGroup, essentially simplifying application deployments to large groups of clusters. This feature is in GA stage and enabled by default.
 
 === Agent TLS Mode
 This feature gate is used to instruct Turtles on whether it should follow Rancher's `agent-tls-mode` setting, when retrieving cluster registration manifests for importing clusters. When enabled, Turtles will lookup the value of Rancher's `agent-tls-mode` setting to determine whether it has been set to `system-store` or `strict`. If set to `system-store`, Turtles will trust any certificate generated by a public Certificate Authority contained in the operating system's trust store, including those signed by authorities such as Let's Encrypt. If set to `strict`, Turtles will only trust certificates generated by the Certificate Authority contained in Rancher's `cacerts` setting. When this setting is disabled, Turtles will fallback to work in `system-store` mode. This feature is in beta stage and enabled by default.

docs/next/modules/en/pages/tutorials/quickstart.adoc

@@ -23,7 +23,7 @@ Before you can install {product_name}, you need to have the following components
 | Follow the official https://helm.sh/docs/intro/install[installation docs]
 
 | Rancher
-| `v2.12.0`
+| `v2.11.0`
 | Install using https://ranchermanager.docs.rancher.com/pages-for-subheaders/install-upgrade-on-a-kubernetes-cluster#install-the-rancher-helm-chart[Helm] on any Kubernetes cluster, whether self-hosted or on a managed service from https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks[Amazon], https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks[Azure], or https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-gke[Google].
 
 | Cert-manager

docs/next/modules/en/pages/user/clusterclass.adoc

@@ -410,7 +410,7 @@ spec:
 
 [WARNING]
 ====
-The experimental `HelmApp` CRD introduced in Rancher `v2.11` has been renamed to `HelmOp` in Rancher `v2.12`.
+Examples using `HelmApps` need at least Rancher `v2.11`, or otherwise Fleet `v0.12` or higher.
 ====
 
 [tabs]
@@ -448,7 +448,7 @@ For this example we are also going to install https://docs.tigera.io/calico/late
 +
 We can do this automatically at Cluster creation using the https://rancher.github.io/cluster-api-addon-provider-fleet/[Cluster API Add-on Provider Fleet]. +
 This Add-on provider is installed by default with {product_name}. +
-Two `HelmOps` need to be created first, to be applied on the new Cluster via label selectors. +
+Two `HelmApps` need to be created first, to be applied on the new Cluster via label selectors. +
 +
 [source,bash]
 ----
@@ -595,7 +595,7 @@ For this example we are also going to install https://docs.tigera.io/calico/late
 +
 We can do this automatically at Cluster creation using the https://rancher.github.io/cluster-api-addon-provider-fleet/[Cluster API Add-on Provider Fleet]. +
 This Add-on provider is installed by default with {product_name}. +
-Two `HelmOps` need to be created first, to be applied on the new Cluster via label selectors. +
+Two `HelmApps` need to be created first, to be applied on the new Cluster via label selectors. +
 +
 [source,bash]
 ----
@@ -677,7 +677,7 @@ kubectl apply -f https://raw.githubusercontent.com/rancher/turtles/refs/tags/v0.
 +
 We can do this automatically at Cluster creation using the https://rancher.github.io/cluster-api-addon-provider-fleet/[Cluster API Add-on Provider Fleet]. +
 This Add-on provider is installed by default with {product_name}. +
-The `HelmOps` need to be created first, to be applied on the new Cluster via label selectors. This will take care of deploying Calico, the EBS CSI Driver, and the AWS Cloud Controller Manager in the workload cluster. +
+The `HelmApps` need to be created first, to be applied on the new Cluster via label selectors. This will take care of deploying Calico, the EBS CSI Driver, and the AWS Cloud Controller Manager in the workload cluster. +
 +
 [source,bash]
 ----
@@ -768,7 +768,7 @@ kubectl apply -f https://raw.githubusercontent.com/rancher/turtles/refs/tags/v0.
 +
 We can do this automatically at Cluster creation using the https://rancher.github.io/cluster-api-addon-provider-fleet/[Cluster API Add-on Provider Fleet]. +
 This Add-on provider is installed by default with {product_name}. +
-The `HelmOps` need to be created first, to be applied on the new Cluster via label selectors. This will take care of deploying Calico, the EBS CSI Driver, and the AWS Cloud Controller Manager in the workload cluster. +
+The `HelmApps` need to be created first, to be applied on the new Cluster via label selectors. This will take care of deploying Calico, the EBS CSI Driver, and the AWS Cloud Controller Manager in the workload cluster. +
 +
 [source,bash]
 ----
@@ -862,7 +862,7 @@ kubectl apply -f https://raw.githubusercontent.com/rancher/turtles/refs/tags/v0.
 +
 We can do this automatically at Cluster creation using a combination of https://rancher.github.io/cluster-api-addon-provider-fleet/[Cluster API Add-on Provider Fleet] and https://fleet.rancher.io/bundle-add[Fleet Bundle]. +
 The Add-on provider is installed by default with {product_name}. +
-The `HelmOps` need to be created first, to be applied on the new Cluster via label selectors. This will take care of deploying Calico. +
+The `HelmApps` need to be created first, to be applied on the new Cluster via label selectors. This will take care of deploying Calico. +
 +
 [source,bash]
 ----
@@ -954,7 +954,7 @@ kubectl apply -f https://raw.githubusercontent.com/rancher/turtles/refs/tags/v0.
 +
 We can do this automatically at Cluster creation using the https://rancher.github.io/cluster-api-addon-provider-fleet/[Cluster API Add-on Provider Fleet]. +
 This Add-on provider is installed by default with {product_name}. +
-Two `HelmOps` need to be created first, to be applied on the new Cluster via label selectors. +
+Two `HelmApps` need to be created first, to be applied on the new Cluster via label selectors. +
 +
 [source,bash]
 ----
@@ -1025,7 +1025,7 @@ kubectl apply -f https://raw.githubusercontent.com/rancher/turtles/refs/tags/v0.
 +
 We can do this automatically at Cluster creation using the https://rancher.github.io/cluster-api-addon-provider-fleet/[Cluster API Add-on Provider Fleet]. +
 This Add-on provider is installed by default with {product_name}. +
-Two `HelmOps` need to be created first, to be applied on the new Cluster via label selectors. +
+Two `HelmApps` need to be created first, to be applied on the new Cluster via label selectors. +
 +
 [source,bash]
 ----
@@ -1110,7 +1110,7 @@ Finally, for this example we are going to install https://docs.tigera.io/calico/
 +
 We can install all applications automatically at Cluster creation using the https://rancher.github.io/cluster-api-addon-provider-fleet/[Cluster API Add-on Provider Fleet]. +
 This Add-on provider is installed by default with {product_name}. +
-Two `HelmOps` need to be created first, to be applied on the new Cluster via label selectors. +
+Two `HelmApps` need to be created first, to be applied on the new Cluster via label selectors. +
 +
 [source,bash]
 ----
@@ -1288,7 +1288,7 @@ Finally, for this example we are going to install https://docs.tigera.io/calico/
 +
 We can install all applications automatically at Cluster creation using the https://rancher.github.io/cluster-api-addon-provider-fleet/[Cluster API Add-on Provider Fleet]. +
 This Add-on provider is installed by default with {product_name}. +
-Two `HelmOps` need to be created first, to be applied on the new Cluster via label selectors. +
+Two `HelmApps` need to be created first, to be applied on the new Cluster via label selectors. +
 +
 [source,bash]
 ----