suse-edge/Factory
SHA256
17
0
Fork 18
Code Issues Pull Requests 4 Actions Packages Projects Releases Wiki Activity

rancher-turtles: Add new rancher-turtles-providers chart #318

Merged
steven.hardy merged 1 commits from steven.hardy/Factory:turtles_providers into main 2025-12-05 12:45:56 +01:00
Conversation 7 Commits 1 Files Changed 9 +666
steven.hardy commented 2025-11-28 15:58:08 +01:00
Owner
Copy Link

This aligns with the new chart for the certified providers,
but we remove all those not supported as part of the Edge product
and add CAPM3

Note it's +up0.0.0 because https://github.com/rancher/turtles/tree/main/charts/rancher-turtles-providers doesn't yet have any tagged releases (this is planned alongside Rancher 2.13

This aligns with the new chart for the certified providers, but we remove all those not supported as part of the Edge product and add CAPM3 Note it's +up0.0.0 because https://github.com/rancher/turtles/tree/main/charts/rancher-turtles-providers doesn't yet have any tagged releases (this is planned alongside Rancher 2.13
steven.hardy requested review from fdegirmenci 2025-11-28 15:58:08 +01:00
steven.hardy requested review from nbelouin 2025-11-28 15:58:09 +01:00
steven.hardy commented 2025-11-28 16:09:47 +01:00
Author
Owner
Copy Link

@nbelouin I forgot to add this to the release manifest, but since the manifest check is passing perhaps it makes sense to merge this first to enable testing, then when fully proven e.g in SV we can remove the old rancher-turtles charts and update the manifest?

@nbelouin I forgot to add this to the release manifest, but since the manifest check is passing perhaps it makes sense to merge this first to enable testing, then when fully proven e.g in SV we can remove the old rancher-turtles charts and update the manifest?
nbelouin requested changes 2025-11-28 16:49:50 +01:00
Dismissed
nbelouin left a comment
Owner
Copy Link

Missing the _service file, otherwise LGTM
For the release manifest, I'm okay with that, it passes because it only checks that our charts present in release manifest are correct.

Missing the `_service` file, otherwise LGTM For the release manifest, I'm okay with that, it passes because it only checks that our charts present in release manifest are correct.
fdegirmenci requested review from kzhelyazkov 2025-12-01 08:37:57 +01:00
fdegirmenci commented 2025-12-01 08:38:23 +01:00
Owner
Copy Link

We'll give this a try however we need OBS build fixed to be able to do that.

We'll give this a try however we need OBS build fixed to be able to do that.
steven.hardy commented 2025-12-01 10:17:50 +01:00
Author
Owner
Copy Link

@fdegirmenci OBS build now working - I also pushed some WIP docs updates

For the non-airgap scenario the updates are basically:

  • Instead of installing the rancher-turtles chart we install this new rancher-turtles-providers chart (note the target namespace changed it's now cattle-turtles-system to match where Rancher installs the other turtles components in 2.13)
  • Remove the embedded-cluster-api Feature CR from the metal3.sh script, and also the deletion of the webhooks

If we're validating the deployments in SV note that some namespaces changed:

  • The rancher-turtles controller now runs in cattle-turtles-system
  • The core CAPI controller now runs in cattle-capi-system
  • The fleet provider controller now runs in fleet-addon-system

Also note that there are some upstream images currently (I'm testing the community rancher-2.13.0-rc4 and apparently this is expected so we may have to allow it until there's a Rancher Prime RC we can test)

> for ns in cattle-capi-system capm3-system cattle-turtles-system metal3-ipam-system fleet-addon-system rke2-bootstrap-system rke2-control-plane-system; do kubectl get deployment -n $ns -o yaml | grep "image:"; done
          image: registry.k8s.io/cluster-api/cluster-api-controller:v1.10.6
          image: registry.suse.com/rancher/cluster-api-provider-metal3:v1.10.4
          image: rancher/turtles:v0.25.0
          image: registry.rancher.com/rancher/ip-address-manager:v1.10.4
        - image: ghcr.io/rancher/cluster-api-addon-provider-fleet:v0.12.0
          image: ghcr.io/rancher/cluster-api-addon-provider-fleet:v0.12.0
          image: ghcr.io/rancher/cluster-api-provider-rke2-bootstrap:v0.21.1
          image: ghcr.io/rancher/cluster-api-provider-rke2-controlplane:v0.21.1
@fdegirmenci OBS build now working - I also pushed some [WIP docs updates](https://github.com/hardys/suse-edge.github.io/commit/00496cf60eefb1354c3684216c84f86e971d5229) For the non-airgap scenario the updates are basically: * Instead of installing the rancher-turtles chart we install this new rancher-turtles-providers chart (note the target namespace changed it's now `cattle-turtles-system` to match where Rancher installs the other turtles components in 2.13) * Remove the `embedded-cluster-api` Feature CR from the `metal3.sh` script, and also the deletion of the webhooks If we're validating the deployments in SV note that some namespaces changed: * The rancher-turtles controller now runs in `cattle-turtles-system` * The core CAPI controller now runs in `cattle-capi-system` * The fleet provider controller now runs in `fleet-addon-system` Also note that there are some upstream images currently (I'm testing the community rancher-2.13.0-rc4 and apparently this is expected so we may have to allow it until there's a Rancher Prime RC we can test) ``` > for ns in cattle-capi-system capm3-system cattle-turtles-system metal3-ipam-system fleet-addon-system rke2-bootstrap-system rke2-control-plane-system; do kubectl get deployment -n $ns -o yaml | grep "image:"; done image: registry.k8s.io/cluster-api/cluster-api-controller:v1.10.6 image: registry.suse.com/rancher/cluster-api-provider-metal3:v1.10.4 image: rancher/turtles:v0.25.0 image: registry.rancher.com/rancher/ip-address-manager:v1.10.4 - image: ghcr.io/rancher/cluster-api-addon-provider-fleet:v0.12.0 image: ghcr.io/rancher/cluster-api-addon-provider-fleet:v0.12.0 image: ghcr.io/rancher/cluster-api-provider-rke2-bootstrap:v0.21.1 image: ghcr.io/rancher/cluster-api-provider-rke2-controlplane:v0.21.1 ```
steven.hardy added 1 commit 2025-12-02 18:50:30 +01:00
rancher-turtles: Add new rancher-turtles-providers chart
All checks were successful
Check Release Manifest Local Charts Versions / Check Release Manifest Local Charts Versions (pull_request) Successful in 9s
Details
Build PR in OBS / Build PR in OBS (pull_request_target) Successful in 13s
Details
9058c6e48b 
This aligns with the new chart for the certified providers,
but we remove all those not supported as part of the Edge product
and add CAPM3
steven.hardy commented 2025-12-02 18:52:05 +01:00
Author
Owner
Copy Link

Updated with an image repo override in the ClusterctlConfig so we're using mostly downstream images (this is a community rancher 2.13-rc4 environment, the rancher/turtles one should be taken care of by switching to the prime builds

          image: registry.suse.com/rancher/cluster-api-controller:v1.10.6
          image: registry.suse.com/rancher/cluster-api-provider-metal3:v1.10.4
          image: rancher/turtles:v0.25.0
          image: registry.rancher.com/rancher/ip-address-manager:v1.10.4
        - image: registry.suse.com/rancher/cluster-api-addon-provider-fleet:v0.12.0
          image: registry.suse.com/rancher/cluster-api-addon-provider-fleet:v0.12.0
          image: registry.suse.com/rancher/cluster-api-provider-rke2-bootstrap:v0.21.1
          image: registry.suse.com/rancher/cluster-api-provider-rke2-controlplane:v0.21.1
Updated with an image repo override in the ClusterctlConfig so we're using mostly downstream images (this is a community rancher 2.13-rc4 environment, the `rancher/turtles` one should be taken care of by switching to the prime builds ``` image: registry.suse.com/rancher/cluster-api-controller:v1.10.6 image: registry.suse.com/rancher/cluster-api-provider-metal3:v1.10.4 image: rancher/turtles:v0.25.0 image: registry.rancher.com/rancher/ip-address-manager:v1.10.4 - image: registry.suse.com/rancher/cluster-api-addon-provider-fleet:v0.12.0 image: registry.suse.com/rancher/cluster-api-addon-provider-fleet:v0.12.0 image: registry.suse.com/rancher/cluster-api-provider-rke2-bootstrap:v0.21.1 image: registry.suse.com/rancher/cluster-api-provider-rke2-controlplane:v0.21.1 ```
nbelouin approved these changes 2025-12-03 11:16:47 +01:00
steven.hardy commented 2025-12-05 12:45:11 +01:00
Author
Owner
Copy Link

I'll merge this iteration then follow up with changes to enable airgap testing, and we can remove the old charts when ready and add this to the release manifest for 3.5

I'll merge this iteration then follow up with changes to enable airgap testing, and we can remove the old charts when ready and add this to the release manifest for 3.5
steven.hardy merged commit 1827d8708d into main 2025-12-05 12:45:56 +01:00
steven.hardy deleted branch turtles_providers 2025-12-05 12:45:56 +01:00
Sign in to join this conversation.
Reviewers
No Reviewers
fdegirmenci
kzhelyazkov
nbelouin
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
amorgante antaloala atanasdinov atrendafilov dbekhit dprodanov eminguez fdegirmenci geoagriogiannis ipetrov117 jarndt jtomasek kzhelyazkov mchiappero mkrutov nbelouin roxenham steven.hardy
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: suse-edge/Factory#318
Delete Branch "steven.hardy/Factory:turtles_providers"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?