You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* <<components-metal3,Metal3>> IPAM provider (currently not supported)
38
+
* Fleet addon provider
37
39
38
40
Only the default providers installed via the wrapper chart are supported - alternative Control Plane, Bootstrap and Infrastructure providers are not currently supported as part of the SUSE Edge stack.
39
41
40
42
== Installing Rancher Turtles
41
43
42
-
Rancher Turtles may be installed by following the <<quickstart-metal3,Metal3 Quickstart>> guide, or the <<atip-management-cluster,Management Cluster>> documentation.
44
+
Since Rancher 2.13, Rancher Turtles is enabled by default when installing Rancher.
45
+
46
+
Rancher Turtles Providers may be installed by following the <<quickstart-metal3,Metal3 Quickstart>> guide, or the <<atip-management-cluster,Management Cluster>> documentation.
Copy file name to clipboardExpand all lines: asciidoc/day2/migration.adoc
+23-5Lines changed: 23 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
[#day2-migration]
2
2
= Edge {version-edge} migration
3
-
:revdate: 2025-09-30
3
+
:revdate: 2025-12-15
4
4
:page-revdate: {revdate}
5
5
:experimental:
6
6
@@ -13,9 +13,9 @@ ifdef::env-github[]
13
13
:warning-caption: :warning:
14
14
endif::[]
15
15
:toc: preamble
16
-
:previous-edge-version: 3.3
17
-
:static-edge-version: 3.4.0
18
-
:static-fleet-examples-tag: release-3.4.0
16
+
:previous-edge-version: 3.4
17
+
:static-edge-version: 3.4.2
18
+
:static-fleet-examples-tag: release-3.4.2
19
19
20
20
This section explains how to migrate your `management` and `downstream` clusters from `Edge {previous-edge-version}` to `Edge {static-edge-version}`.
21
21
@@ -62,7 +62,7 @@ This section covers the following topics:
62
62
63
63
[NOTE]
64
64
====
65
-
Applies only to clusters that require a <<components-metal3>> chart upgrade.
65
+
Applies only to CAPI/Metal3 management clusters that require a <<components-metal3>> chart upgrade.
66
66
====
67
67
68
68
The `Metal^3^` Helm chart includes the link:https://book.metal3.io/bmo/introduction.html[Bare Metal Operator (BMO)] CRDs by leveraging Helm's link:https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#method-1-let-helm-do-it-for-you[CRD] directory.
@@ -80,6 +80,24 @@ On a machine with `Helm` installed and `kubectl` configured to point to your `{c
Applies only to CAPI/Metal3 management clusters that require a rancher turtles chart upgrade.
88
+
89
+
You must ensure the management cluster is first updated to the latest 3.4 z-stream, which contains the necessary 0.24.3 Rancher Turtles version.
90
+
====
91
+
92
+
Starting with Rancher 2.13, Rancher Turtles is installed by default, therefore it is necessary to follow some additional migration steps as describwd in the https://turtles.docs.rancher.com/turtles/next/en/tutorials/migration.html[Rancher Turtles Documentation]
Copy file name to clipboardExpand all lines: asciidoc/product/atip-management-cluster.adoc
+17-74Lines changed: 17 additions & 74 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
[#atip-management-cluster]
2
2
== Setting up the management cluster
3
-
:revdate: 2025-07-31
3
+
:revdate: 2025-12-01
4
4
:page-revdate: {revdate}
5
5
:experimental:
6
6
@@ -64,7 +64,6 @@ The following are the main steps to set up the management cluster using a declar
64
64
- xref:mgmt-cluster-image-definition-file-airgap[Modifications in the definition file]: The `mgmt-cluster.yaml` file must be modified to include the `embeddedArtifactRegistry` section with the `images` field set to all container images to be included into the EIB output image.
65
65
- xref:mgmt-cluster-custom-folder-airgap[Modifications in the custom folder]: The `custom` folder must be modified to include the resources needed to run the management cluster in an air-gap environment.
66
66
** Register script: The `custom/scripts/99-register.sh` script must be removed when you use an air-gap environment.
67
-
- xref:mgmt-cluster-helm-values-folder-airgap[Modifications in the helm values folder]: The `helm/values` folder must be modified to include the configuration needed to run the management cluster in an air-gap environment.
68
67
69
68
. **xref:mgmt-cluster-image-creation[Image creation]**: This step covers the creation of the image using the Edge Image Builder tool (for both, connected and air-gap scenarios). Check the <<components-eib,prerequisites>> to run the Edge Image Builder tool on your system.
This section describes how to prepare the image for air-gap environments showing only the differences from the previous sections. The following changes to the previous section (xref:mgmt-cluster-image-preparation-connected[Image preparation for connected environments]) are required to prepare the image for air-gap environments:
1008
992
1009
993
- The `mgmt-cluster.yaml` file must be modified to include the `embeddedArtifactRegistry` section with the `images` field set to all container images to be included into the EIB output image.
1010
-
- The `mgmt-cluster.yaml` file must be modified to include `rancher-turtles-airgap-resources` helm chart.
1011
994
- The `custom/scripts/99-register.sh` script must be removed when use an air-gap environment.
1012
995
1013
996
[#mgmt-cluster-image-definition-file-airgap]
@@ -1022,8 +1005,6 @@ The following is an example of the `mgmt-cluster.yaml` file with the `embeddedAr
1022
1005
Make sure to the listed images contain the component versions you need.
1023
1006
====
1024
1007
1025
-
The `rancher-turtles-airgap-resources` helm chart must also be added, this creates resources as described in the https://documentation.suse.com/cloudnative/cluster-api/{rancher-turtles-docs-version}/en/getting-started/air-gapped-environment.html[Rancher Turtles Airgap Documentation]. This also requires a turtles.yaml values file for the rancher-turtles chart to specify the necessary configuration.
- The `custom/scripts/99-register.sh` script must be removed when using an air-gap environment. As you can see in the directory structure, the `99-register.sh` script is not included in the `custom/scripts` folder.
1182
1157
1183
1158
1184
-
[#mgmt-cluster-helm-values-folder-airgap]
1185
-
==== Modifications in the helm values folder
1186
-
1187
-
- The `turtles.yaml`: contains the configuration required to specify airgapped operation for Rancher Turtles, note this depends on installation of the rancher-turtles-airgap-resources chart.
After some time, the controller pods should be running in the `capi-system`, `capm3-system`, `rke2-bootstrap-system` and `rke2-control-plane-system` namespaces.
168
+
After some time, the controller pods should be running in the `cattle-capi-system`, `capm3-system`, `rke2-bootstrap-system` and `rke2-control-plane-system` namespaces.
* Use `curl` from the Metal^3^ control plane to test connectivity to the BMCs via redfish.
88
88
* Ensure correct BMC credentials are provided in the `BareMetalHost-Secret` definition.
89
89
90
-
. *Verify turtles/CAPI/metal3 pod status*: Ensure the containers on the management cluster are up and running: `kubectl get pods -n metal3-system` and `kubectl get pods -n rancher-turtles-system` (also see `capi-system`, `capm3-system`, `rke2-bootstrap-system` and `rke2-control-plane-system`).
90
+
. *Verify turtles/CAPI/metal3 pod status*: Ensure the containers on the management cluster are up and running: `kubectl get pods -n metal3-system` and `kubectl get pods -n cattle-turtles-system` (also see `cattle-capi-system`, `capm3-system`, `rke2-bootstrap-system` and `rke2-control-plane-system`).
91
91
92
92
. *Verify the ironic endpoint is reachable from the host being provisioned*: The host being provisioned needs to be able to reach out the Ironic endpoint to report back to Metal^3^. Check the IP with `kubectl get svc -n metal3-system metal3-metal3-ironic` and try to reach it via `curl/nc`.
0 commit comments