Skip to content

Conversation

@evrardjp
Copy link
Collaborator

@evrardjp evrardjp commented Jan 6, 2026

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

Now that a new kind version is released supporting 1.35,
we can use it for our CI testing.

This commit:
- Bumps the kind version and its images to support the 1.35
- Ensure all the API calls are done with client-go (and other k8s deps)
  supporting a maximum ranges of versions (0.34)
- Aligns Kured go version with k8s 0.34 go version.

Signed-off-by: Jean-Philippe Evrard <open-source@a.spamming.party>
@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 from 250272b to e0d5404 Compare January 6, 2026 21:38
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 e0d5404 to 29c3f5c Compare January 6, 2026 21:42
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