Images with -rc

rancher/aks-operator:v1.13.2-rc.1
rancher/backup-restore-operator:v9.0.1-rc.1
rancher/compliance-operator:v1.3.2-rc.1
rancher/eks-operator:v1.13.2-rc.1
rancher/gke-operator:v1.13.2-rc.1
rancher/rancher-agent:v2.13.2-alpha4
rancher/rancher-webhook:v0.9.2-rc.1
rancher/rancher:v2.13.2-alpha4
rancher/rke2-cloud-provider:v1.32.0-rc3.0.20241220224140-68fbd1a6b543-build20250101
rancher/rke2-cloud-provider:v1.32.5-rc1.0.20250516182639-8e8f2a4726fd-build20250612
rancher/rke2-cloud-provider:v1.32.8-rc1.0.20250814215348-fe896f7e7cf8-build20250908
rancher/rke2-cloud-provider:v1.33.0-rc1.0.20250430074337-dc03cb4b3faa-build20250430
rancher/rke2-cloud-provider:v1.33.0-rc1.0.20250905195603-857412ae5891-build20250908
rancher/rke2-cloud-provider:v1.33.4-rc1.0.20250814212538-148243c49519-build20250908
rancher/security-scan:v0.8.2-rc.1
rancher/turtles:v0.25.2-rc.0

Components with -rc

DASHBOARD_UI_VERSION v2.13.2-alpha2
UI_VERSION 2.13.2-alpha2

Min version components with -rc

Chart/KDM sources

• CHART_DEFAULT_BRANCH: dev-v2.13 (scripts/package-env)
• CHART_DEFAULT_BRANCH: dev-v2.13 (package/Dockerfile)
• CATTLE_KDM_BRANCH: dev-v2.13 (package/Dockerfile)
• CATTLE_KDM_BRANCH: dev-v2.13 (Dockerfile.dapper)
• KDMBranch: dev-v2.13 (pkg/settings/setting.go)
• ChartDefaultBranch: dev-v2.13 (pkg/settings/setting.go)

Images with -rc

rancher/backup-restore-operator:v9.0.1-rc.1
rancher/compliance-operator:v1.3.2-rc.1
rancher/eks-operator:v1.13.2-rc.1
rancher/gke-operator:v1.13.2-rc.1
rancher/rancher-agent:v2.13.2-alpha3
rancher/rancher-webhook:v0.9.2-rc.1
rancher/rancher:v2.13.2-alpha3
rancher/rke2-cloud-provider:v1.32.0-rc3.0.20241220224140-68fbd1a6b543-build20250101
rancher/rke2-cloud-provider:v1.32.5-rc1.0.20250516182639-8e8f2a4726fd-build20250612
rancher/rke2-cloud-provider:v1.32.8-rc1.0.20250814215348-fe896f7e7cf8-build20250908
rancher/rke2-cloud-provider:v1.33.0-rc1.0.20250430074337-dc03cb4b3faa-build20250430
rancher/rke2-cloud-provider:v1.33.0-rc1.0.20250905195603-857412ae5891-build20250908
rancher/rke2-cloud-provider:v1.33.4-rc1.0.20250814212538-148243c49519-build20250908
rancher/security-scan:v0.8.2-rc.1
rancher/turtles:v0.25.2-rc.0

Components with -rc

DASHBOARD_UI_VERSION v2.13.2-alpha1
UI_VERSION 2.13.2-alpha1

Min version components with -rc

Chart/KDM sources

• CHART_DEFAULT_BRANCH: dev-v2.13 (scripts/package-env)
• CHART_DEFAULT_BRANCH: dev-v2.13 (package/Dockerfile)
• CATTLE_KDM_BRANCH: dev-v2.13 (package/Dockerfile)
• CATTLE_KDM_BRANCH: dev-v2.13 (Dockerfile.dapper)
• KDMBranch: dev-v2.13 (pkg/settings/setting.go)
• ChartDefaultBranch: dev-v2.13 (pkg/settings/setting.go)

