This message was deleted.
# rke2
a
This message was deleted.
b
we are preparing the flannel release as of today 🙂
We started ~10 minutes ago
👍 1
@eager-iron-71848 is working on it
This is the plan: 1 - Release flannel to v0.25.2 2 - Upgrade flannel version in K3s (to fix https://github.com/k3s-io/k3s/issues/9957) and use the new iptables package 3 - Bump new version in rke2-flannel of rke2-charts 4 - Add the new chart to rke2
The plan is to be part of rke2/k3s June release
5 should be the hardened flannel image for canal
w
Thanks. How is that cascade of changes from base flannel to hardened flannel to rke2 release work? Are there manual verifications along the way or is it pretty much automated? Just curious. Also would you waste your time trying to install a hardened flannel image into a pre-existing release or just wait for updated rke2 release?
b
the hardened flannel repo is pretty automated, it will detect the new version and create a PR https://github.com/rancher/image-build-flannel/blob/master/updatecli/updatecli.d/updateflannel.yaml
The rke2-charts repo which consumes the new image is also pretty automated but it sometimes require manual intervention
I would wait for the rke2 release if possible. That way you get an artifact that was thoroughly tested by our QA team
w
Thanks for the info!