LoginSign Up
← Back to all sparks
R

Rancher

INFRA · APIS
Velocity5.0

Kubernetes management platform for multi-cluster operations

www.rancher.com ↗

The 2.15 branch takes its own second candidate — an RBAC reconcile fix on the replica path.

branch matrixpatch roundrbac reconcilerelease automationnotes published elsewhere
◆Current state
Every live branch is mid-patch-round and they are resolving at different speeds. The 2.12 and 2.11 branches promoted to final tags carrying only the automated Dashboard ref bump. The 2.14 and 2.13 branches each cut an rc2 for a token-sync correctness fix. The newest branch, 2.15, has now cut its own rc2 for a different problem: inherited namespaced rule Roles were not being reconciled on the replica.
◆Where it's heading
The feed continues to publish the branch matrix rather than what shipped in it, because supported-branch notes live behind the Prime docs. What is readable is which branches needed a second pass and for what: the two newest lines each took a distinct correctness fix before promotion while the older lines shipped plumbing only. Entry bodies here are truncated commit subjects, so the fixes are nameable but not scopeable.
◆Prediction
Expect v2.15.1 to promote to a final tag once this candidate clears, following 2.12 and 2.11. The 2.14 and 2.13 finals carrying the token-sync fix are still outstanding in this feed.

◆Recent moves

  1. 19d ago

    2.15.1-rc2 reconciles inherited namespaced Roles on the replica

    A single-commit candidate on the newest branch, fixing inherited namespaced rule Roles not being reconciled on the replica. It is the 2.15 line's equivalent of the second pass 2.14 and 2.13 took, on a different defect.

    View source ↗
  2. 19d ago

    2.12.13 finalizes the patch round for the 2.12 branch

    Promotion to a final tag whose only visible commit is the bot-generated Dashboard ref bump. The older branches cleared this round without needing a second candidate.

    View source ↗
  3. 19d ago

    2.11.17 finalizes the patch round for the 2.11 branch

    The 2.11 mirror of the 2.12 promotion, tagged twenty seconds apart with the same automated content. One release round, counted once.

    View source ↗
  4. 19d ago

    Downstream token sync reads the hash from its backing Secret

    The correctness fix that forced a second candidate on 2.14: token hashes are now read from the backing Secret when syncing downstream. It is the one change in this window with a stated user-visible failure mode behind it.

    View source ↗
  5. 20d ago

    2.13 backport of the downstream token-sync fix

    The same token-sync change carried to the 2.13 branch. Both branches stayed in candidate rather than promoting, which is why the round has not closed.

    View source ↗
  6. 20d ago

    2.14.5-rc1 updates Dashboard refs only

    The first candidate of the round on 2.14, carrying nothing but the automated Dashboard reference bump. The substance arrived in rc2 a day later.

    View source ↗