Images with -rc

rancher/compliance-operator:v1.3.2-rc.1
rancher/rancher-agent:v2.13.2-alpha2
rancher/rancher:v2.13.2-alpha2
rancher/rke2-cloud-provider:v1.32.0-rc3.0.20241220224140-68fbd1a6b543-build20250101
rancher/rke2-cloud-provider:v1.32.5-rc1.0.20250516182639-8e8f2a4726fd-build20250612
rancher/rke2-cloud-provider:v1.32.8-rc1.0.20250814215348-fe896f7e7cf8-build20250908
rancher/rke2-cloud-provider:v1.33.0-rc1.0.20250430074337-dc03cb4b3faa-build20250430
rancher/rke2-cloud-provider:v1.33.0-rc1.0.20250905195603-857412ae5891-build20250908
rancher/rke2-cloud-provider:v1.33.4-rc1.0.20250814212538-148243c49519-build20250908
rancher/security-scan:v0.8.2-rc.1
rancher/turtles:v0.25.2-rc.0

Components with -rc

DASHBOARD_UI_VERSION v2.13.2-alpha1
UI_VERSION 2.13.2-alpha1

Min version components with -rc

Chart/KDM sources

• CHART_DEFAULT_BRANCH: dev-v2.13 (scripts/package-env)
• CHART_DEFAULT_BRANCH: dev-v2.13 (package/Dockerfile)
• CATTLE_KDM_BRANCH: dev-v2.13 (package/Dockerfile)
• CATTLE_KDM_BRANCH: dev-v2.13 (Dockerfile.dapper)
• KDMBranch: dev-v2.13 (pkg/settings/setting.go)
• ChartDefaultBranch: dev-v2.13 (pkg/settings/setting.go)

Images with -rc

rancher/compliance-operator:v1.3.2-rc.1
rancher/rancher-agent:v2.13.2-alpha1
rancher/rancher:v2.13.2-alpha1
rancher/rke2-cloud-provider:v1.32.0-rc3.0.20241220224140-68fbd1a6b543-build20250101
rancher/rke2-cloud-provider:v1.32.5-rc1.0.20250516182639-8e8f2a4726fd-build20250612
rancher/rke2-cloud-provider:v1.32.8-rc1.0.20250814215348-fe896f7e7cf8-build20250908
rancher/rke2-cloud-provider:v1.33.0-rc1.0.20250430074337-dc03cb4b3faa-build20250430
rancher/rke2-cloud-provider:v1.33.0-rc1.0.20250905195603-857412ae5891-build20250908
rancher/rke2-cloud-provider:v1.33.4-rc1.0.20250814212538-148243c49519-build20250908
rancher/security-scan:v0.8.2-rc.1
rancher/turtles:v0.25.2-rc.0

Components with -rc

DASHBOARD_UI_VERSION v2.13.2-alpha1
UI_VERSION 2.13.2-alpha1

Min version components with -rc

Chart/KDM sources

• CHART_DEFAULT_BRANCH: dev-v2.13 (scripts/package-env)
• CHART_DEFAULT_BRANCH: dev-v2.13 (package/Dockerfile)
• CATTLE_KDM_BRANCH: dev-v2.13 (package/Dockerfile)
• CATTLE_KDM_BRANCH: dev-v2.13 (Dockerfile.dapper)
• KDMBranch: dev-v2.13 (pkg/settings/setting.go)
• ChartDefaultBranch: dev-v2.13 (pkg/settings/setting.go)

Release v2.13.1

Important: In Rancher Community v2.13.1 if your registry configuration is one of the following you may see Rancher generate the cattle-cluster-agent image with an incorrect docker.io path segment:

• Environments where a cluster-scoped container registry is configured for system images.
• Environments where a global system-default-registry is configured (e.g. airgap setups), even if no cluster-scoped registry is set.

