https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# general
a
This message was deleted.
h
Please clarify a bit what exactly you are looking for? you have a private registry so you want to know how to install Rancher from this private registry?
I always like to review the support matrix first to understand what is supported: https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-13-2/ This is link to Rancher docs https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade If you need help with pushing images to your private registry: https://docs.hauler.dev/docs/intro
s
I’m designing an air-gapped Rancher deployment (Rancher server + RKE2 downstream clusters) with a private registry for all artifacts.
From the Rancher release URLs, I can see the rancher-images.txt file, which lists all images supported by a Rancher version. However, that list appears to be superset-based, and I’d like to avoid pulling unnecessary images.
What I’m specifically looking for is a deterministic way to identify only the required images and dependencies for:
• a specific Rancher version, and • a specific target RKE2/Kubernetes version for downstream clusters
Ideally, I want to mirror only what Rancher will actually deploy (Rancher server, system charts, downstream cluster components), rather than all optional or unused images.
Is there a recommended approach or tooling (e.g. chart inspection, runtime discovery, Rancher APIs, Hauler/Hangar workflows) to derive the minimal required image set per Rancher + RKE2 version combination?
Any guidance from folks who’ve done production air-gap setups would be greatly appreciated. Thanks!
h
you can use hauler to "derive the minimal required image set per Rancher + RKE2 version combination" https://docs.hauler.dev/docs/hauler-usage/store/sync https://docs.hauler.dev/docs/guides-references/hauler-manifests
7 Views
Open in Slack
PreviousNext
Powered by