Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
a
agreeable-airplane-98995
05/19/2023, 6:36 PMHello! Following my initial message on #general, I'm redirecting my RKE2 specific questions here in a thread
RKE2:
• while RKE2 is CNCF compliant, I was surprised to see that, contrary to K3s, it isn't considered a CNCF project per se. Does this mean anything governance wise?
• Is it possible to do away with the additional features on top of the vanilla experience like the helm controller? In particular, I'd rather follow an upstream cilium chart instead of the bundled one
• Deployment wise, we're evaluating cluster api. We've seen https://github.com/rancher-sandbox/cluster-api-provider-rke2, and rancher manager docs mention using CAPI to deploy RKE2. Is this what is used by rancher?
Basically, we're already familiar with vanilla K8S, and are mainly interested in RKE2 for the hardening and compliance parts, not so much the comfort features. In this situation, is RKE2 a good fit for us?
c
creamy-pencil-82913
05/19/2023, 8:57 PM1. It's owned by suse, not cncf. Only k3s was donated to cncf. At the moment it means very little, as we have not had anyone outside suse step up to help maintain k3s so both projects are maintained by the same team, and neither have required much action by way of governance. Note that distros do not have to be owned by cncf to be certified as compliant, in fact very few are.
2. Yes, you can disable the bits you don't like.
3. No, rancher has its own provisioning framework based on capi that it uses to provision nodes. That standalone capi provisioner is experimental and not currently used by any of our supported products. This is more of a rancher question than a rke2 question though.
a
agreeable-airplane-98995
05/19/2023, 9:23 PMthank you very much for your responses!
Indeed, CAPI might be a tad young to be used industrially. So the recommended ways to install for now are either through rancher of through the tarball/script? I'll patiently wait for answers from the rancher team on the other channel 🙂