Workaround for Affected Setups: As a workaround, override the cattle-cluster-agent image via the CATTLE_AGENT_IMAGE environment variable. This value must not contain any registry prefix (Rancher will handle that automatically). It should be set only to the repository and tag, for example:rancher/rancher-agent:v2.13.1

Helm install example:

helm install rancher rancher-latest/rancher \
...
 --set extraEnv[0].name=CATTLE_AGENT_IMAGE \
 --set extraEnv[0].value=rancher/rancher-agent:v2.13.1

Helm upgrade example:

helm upgrade rancher rancher-latest/rancher \
...
 --set extraEnv[0].name=CATTLE_AGENT_IMAGE \
 --set extraEnv[0].value=rancher/rancher-agent:v2.13.1

Important Upgrade Note:

The CATTLE_AGENT_IMAGE override is intended only as a temporary workaround for the affected configurations. Once a Rancher version is available that corrects this behavior, the CATTLE_AGENT_IMAGE override should be removed from Helm values, so that Rancher can resume managing the agent image normally and automatically track future image and tag changes. See #53187 for further information.

Important: If you are using Active Directory Federation Service (AD FS), upgrading to Rancher v2.10.1 or later may cause issues with authentication, requiring manual intervention. These issues are due to the AD FS Relying Party Trust not being able to pick up a signature verification certificate from the metadata. They can be corrected by either of two methods:

• Updating the Relying Party Trust information from federation metadata (Relying Party Trust -> Update from Federation Metadata...)
• Directly adding the certificate (Relying Party Trust -> Properties -> Signature tab -> Add -> Select the certificate).

For more information see #48655.

Important: Rancher-Istio has been deprecated in Rancher v2.12.0; turn to the SUSE Application Collection build of Istio for enhanced security (included in SUSE Rancher Prime subscriptions). Detailed information can be found in this announcement.

Rancher v2.13.1 is the latest patch release of Rancher. This is a Community version release that introduces maintenance updates and bug fixes.

For more information on new features in the general minor release see the v2.13.0 release notes.

Rancher App (Global UI)

Major Bug Fixes

• Fixed an issue where in air-gapped environments when attempting to access the legacy v3 API-UI page directly via the host URL (<RANCHER-SERVER-URL>/v3), the page fails to load and displays a blank page. See #52790.

Cluster Provisioning

Major Bug Fixes

• Fixed an issue with cluster provisioning not working as expected in air-gapped Rancher setups due to capi-controller-manager not coming up Active. See #52833 and #52495 for further information.

K3s Provisioning

Major Bug Fixes

• Fixed an issue where when attempting to provision an IPv6-only K3s cluster (either Custom or Node-Driver) with IPv6 CIDRs, the cluster would become stuck in a provisioning state and does not become Active. See #52860.

RKE2 Provisioning

Major Bug Fixes

• Fixed an issue when provisioning a Custom RKE2 cluster where the nodes are configured with IPv6-only addresses, the cluster would fail to provision correctly. Specifically, the rke2-server service on the etcd-only nodes crashes repeatedly with a fatal error: runtimes: failed to get runtime classes. As a result, the etcd node is continually seen flipping between Waiting for Node Ref and Reconciling status, preventing the cluster from reaching an Active state. See #52861.

Backup/Restore

Features and Enhancements

• The rancher/backup-restore-operator pod now supports the CPU and memory Helm chart resources requests and limits. See #786.

Harvester

Known Issues

• When upgrading to Rancher v2.13.1 while using Harvester v1.6.1, users may encounter an issue with their Load Balancers in downstream clusters using the Harvester Cloud Provider, and must perform the following workaround to instruct Calico to not use any of the IP/interface managed by kube-vip. See #9767.

Install/Upgrade Notes

• If you're installing Rancher for the first time, your environment must fulfill the installation requirements.

