Anyone tested 1.28 yet?

[tschuering]

Hey, currently 1.28 is forbidden as value for k3s_initial_channel, so is this still not working or did anybody already some tests? Otherwise I would suggest a PR to change this. @mysticaltech

[mysticaltech]

How come, try "v1.28", and if not in the allowed values, PR most welcome 🙏

[mysticaltech]

It should work, but probably not with Cilium and Calico, as they don't support it yet to the best of my knowledge.

[maggie44]

Was this ever merged? #995

[maggie44]

I think they do support it now.

cilium/cilium#29004
https://docs.tigera.io/calico/latest/getting-started/kubernetes/requirements#kubernetes-requirements

[mysticaltech]

Thanks for the info @maggie44, will update it tonight.

[M4t7e]

I don't think they support it in one of the 1.14.* releases. Just because something was merged to the main branch does not mean it is released officially and even if it is, it does also not say in which version either. As far as I can see the changes found the way only to the 1.15.*-pre releases.

Example:

• 1.28 support is in 1.15.0-pre: https://github.com/cilium/cilium/blob/v1.15.0-pre.0/.github/actions/ginkgo/main-k8s-versions.yaml#L4
• 1.28 support is not in 1.14.4: https://github.com/cilium/cilium/blob/v1.14.4/.github/actions/ginkgo/main-k8s-versions.yaml#L4

AFAIK there is no plan to support that in any 1.14.* release and it will come in version 1.15 like I mentioned here: #995 (comment)

It is relatively easy to check the supported K8s version for different Cilium versions here: https://github.com/cilium/cilium/blob/v1.14.4/Documentation/network/kubernetes/compatibility.rst
Just change the tag to see what is supported and what not

[Silvest89]

I've been running 1.28 for ages with cilium 1.14, os and kube auto update enabled. I am currently on 1.28.3 even.
I have it at latest ;)

[mysticaltech]

Good will update tonight tonight.

[mysticaltech]

@tschuering @maggie44 v1.28 is now default in v2.10.0.