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
b
bright-farmer-78407
01/23/2023, 10:07 PMDoes RKE follows same End-of-Life/End-of-Support lifecycle as vanilla k8s ? Or where can I query that information for every RKE release ?
c
creamy-pencil-82913
01/23/2023, 10:14 PMSupport for minors follows the upstream release cycle. When upstream stops putting out releases on a minor, so do we.
also, I am assuming you’re asking about RKE2 and not RKE since that’s what channel you’re in.
b
bright-farmer-78407
01/23/2023, 10:25 PMYes, RKE2
So RKE2 team does not maanage EOS/EOL separately ? Or is there some programmatic way to query this information ?
c
creamy-pencil-82913
01/23/2023, 10:29 PMNope. We put out a RKE2 release for every upstream Kubernetes release. Occasionally we will put out a r2 release to fix a critical issue between upstream patch releases, but that is infrequent. When upstream stops putting out releases for a minor, we stop putting them out as well.
there is no RKE2 release schedule or support lifecycle distinct from that maintained by upstream.
b
bright-farmer-78407
01/23/2023, 10:32 PMthanks @creamy-pencil-82913 for quick help!