Important: Rancher now requires the cluster it runs on to have the Kubernetes API Aggregation Layer enabled. This is because Rancher extends Kubernetes with additional APIs by registering its own extension API server. Please note that all versions of Kubernetes supported in this Rancher versions K8s distributions (RKE2/K3s) will have the aggregation layer configured and enabled by default. Refer to the Extension API Server documentation and #50400 for more information.

Important: Rancher Kubernetes Engine (RKE/RKE1) has reached end of life as of July 31, 2025. Rancher versions 2.12.0 and later no longer support provisioning or managing downstream RKE1 clusters. We recommend replatforming RKE1 clusters to RKE2 to ensure continued support and security updates. Learn more about the transition here.

Rancher now has a pre-upgrade validation check for RKE1 resources which fails and lists the RKE1 resources if present. Refer to the RKE1 Resource Validation and Upgrade Requirements documentation and #50286 for more information.

Important: It is crucial that you review the available disk space on your nodes and plan accordingly before upgrading to Rancher v2.12.0 and later to avoid potential disk pressure and pod eviction issues. For additional information refer to the UI Server Side Pagination - Disk Space documentation.

Important: Rancher now has an enablement option called AUDIT_LOG_ENABLED for API Audit Logs for a Rancher installation. In Rancher versions 2.11.x and earlier, only the AUDIT_LEVEL could be set and the default log level (0) would disable the audit log. In Rancher versions 2.12.x and later, the default log level (0) now only contains the log request and response metadata, and can be set when configuring AUDIT_LOG_ENABLED. If installing or upgrading via Helm you can enable the API Audit Logs and specify the log level by applying the following setting to your Helm command: --set auditLog.enabled=true --set auditLog.level=0. See the Enabling the API Audit Log to Record System Events documentation and #48941.

Changes in Image Artifacts

Image artifact digests are renamed in Rancher v2.12.0, v2.11.4 and v2.10.8. Up until this change, separate image digests files for each operating system and architecture have been maintained for compatibility reasons. With this change, only one file for each operating system is to be provided:

• The rancher-images-digests-linux-amd64.txt and rancher-images-digests-linux-arm64.txt files are to be renamed to rancher-images-digests-linux.txt.
• The rancher-images-digests-windows-ltsc2019.txt and rancher-images-digests-windows-ltsc2022.txt files are to be renamed to rancher-images-digests-windows.txt.

Upgrade Requirements

• Creating backups: Create a backup before you upgrade Rancher. To roll back Rancher after an upgrade, you must first back up and restore Rancher to the previous Rancher version. Be...

Images with -rc

rancher/rancher-agent:v2.13.1-rc1
rancher/rancher:v2.13.1-rc1
rancher/rke2-cloud-provider:v1.32.0-rc3.0.20241220224140-68fbd1a6b543-build20250101
rancher/rke2-cloud-provider:v1.32.5-rc1.0.20250516182639-8e8f2a4726fd-build20250612
rancher/rke2-cloud-provider:v1.32.8-rc1.0.20250814215348-fe896f7e7cf8-build20250908
rancher/rke2-cloud-provider:v1.33.0-rc1.0.20250430074337-dc03cb4b3faa-build20250430
rancher/rke2-cloud-provider:v1.33.0-rc1.0.20250905195603-857412ae5891-build20250908
rancher/rke2-cloud-provider:v1.33.4-rc1.0.20250814212538-148243c49519-build20250908

Components with -rc

DASHBOARD_UI_VERSION v2.13.1-rc1
UI_VERSION 2.13.1-rc1

Min version components with -rc

Chart/KDM sources

• CHART_DEFAULT_BRANCH: release-v2.13 (scripts/package-env)
• CHART_DEFAULT_BRANCH: release-v2.13 (package/Dockerfile)
• CATTLE_KDM_BRANCH: release-v2.13 (package/Dockerfile)
• CATTLE_KDM_BRANCH: release-v2.13 (Dockerfile.dapper)
• KDMBranch: release-v2.13 (pkg/settings/setting.go)
• ChartDefaultBranch: release-v2.13 (pkg/settings/setting.go)