Skip to content
Discussion options

You must be logged in to vote

Our overnight e2es "float" the kubernetes version, as you can see in the e2e pipelines in https://github.com/projectcalico/calico/tree/release-v3.31/.semaphore/end-to-end/pipelines

We test against stable, stable-1 and stable-2. Currently k8s "stable" is 1.35, and I'm not seeing any issues with either Calico v3.30 or v3.31.

The "official" support statement is here: https://docs.tigera.io/calico/latest/getting-started/kubernetes/requirements#kubernetes-requirements, but that gets updated (with a delay) from the e2e run results - I'm sure we'll be adding 1.35 to the supported list for Calico v3.31 as soon as we get a moment.

Replies: 3 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by lwr20
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants