RancherOS 1.x is currently in a maintain-only-as-essential mode. That is to say, it is no longer being actively maintained at a code level other than addressing critical or security fixes. There are two significant reasons behind this product decision:
- Docker. The current industry requirements for a container runtime is very much evolving. Container runtimes like containerd and CRIO are now being actively considered as the default choice. RancherOS 1.x, which was specifically designed around using Docker engine only, unfortunately does not lend itself, in its current design, to this new evolving requirement. To address this situation, at Rancher Labs, we are currently working on new technologies such as K3OS that leverages k3s constructs built on containerd. When done, it is a desired outcome for us to be able to offer K3OS as a RancherOS 2.0 alternate.
- ISV Support. RancherOS was specifically designed as a minimalistic OS to support purpose-built containerized applications. It was not designed to be used as a general purpose OS (such as CentOS or Ubuntu). As such, most ISVs have not certified their software to run on RancherOS, nor does RancherOS even contain the necessary components for many of these applications to run. For the K3OS project, our outlook is to investigate the viability of technologies like AWS Bottlerocket that can be used as the default general purpose OS and leverage its ecosystem of compatible ISVs.
For customers with a currently active support subscription for RancherOS
- Commercial support continues to be available until the subscription term end date, per our terms of service described here. Upon term end date, currently active subscriptions shall not be available for renewal toward a new term, for reasons cited in the Development Status section above.
For Rancher (1.x and 2.x) customers without a separate and currently active subscription for RancherOS
- Please refer this FAQ: Does my support subscription to Rancher include support for RancherOS?
- Any assistance from Rancher Support on RancherOS topics, filed as support tickets, are not SLA-bound and shall be available on a best-effort basis only.