Skip to content

Update policy on kube versions#1268

Merged
evrardjp merged 2 commits intokubereboot:mainfrom
evrardjp:update-policy-on-kube-versions
Mar 23, 2026
Merged

Update policy on kube versions#1268
evrardjp merged 2 commits intokubereboot:mainfrom
evrardjp:update-policy-on-kube-versions

Conversation

@evrardjp
Copy link
Copy Markdown
Collaborator

@evrardjp evrardjp commented Jan 6, 2026

For the future! (This needs to be rebased on top of main when #1267 is merged)

@evrardjp evrardjp changed the title Update policy on kube versions Draft: Update policy on kube versions Jan 6, 2026
@evrardjp evrardjp force-pushed the update-policy-on-kube-versions branch 2 times, most recently from e0d5404 to 29c3f5c Compare January 6, 2026 21:42
@evrardjp
Copy link
Copy Markdown
Collaborator Author

Need rebase.

@evrardjp evrardjp force-pushed the update-policy-on-kube-versions branch 2 times, most recently from 8e13fff to 6d29f0f Compare March 19, 2026 04:56
We have historically decided to support AND TEST 3 versions
of kubernetes. For that, we lagged behind in terms of client versions.

Lagging behind one version allowed us, thanks to kubernetes client version skew,
to support 3 versions at relatively low cost.

However, maintaining 3 versions has always been a pain.
For that, we pinned old versions of kubernetes clients/api and test tooling.

In december 2025 community meeting, we decided to only maintain two
versions: the most current one, and the previous one.

This allows us to bump more regularly and be more secure.
We can also more easily use dependabot this way.

Signed-off-by: Jean-Philippe Evrard <open-source@a.spamming.party>
@evrardjp evrardjp force-pushed the update-policy-on-kube-versions branch from 6d29f0f to 168fe81 Compare March 19, 2026 05:07
@evrardjp
Copy link
Copy Markdown
Collaborator Author

We need to merge this as is and fix the actions not bumping trivy.

The latter will fail if this one hasn't merged ...

@evrardjp evrardjp changed the title Draft: Update policy on kube versions Update policy on kube versions Mar 19, 2026
Without this, the CI will fail to use trivy.

Multiple reasons:
- We used shas + tags in the past. This was to guarantee the
version matches the release. Sadly that behaviour has changed
since september 2025, and dependabot does not update anymore
the sha pinned actions unless the version is also in comment.
This will be fixed in another PR.
- Trivy releases had to be republished since trivy security
incident.
- Old releases should not be used, so bumping is necessary.

Signed-off-by: Jean-Philippe Evrard <open-source@a.spamming.party>
@evrardjp evrardjp requested a review from dharsanb March 19, 2026 18:08
@evrardjp evrardjp mentioned this pull request Mar 19, 2026
@evrardjp evrardjp merged commit 6a5dc50 into kubereboot:main Mar 23, 2026
25 checks passed
@evrardjp evrardjp deleted the update-policy-on-kube-versions branch March 23, 2026 05:46
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.

2 participants