mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-04-17 03:45:39 +00:00
a94f94128a
* Sync changes from main to v2.13.2 (#2156) * Fixed links to images * Added documentation for using the keywords option in Chart.yaml * Sync Product PR #587 (Add ec2:DescribeAvailabilityZones to control plane and etcd/worker permissions) * Revert image link change, it would break the docs website * Fixed some typos and backported docs --------- Co-authored-by: mschroeder-fzj <m.schroeder@fz-juelich.de> Co-authored-by: Billy Tat <btat@suse.com> Co-authored-by: Petr Kovar <petr.kovar@suse.com> * v2.13.2 - Rancher Manager Release Maintenance (#2160) * Update the versions table * Update the Rancher:webhook version mapping table * Update the CSP adapter compatibility matrix * Update the deprecated features table * Update release date (#2171) --------- Co-authored-by: mschroeder-fzj <m.schroeder@fz-juelich.de> Co-authored-by: Billy Tat <btat@suse.com> Co-authored-by: Petr Kovar <petr.kovar@suse.com>
1.5 KiB
1.5 KiB
title
| title |
|---|
| Deprecated Features in Rancher |
What is Rancher's deprecation policy?
The community version of Rancher follows the same deprecation policy as Rancher Prime. The official deprecation policy is documented in the Rancher Prime Deprecation Policy.
Where can I find out which features have been deprecated in Rancher?
Rancher will publish deprecated features as part of the release notes for Rancher found on GitHub. Please consult the following patch releases for deprecated features:
| Patch Version | Release Date |
|---|---|
| 2.13.2 | January 29, 2026 |
| 2.13.1 | December 18, 2025 |
| 2.13.0 | November 25, 2025 |
What can I expect when a feature is marked for deprecation?
In the release where functionality is marked as "Deprecated", it will still be available and supported allowing upgrades to follow the usual procedure. Once upgraded, users/admins should start planning to move away from the deprecated functionality before upgrading to the release it marked as removed. The recommendation for new deployments is to not use the deprecated feature.