What rancher/rancher shipped
Written by FoxPlug from the repository's own releases; not affiliated with Rancher. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/rancher/rancher; Rancher did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of November 2, 2026
What shipped
- Etcd is bumped to v3.7.3, which fixes multiple public security vulnerabilities. Pull request #58558
- The TLS pod-IP tracker now resolves its pod selector from the app selector, so Helm installs whose release name differs from rancher get a consistent live pod IP set across HA replicas. Pull request #58606
- New ClusterRepo objects get a Downloading condition before downloading starts, instead of showing the default Active condition. Pull request #58503
- A token's last used time is now written at most once a minute on v2.13. Pull request #58592
- A token's last used time is now written at most once a minute on v2.14. Pull request #58566
- A token's last used time is now written at most once a minute on v2.15. Pull request #58565
- Client-facing status codes are kept on ext.Token backing errors on v2.15. Pull request #58557
- Local user passwords can be set on v2.15 without depending on the webhook. Pull request #58546
- SCIM login now merges attributes on v2.15. Pull request #58550
- User and cluster-create role permissions are fixed on v2.15. Pull request #58433
Why it matters
This week covers security and correctness fixes that affect how clusters and repos report state, and how user identity is handled. etcd is bumped to a release that fixes public security vulnerabilities, and users are asked to update as soon as reasonably possible. Several fixes land across the supported release lines, including token last-used writes, SCIM login, local user passwords and role permissions.
Changelog entry
- Bump etcd to v3.7.3, fixing multiple public security vulnerabilities. Pull request #58558
- Resolve the TLS pod-IP tracker's pod selector from the app selector so Helm installs with non-default release names agree on the live pod IP set. Pull request #58606
- Set a ClusterRepo's condition to Downloading before downloading starts. Pull request #58503
- Write a token's last used time at most once a minute (v2.13). Pull request #58592
- Write a token's last used time at most once a minute (v2.14). Pull request #58566
- Write a token's last used time at most once a minute (v2.15). Pull request #58565
- Keep client-facing status codes on ext.Token backing errors (v2.15). Pull request #58557
- Set local user passwords without depending on the webhook (v2.15). Pull request #58546
- Merge attributes on SCIM login (v2.15). Pull request #58550
- Move the SCIM provider config reader into its own package (v2.15). Pull request #58548
- Fix user and cluster-create role permissions (v2.15). Pull request #58433
- Update Fleet to v0.17.0-beta.3 (111.0.0+up0.17.0-beta.3). Pull request #58536
This week: etcd bumped to v3.7.3 for public security fixes, TLS pod-IP tracking fixed for Helm installs with non-default release names, ClusterRepo now reports Downloading before it downloads, and token last-used writes are throttled across release lines.
Changes in rancher/rancher this week: etcd is bumped to v3.7.3, which fixes multiple public security vulnerabilities, and users are asked to update as soon as reasonably possible. The TLS pod-IP tracker now resolves its pod selector from the app selector, so Helm installs whose release name differs from rancher no longer see replicas disagree on the live pod IP set. New ClusterRepo objects get a Downloading condition before downloading starts, instead of showing the default Active condition. Token last-used times are written at most once a minute, and fixes for SCIM login attributes, local user passwords and role permissions land across supported release lines.
Week of October 26, 2026
What shipped
- Creating an ext.Token of kind session through the API is now rejected so users cannot forge login sessions. Pull request #58332
- Ext.Token objects of kind session are now limited to the login session lifetime instead of the general token TTL, and status updates are rejected. Pull request #58339
- The same TTL limits now apply to both v3 tokens and ext tokens, so kubeconfig tokens no longer get different lifetimes by token type. Pull request #58414
- The main build is fixed after the session token kind rename, with the login check moved to the session kind and tests updated. Pull request #58455
- The pod-IP TLS filter now resolves the pod selector from the app selector environment variable instead of a hardcoded app=rancher label. Pull request #57720
- Restore mode and improper IP configuration issues are fixed, including reinstalling on the correct Kubernetes version and selecting the right IP family. Pull request #58360
- The PC PDB fix is backported to release/v2.15. Pull request #58461
- The PC PDB fix is backported to release/v2.14. Pull request #58462
- Agent and server images are built using Go from the SUSE Application Collection, with leftover airgap build tags removed. Pull request #57594
- The airgap tool is reworked to avoid a CGO dependency, enabling a change of Go builder environment. Pull request #58415
Why it matters
This week brings tighter control over session tokens, closing the gap that let session tokens use the general token TTL and rejecting session tokens created directly through the API. It also fixes token TTL consistency between v3 and ext tokens, a main branch build break after the token kind rename, and TLS certificate pod selection. Point releases across supported lines carry dashboard updates, chart reference fixes and remotedialer proxy bumps.
Changelog entry
- Reject creating ext.Token objects of kind session through the API. Pull request #58332
- Limit session ext.Token to the login session lifetime and reject status updates. Pull request #58339
- Apply the same TTL limits to v3 and ext tokens. Pull request #58414
- Fix the main build after the session token kind rename. Pull request #58455
- Resolve the pod selector for TLS certificates from the app selector environment. Pull request #57720
- Fix restore mode and improper IP configuration issues, including reinstall on the correct Kubernetes version. Pull request #58360
- Backport the PC PDB fix to release/v2.15. Pull request #58461
- Backport the PC PDB fix to release/v2.14. Pull request #58462
- Build agent and server images using Go from the SUSE Application Collection. Pull request #57594
- Rework the airgap tool to avoid a CGO dependency. Pull request #58415
- Release v2.15.3. Release
- Update Dashboard refs to v2.12.15, v2.11.19, v2.13.11 and v2.14.7. Release
Rancher this week: session ext.Tokens can no longer be created via the API and are limited to the login session lifetime; v3 and ext token TTLs now match. Also fixed: the main build after the token kind rename, TLS pod selector resolution, and restore mode IP config. Point releas
This week in Rancher: creating ext.Token objects of kind session through the API is now rejected, and session tokens are limited to the login session lifetime instead of the general token default. The same TTL rules now apply to v3 and ext tokens. We also fixed the main build after the session token kind rename, resolved the TLS pod selector from the app selector environment instead of a hardcoded label, and fixed restore mode and IP configuration issues. Point releases shipped for v2.11, v2.12, v2.13, v2.14 and v2.15 with dashboard updates and chart reference fixes, plus remotedialer proxy bumps on several lines.
Week of October 19, 2026
What shipped
- Catalog repository resets now rebuild a truncated git index instead of failing with an io.EOF error after an interrupted write. Pull request #58318
- Catalog content from a bundled repo is served by a replica only after that replica has restored it, avoiding shared status misleading content requests. Pull request #58300
- Roletemplate aggregation is now disabled by default in v2.16.0 following last-minute bugs before the release. Pull request #58265
- Meta proxy error handling was fixed, with unit tests added. Pull request #58241
- Meta proxy header handling was fixed, with unit tests added. Pull request #58223
- The SCC Operator image was updated to v0.5.3-rc.2 on main. Pull request #58255
- System-agent was bumped to v0.16.0-rc.5 on main. Pull request #58269
- Fleet was updated to v0.16.3 for release v2.15. Pull request #58285
- A Go toolchain was added to v2.15 to make building Rancher in dev environments less restrictive. Pull request #58271
- The rancher-assets auto-approve workflow now uses a Vault permission set token instead of a minted GitHub App token. Pull request #58311
Why it matters
This week brings fixes for catalog repositories that could stall on a truncated git index or serve content before a replica restored it, plus meta proxy fixes for errors and headers. Release lines received dependency bumps including Fleet, SCC Operator, system-agent, machine and kube-api-auth. The roletemplate aggregation feature is off by default in v2.16.0 because of last-minute bugs, and a Go toolchain was added to v2.15 for easier dev builds.
Changelog entry
- Rebuild a truncated git index when resetting a catalog repository. Pull request #58318
- Serve catalog content from a bundled repo only after the replica has restored it. Pull request #58300
- Disable roletemplate aggregation by default in v2.16.0. Pull request #58265
- Fix meta proxy error handling. Pull request #58241
- Fix meta proxy header handling. Pull request #58223
- Use a Vault permission set token for rancher-assets auto-approve. Pull request #58311
- Bump system-agent to v0.16.0-rc.5 on main. Pull request #58269
- Update Fleet to v0.16.3 for release v2.15. Pull request #58285
- Update SCC Operator to v0.5.3-rc.2 on main. Pull request #58255
- Add Go toolchain on v2.15. Pull request #58271
- Bump kube-api-auth to v0.15.4-rc.1 on v2.15. Pull request #58247
- Bump machine to v0.15.0-rancher145.3-rc.2 on v2.15. Pull request #58301
This week: catalog repos recover from a truncated git index and only serve bundled content after a replica restores it. Meta proxy error and header handling fixed. Roletemplate aggregation off by default in v2.16.0. Fleet, SCC Operator, system-agent and kube-api-auth bumps across
This week in Rancher: catalog repository resets now rebuild a truncated git index left by an interrupted write, and bundled catalog content is served by a replica only after that replica has restored it. Meta proxy error handling and header handling were fixed with unit tests, and roletemplate aggregation is disabled by default in v2.16.0 due to last-minute bugs. Dependency updates landed across release lines, including Fleet v0.16.3 for v2.15, SCC Operator v0.5.3-rc.2, system-agent v0.16.0-rc.5, and kube-api-auth and machine bumps. A Go toolchain was also added to v2.15.
Week of October 12, 2026
What shipped
- Cluster agent is no longer deployed with an empty registration token when a cluster's token secret name is missing during upgrade. Pull request #57887
- Explicit nulls in chartValues on the RKEControlPlane are now preserved instead of being dropped. Pull request #57295
- Audit logs now show real usernames at the top level instead of only Rancher user IDs. Pull request #58008
- The token-file is now always written during an etcd restore, so nodes can join a server specified in configuration. Pull request #57960
- A stale false status condition on a namespace is now checked and cleared when a none change occurs. Pull request #58017
- Downstream cluster controllers are no longer retried after a failed start. Pull request #58040
- Users with the authn-manage role can now create AuthConfigs, not just modify existing ones. Pull request #58002
- A new TableConfiguration CRD lets shared table configurations be stored outside per-user preferences. Pull request #57751
- The last used value is now persisted when modifying an app. Pull request #57961
- Settings sourced from environment variables no longer hit the unset-value flaw, with backports to 2.12 through 2.15. Pull request #58076
Why it matters
This week tightens upgrade behavior and permissions in ways users will notice: cluster agents avoid empty registration tokens, etcd restores write the token file reliably, and authn-manage now covers creating auth configs. It also adds a TableConfiguration CRD and surfaces real usernames in audit logs, cutting manual lookups. Alongside, several fixes and dependency updates land across maintenance branches.
Changelog entry
- Do not deploy the cluster agent with an empty registration token. Pull request #57887
- Preserve explicit nulls in chartValues on the RKEControlPlane. Pull request #57295
- Show real usernames in audit log entries. Pull request #58008
- Always write the token-file during an etcd restore. Pull request #57960
- Check and clear a stale false condition on a none change for namespace status. Pull request #58017
- Stop retrying the start of downstream cluster controllers. Pull request #58040
- Allow users with the authn-manage role to create AuthConfigs. Pull request #58002
- Add the TableConfiguration CRD. Pull request #57751
- Persist last used when modifying an app. Pull request #57961
- Fix Settings sourced from environment variables being unset. Pull request #58076
- Replace deprecated YAML modules with maintained ones. Pull request #58011
- Update the SCC Operator image to v0.5.3-rc.1. Pull request #57956
This week in Rancher: cluster agent no longer deploys with an empty registration token, chartValues nulls are preserved on RKEControlPlane, audit logs show real usernames, authn-manage can create AuthConfigs, and a new TableConfiguration CRD arrives.
This week in Rancher: the cluster agent is no longer deployed with an empty registration token during upgrade, explicit nulls in chartValues on the RKEControlPlane are preserved, and audit logs now show real usernames instead of only user IDs. Users with the authn-manage role can create AuthConfigs, downstream cluster controllers are no longer retried after a failed start, and a new TableConfiguration CRD adds a place for shared table configuration. Backports of the settings env unset fix and SCC Operator updates also landed across maintenance branches.
Week of October 5, 2026
What shipped
- Fix management cluster name reuse so a new cluster created with the same name as a previously deleted one no longer gets stuck on leftover resources, with UID-correct failure handling in the cluster controller. Pull request #57733
- Backport the management cluster name reuse fix so older release lines get the same leftover-resource handling. Pull request #57856
- Let imported clusters have their etcd retention and automatic snapshot settings modified and restore from s3 snapshots, by writing configuration to downstream etcd nodes through the system-agent. Pull request #57135
- Centralize Kubernetes node taint handling in provisioning into a new taints utility and manage node taints and worker labels automatically. Pull request #55487
- Backport the automatic node taint and worker label management changes to the v2.15 line. Pull request #57322
- Add support for multiple authentication providers. Pull request #57533
- Add an option to prefer the Rancher proxy context for clusters with the Authorized Cluster Endpoint enabled, changing how kubeconfigs generated since v2.14 pick their current context. Pull request #57779
- Add a selector based auth annotation for machineSelectorFiles, checking that the user has get access to the Secrets and ConfigMaps referenced by the cluster. Pull request #57641
- Add a setting to name the Rancher user in kubeconfig exec entries so generated kubeconfigs identify which Rancher user they were made for. Pull request #57738
- Clean up unused infrastructure clusters and templates so templates that were never adopted are removed. Pull request #57736
Why it matters
Several fixes this week target clusters that get stuck or redeploy endlessly: name reuse for management clusters, control plane taints causing cattle-cluster-agent redeploys, and toleration scoping for the pre-bootstrap cluster agent. Imported clusters gain etcd retention, snapshot configuration, and s3 restore support, and multiple authentication providers are now supported. Kubeconfig handling also changed, with a Rancher proxy context option for ACE clusters and a setting to name the Rancher user in exec entries.
Changelog entry
- Fix management cluster name reuse so new clusters with the same name as a deleted cluster do not get stuck on leftover resources. Pull request #57733
- Allow imported clusters to modify etcd retention and automatic snapshot settings and to restore from s3 snapshots. Pull request #57135
- Add support for multiple authentication providers. Pull request #57533
- Add an option to prefer the Rancher proxy context for clusters with the Authorized Cluster Endpoint. Pull request #57779
- Centralize node taint handling in provisioning and manage node taints and worker labels automatically. Pull request #55487
- Add a selector based auth annotation for machineSelectorFiles. Pull request #57641
- Add a setting to name the Rancher user in kubeconfig exec entries. Pull request #57738
- Clean up unused infrastructure clusters and templates. Pull request #57736
- Add status messages for hosted providers gke, aks, eks and ali so cluster operation status is visible. Pull request #57532
- Allow clusters-create to view capiproviders to determine which installed UI extensions to show. Pull request #57754
- Add automation to dynamically update CATTLE_HELM_VERSION. Pull request #57776
- Do not create a local namespace for downstream clusters. Pull request #57222
This week in Rancher: management cluster name reuse fix, etcd retention and s3 restore for imported clusters, multiple auth providers, ACE proxy context option, automatic node taint and worker label management, and Fleet updates across release lines.
This week in Rancher brought a mix of fixes and features. Management cluster name reuse is fixed so a new cluster created with the same name as a deleted one no longer gets stuck on leftover resources. Imported clusters can now have their etcd retention and automatic snapshot settings modified and can restore from s3 snapshots. Support for multiple authentication providers was added, and clusters with the Authorized Cluster Endpoint enabled can prefer the Rancher proxy context in generated kubeconfigs. Node taint handling was centralized in provisioning with automatic node taint and worker label management. Kubeconfigs can now name the Rancher user in exec entries, and Fleet was updated across release lines.
Week of September 28, 2026
What shipped
- Added configurable Content-Security-Policy header support via the ui-csp-policy setting, which can be disabled by setting it to none. Pull request #57032
- LDAP/AD authentication now supports configurable principal ID attributes instead of always using Distinguished Name, preventing RBAC binding breakage when users move between OUs. Pull request #54912
- Fixed SCIM login to preserve user attributes including external ID and email during provider refresh instead of replacing them. Pull request #57682
- SCIM is now a Prime-only feature, with status reporting prime and remaining disabled on non-Prime builds. Pull request #57622
- Migrated cattle-cluster-agent entrypoint logic from shell scripts to Go code, replacing external tool dependencies like curl with Go standard library alternatives. Pull request #55860
- SCIM audit logs now record the identity provider and request bodies for better auditability. Pull request #57615
- Fleet workspace namespaces are now automatically created when users set custom fleetWorkspaceName for imported clusters. Pull request #57358
- Fixed endless cattle-cluster-agent redeployment caused by control plane taints. Pull request #57355
- Extended tracing to record cluster cluster-role activity, CRTB activity, relevant cluster and Rancher instance information. Pull request #57614
- Removed openssl and patterns-base-fips from server image to reduce CVE exposure. Pull request #55733
Why it matters
This week includes authentication improvements for LDAP/AD and SCIM providers with better attribute handling and auditability, security enhancements to reduce CVE surface area, and stability fixes for the test infrastructure and agent deployment. These changes address user management reliability and security posture.
Changelog entry
- Add configurable Content-Security-Policy header via ui-csp-policy setting Pull request #57032
- LDAP/AD: Allow configurable principal ID attribute instead of always using DN Pull request #54912
- Fix SCIM login to preserve user attributes during provider refresh Pull request #57682
- Make SCIM a Prime-only feature Pull request #57622
- Migrate cattle-cluster-agent entrypoint to Go code Pull request #55860
- Record SCIM identity provider and request bodies in audit logs Pull request #57615
- Auto-create fleet workspace namespaces for custom fleetWorkspaceName Pull request #57358
- Fix endless cattle-cluster-agent redeploy caused by control plane taints Pull request #57355
- Extended tracing for cluster cluster-role and CRTB activity Pull request #57614
- Remove openssl and patterns-base-fips from server image Pull request #55733
- Fix flaky RBAC e2e tests by checking for finalizers Pull request #57680
- Add feature gate for LDAP/AD search as prime feature Pull request #57628
V2.15.2-hotfix and v2.13.10-hotfix released with tracing improvements. Main branch shipping LDAP/AD principal ID configuration, SCIM attribute fixes, CSP headers, and agent entrypoint rewrite.
This week's Rancher updates focus on authentication and security. LDAP/AD admins can now configure principal ID attributes to prevent RBAC breakage during OU migrations. SCIM improvements preserve user attributes during refresh and add comprehensive audit logging. Security hardening removes unnecessary dependencies from the server image. The cattle-cluster-agent entrypoint has been rewritten in Go, eliminating external tool dependencies for better reliability.
Week of September 21, 2026
What shipped
- Released v2.15.2 with fixes for AD FS authentication issues that could occur during upgrades to v2.10.1 or later. Release
- Users can now select restore modes for etcd snapshots on imported RKE2/K3s and CAPRKE2 clusters through a new snapshotextrametadata handler. Pull request #57227
- Day2 Operations now supports certificate rotation through a new CertificateRotation CRD and controller, matching functionality from legacy provisioning. Pull request #56333
- Migrated the EKS handler from v1 to v2 with unit, integration, and validation testing. Pull request #57541
- Updated Fleet to v0.17.0-alpha.5. Pull request #57577
- OKTA LDAP provider setup now saves passwords immediately into a secret, consistent with Shibboleth behavior. Pull request #57212
- Implemented LDAP search functionality for the AD FS/SAML provider. Pull request #57021
- Added PodDisruptionBudget support to the Rancher Chart. Pull request #57560
- Improved SCC Operator Deployment security context with stricter pod and container-level security configurations. Pull request #57137
- Removed the audit log package's dependency on management data to allow auth packages to import audit logging without circular dependencies. Pull request #57603
Why it matters
This week shipped releases across multiple versions with authentication fixes, Day2 Operations enhancements for certificate rotation and restore modes, and security improvements. Several test infrastructure and dependency management improvements support ongoing stability and maintainability of the project.
Changelog entry
- Released v2.15.2 Release
- Released v2.14.6 Release
- Released v2.13.10 Release
- Released v2.12.14 Release
- Released v2.11.18 Release
- Add restore mode selection for etcd snapshot restores on imported RKE2/K3s and CAPRKE2 clusters Pull request #57227
- Add Day2 Operations support for certificate rotation Pull request #56333
- Migrate EKS handler from v1 to v2 Pull request #57541
- Update Fleet to v0.17.0-alpha.5 Pull request #57577
- Fix OKTA LDAP setup to save passwords immediately into a secret Pull request #57212
- Implement LDAP search for AD FS/SAML provider Pull request #57021
- Add PodDisruptionBudget support to Rancher Chart Pull request #57560
- Improve SCC Operator Deployment security context Pull request #57137
- Fix Helm4 wait flag to use string type instead of bool Pull request #57518
- Remove audit log package dependency on management data Pull request #57603
Rancher v2.15.2 released with AD FS authentication fixes. New features include etcd snapshot restore modes, certificate rotation for Day2 Ops, and improved security contexts for SCC deployments.
Rancher v2.15.2 is now available with critical AD FS authentication fixes for upgrades. This release brings Day2 Operations support for certificate rotation and etcd snapshot restore modes, enhanced security configurations for SCC deployments, and improved LDAP functionality for OKTA and AD FS providers. Updates also include Fleet v0.17.0-alpha.5 and PodDisruptionBudget support in the Rancher Chart.
Week of September 14, 2026
What shipped
- Fixed retry and recovery logic for failed deferred controller starts, addressing issue #54006. Pull request #57296
- Added deterministic check for last etcd node protection to manage pre-terminate annotations for etcd machines. Pull request #54202
- Added API type definitions for operation cancellation. Pull request #57392
- Updated Fleet to v0.14.11 in release/v2.13. Pull request #57436
- Updated Fleet to v0.13.16 in release/v2.12. Pull request #57437
- Updated Fleet to v0.16.2 in release/v2.15. Pull request #57440
- Updated Fleet to v0.15.7 in release/v2.14. Pull request #57438
- Updated Fleet to v0.12.20 in release/v2.11. Pull request #57439
- Fixed klipper repository URLs in image origins for v2.13 to reflect new k3s-io organization home. Pull request #57370
- Bumped remotedialer-proxy to stable v0.8.2 in release/v2.15. Pull request #57404
Why it matters
This week focused on stability improvements with controller retry fixes and etcd node protection logic, while updating core dependencies like Fleet across all supported release branches. Multiple klipper repository URL corrections ensure accurate artifact generation across releases.
Changelog entry
- Fix retry and recovery from failed deferred controller starts Pull request #57296
- Add deterministic check for last etcd node protection Pull request #54202
- Add operation cancellation API types Pull request #57392
- Update Fleet to v0.14.11 (v2.13) Pull request #57436
- Update Fleet to v0.13.16 (v2.12) Pull request #57437
- Update Fleet to v0.16.2 (v2.15) Pull request #57440
- Update Fleet to v0.15.7 (v2.14) Pull request #57438
- Update Fleet to v0.12.20 (v2.11) Pull request #57439
- Fix klipper repository URLs in image origins (v2.13) Pull request #57370
- Fix klipper repository URLs in image origins (v2.14) Pull request #57369
- Fix klipper repository URLs in image origins (v2.15) Pull request #57368
- Bump remotedialer-proxy to v0.8.2 (v2.15) Pull request #57404
- Bump remotedialer-proxy to v0.7.6 (v2.14) Pull request #57403
- Bump remotedialer-proxy to v0.6.4 (v2.13) Pull request #57402
This week: fixed controller startup recovery, added etcd node protection checks, updated Fleet and remotedialer-proxy across release branches, corrected klipper repository references.
Rancher shipped stability and dependency updates this week: controller retry and recovery fixes for failed deferred starts, deterministic etcd node protection for safe machine termination, and Fleet updates across v2.11-v2.15. Also corrected klipper repository URLs reflecting the k3s-io organization move, ensuring accurate image origin tracking in release artifacts.