This message was deleted.
# rke2
a
This message was deleted.
1
c
the default for RKE2 standalone is not the same as Rancher’s default when provisioning clusters.
👍 1
Pick the one you want, based on your requirements
n
Thanks. In this situation, is it still accurate that Canal is the only one with FIPS-compliance out of the box? This is the main requirement I'm looking after.
I would ask around in the CNI communities, but I figure that RKE2 users are more aware/interested in FIPS-compliance than the average k8s user 🙂
c
You can see in the release notes which CNIs are FIPS Compliant https://github.com/rancher/rke2/releases/tag/v1.30.0%2Brke2r1 for example
1
n
Perfect, thank you!
> the default for RKE2 standalone is not the same as Rancher’s default when provisioning clusters. @creamy-pencil-82913 Out of curiosity, is there a particular reasoning for this? It's not immediately clear to me why say Canal couldn't also be the default when provisioning a new cluster.
c
backwards compatibility with RKE1
n
Canal is also supported by RKE1 though, is it not? So, backwards compatibility in which sense?
c
backwards compatibility in terms of what you get by default when you provision a cluster from rancher
n
Ah I see, thanks