# Rancher v2.15.1

- Product: Rancher (https://whatsnew.fyi/product/rancher)
- Vendor: SUSE
- Date: 2026-08-28
- Version: v2.15.1
- Original notes: https://github.com/rancher/rancher/releases/tag/v2.15.1
- Permalink: https://whatsnew.fyi/product/rancher/releases/v2.15.1

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

- **fixed** — Maintenance updates and bug fixes

#### Release v2.15.1

> [!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. For more information, see [\#48655](https://github.com/rancher/rancher/issues/48655). These issues 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).

Rancher v2.15.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.15.0 release notes](https://github.com/rancher/rancher/releases/tag/v2.15.0).

##### K3s and RKE2 Provisioning

###### Known Issues

- A known issue exists related to CAPI infrastructure providers within Rancher’s V2 provisioning framework. Creating or editing v2prov clusters with native infrastructure providers (such as CAPA or CAPV) from the UI can under some failure conditions leave unused, orphaned infrastructure resources (e.g., `AWSMachineTemplate` or `AWSCluster`) in the management cluster which need to be cleaned up manually. See [\#55752](https://github.com/rancher/rancher/issues/55752).

##### Changes Since v2.15.0

See the full list of [changes](https://github.com/rancher/rancher/compare/v2.15.0%E2%80%A6v2.15.1).

##### Install/Upgrade Notes

If you’re installing Rancher for the first time, your environment must fulfill the [installation requirements](https://ranchermanager.docs.rancher.com/v2.15/getting-started/installation-and-upgrade/installation-requirements).

> [!IMPORTANT]
> - Rancher now requires the cluster it runs on to have the [Kubernetes API Aggregation Layer](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/) 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](https://ranchermanager.docs.rancher.com/v2.15/api/extension-apiserver#aggregation-layer-is-required) and [\#50400](https://github.com/rancher/rancher/issues/50400) for more information.
>
> - 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](https://www.suse.com/support/kb/doc/?id=000021518).
>
>   - Rancher now has a pre-upgrade validation check for RKE1 resources which fails and lists the RKE1 resources if present. Refer to [\#50286](https://github.com/rancher/rancher/issues/50286) for more information.
>
> - 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](https://ranchermanager.docs.rancher.com/v2.15/how-to-guides/advanced-user-guides/ui-server-side-pagination#disk-space).
>
> - Rancher now has an enablement option called [`AUDIT_LOG_ENABLED`](https://ranchermanager.docs.rancher.com/v2.15/how-to-guides/advanced-user-guides/enable-api-audit-log#viewing-api-audit-logs:~:text=Description-,AUDIT_LOG_ENABL

_[Truncated at 4000 characters — full notes: https://github.com/rancher/rancher/releases/tag/v2.15.1]_