Skip to content

Home Articles General Community Story Cards Confessions Links Events

More

News Training Technologies Members

Log in Join usJoin ReadMeFeed↗

Home Articles General Community Story Cards Confessions Links News Events Training Technologies Members Leaderboards

Loading…

Shared knowledge. Real progress.
A home for the people building what comes next.

Explore

Articles
General
Community
Search

Community

Members
Leaderboards
Achievements
Community guidelines

The essentials

About ReadMeFeed
Privacy
Terms of use
Moderation policy

© 2026 ReadMeFeed. Built for the next conversation.Built by curiosity. Powered by people.

Home Community Create Inbox Profile

ReadMeFeed / Community knowledge

#version-skew

Real questions. Useful conversations. Find the people who know your stack.

All Unanswered Has answers Resolved Unresolved

Cards Compact list

Editorial question36.8K views2,005 votes0 answers1,098 following

AI-generated

Rancher Server ↔ Cluster Agent: Should stale agent pods be auto‑removed on version skew?

Goal: Determine whether Rancher should automatically remove stale cluster‑agent pods when a version mismatch is detected between the Rancher server and a downstream Kubernetes cluster, given that the memory‑leak fix in v2.5.13/v2.6.0 resolved goroutine growth but no automated cleanup exists for version‑skew scenarios. Constraints: The current behavior leaves

rancher version-skew cluster-agentLax Nea0 rep · 22 Aug 2022, 23:09 UTC