Skip to content

Fix 2.2.0 router deployment selector migration#2467

Open
c-kruse wants to merge 2 commits into
skupperproject:mainfrom
c-kruse:fix-2.2.0-router-deployment-selector-migration
Open

Fix 2.2.0 router deployment selector migration#2467
c-kruse wants to merge 2 commits into
skupperproject:mainfrom
c-kruse:fix-2.2.0-router-deployment-selector-migration

Conversation

@c-kruse
Copy link
Copy Markdown
Contributor

@c-kruse c-kruse commented May 28, 2026

Resolves Issue #2440

Reverts the change to router Deployment selectors back to pre-2.2.0 state. Adds migration to fix 2.2.0 Deployments.

c-kruse added 2 commits May 28, 2026 10:19
PR skupperproject#2363 (released in 2.2.0) added skupper.io/group to the router
Deployment's spec.selector. That change is reverted in 2.2.1+ because
Deployment selectors are immutable: a 2.2.0 Site upgraded to a
controller without the group label can never be patched in place
breaking upgrades (issue skupperproject#2440).

Detect the 2.2.0 selector at site recovery, and delete the stale
Deployment with Background propagation. The next reconcile recreates it
with the desired (pre-skupperproject#2363) selector.

Signed-off-by: Christian Kruse <christian@c-kruse.com>
@c-kruse
Copy link
Copy Markdown
Contributor Author

c-kruse commented May 28, 2026

Have been working through testing. So far I've covered this - give me shout if I'm missing something that may be interesting.

| Previous Controller Version | Controller Version | Result |
| 2.1.3 | HEAD | ✔️ |
| 2.2.0 | HEAD | ✔️ migration ran |
| HEAD | 2.1.3 | ✔️ |
| HEAD | 2.2.0 | ❌ |

I suggest that last case, a broken downgrade to 2.2.0 is something we have to accept and release note same as 2.1.3 -> 2.2.0.

@c-kruse c-kruse requested a review from hash-d May 28, 2026 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant