Channels
extensions
rancher-extensions
supermicro-sixsq
ozt
os
one-point-x
rio
onlinemeetup
v16-v21-migration
events
onlinetraining
training-1220
training-0110
training-0124
k3s-contributor
submariner
storage
k3os
windows
ci-cd
theranchcast
rfed_ara
nederlands
ukranian
danish
training-0131
masterclass
training-0207
training-0214
terraform-controller
epinio
phillydotnet
swarm
rancher-wrangler
deutsch
russian
chinese
mesos
français
japanese
arm
longhorn-dev
terraform-provider-rke
service-mesh
azure
gcp
academy
random
elemental
espanol
lima
harvester-dev
portugues
kubernetes
kim
hypper
kubewarden
opni
logging
neuvector-security
rancher-setup
developer
office-hours
mexico
cabpr
rke
vsphere
longhorn-storage
k3s
k3d
terraform-provider-rancher2
fleet
amazon
harvester
rke2
s3gw
hobbyfarm
rancher-desktop
general
Title
c
creamy-autumn-87994
12/19/2022, 9:41 PMSo if I’m reading the page Setting up Kubernetes Clusters in Rancher correctly, I will not have a few of the abilities at the bottom of the table if I import a vanilla on-prem virtual machine k8s.io cluster into Rancher?
Will I have full compatibility if I install vanilla k8s.io kubernetes if it’s done through rancher? (I’m not limited to deploying RKE1/RKE2 in rancher?)
c
creamy-pencil-82913
12/19/2022, 10:40 PMYou can import any cluster into Rancher
You can also provision downstream clusters using rancher. If the control-plane is hosted by a cloud-provider (gke/aks/eks) then that counts as provisioned. If you want to provision to bare-metal nodes, then you must use RKE, RKE2, or K3s.
Internally and historically we have referred to things as “provisioned” or “imported”, that page uses “launched” or “registered” for the same meanings.
c
creamy-autumn-87994
12/20/2022, 12:58 AM@creamy-pencil-82913 Thank you, that helps!