openSUSE Leap vs. SUSE Rancher

OpenSUSE Leap is well suited for just about any Linux task. Especially I like to use it as Docker base image for my software deployments, because it has a wide variety of software packages available already precompiled and packages are well maintained - vulnerable software versions are patched in reasonable time. OpenSUSE Leap is rpm based system, and it wouldn't install Debian or other systems packages. If your software is not an rpm package then OpenSUSE Leap would not be suitable for your system.

SUSE Rancher as a management tool becomes useful on a larger scale. Small deployments not so much. If someone also requires Kubernetes capacity or storage, Rancher is an excellent choice. Also, without Kubernetes' skills, it is unlikely that Rancher deployment is going to be a success. Then again if someone else is managing your Kubernetes capacity, setting up the software's capacity will yield greater control. Rancher is not a very integrated solution similar to others in the market.

Incentivized

• Maintenance of software packages using YAST
• Availability of patches when a vulnerability is discovered
• Distribution upgrades

• Public and private cloud infrastructure providers based on K8s CAPI
• REST API that can be used to integrate company services with Rancher
• GUI that is easy to learn and use in daily operations
• Builtin GitOps automation solution based on Fleet project
• It is fully open source

• Commercial packages not always available
• Stable packages sometimes lag behind the latest releases

Incentivized

• No possibility to snapshot Projects. You can snapshot and restore the whole Kubernetes cluster, but not a Project or Namespace. For this, you have to use external tools.
• You cannot detach the Rancher-created Kubernetes clusters from Rancher management.

Overall it deserves an 8 out of 10. The platform is very easy to use as long as the UI is stable. We have had a few buggy versions in the past. However the CLI is excellent and the platform is simple to manage and maintain. It is easy to deploy and offer for company wide use which increases utilization and ROI.

Incentivized

The documentation is quite complete and there is a very active community that is willing to collaborate and answer questions for those who are just starting out.

openSUSE Leap has wide variety of already precompiled software packages in default repositories. It even has some specific packages in official repositories that are not available in other Linux distribution repositories. It is also very stable and reliable distro - we can predict when new versions will be released and when we should make system upgrades.

We started using SUSE Rancher in the early days and spent a large amount of time getting to know and love it. This was before the days of some of the likes of Amazon Web Services who may now provide a cheaper but less feature-rich alternative to SUSE Rancher, however we have yet to explore this.

Incentivized

The investment for small environments is quite significant. There has to be a compelling case to enhance the areas where SUSE Rancher brings in value to make such a financial leap. There is also a free version to test the value propositions, which will help support the user's buying decisions. More clusters, more volume, more tasks and more complexity in the environment equals more value that Rancher can provide.

Incentivized

• More effective maintenance means a smaller headcount needed for running the production servers.
• The easiness of deployment means more time we can spend on software development of company-specific applications.
• Great community support and overlap with other Linux systems mean that an answer to nearly any problem is usually one google query away.

• Shortens "Time-to-Market" factor for new business applications or implementing new functionalities. From 1 to 50 microservices-based business applications in 6 years.
• 24/7 availability, generates more money. There are many infrastructure components that are regularly powered-off for maintenance or upgrade, bur we rarely are turning off our downstream Kubernetes clusters where our business applications lives.
• Single Point of Contact with platform maintenance and development Team, eases implementation of new business applications