Round'em up!
January 24, 2022
Round'em up!
Score 9 out of 10
Vetted Review
Verified User
Software Version
Rancher
Overall Satisfaction with SUSE Rancher
We have two installations of Rancher (prod and non-prod). each rancher instance manages multiple clusters. We are using rancher to better enable users to interact with the clusters, get visual interactions for quicker understanding, and lower the barrier to adoption of the Kubernetes ecosystem. Our Kubernetes clusters and self-managed, and run on k3s. Rancher - fleet (which comes as part of the rancher installation) enables our deployments to follow the Gitops system. Deployments are managed by the feature teams, with versioning and audit of releases done via git. The ability to scale workloads, and get new developers to adopt is so much easier than having to upscale knowledge of CLI tools.
- simplify the visualisations and relations of Kubernetes
- lots of documentation / videos / slack channel
- stable releases are prod ready, works as advertised
- the ui updates sometimes fail and hard refresh is required
- fall over / restart can be slow (room for improvement)
- SSO for rancher is limited
- simplicity
- opensource
- feature complete
- continuous improvement
- support upgrade is possible
- ability to quickly test new features / upgrades
lens installs locally and needs access (network) to the kube_api of the clusters. With Rancher, you need access to the rancher front end (UI / 443), and your clusters Kube API does not need to be exposed (even over a VPN or whitelisted ips). For security reasons, the rancher setup is more favorable
Do you think SUSE Rancher delivers good value for the price?
Yes
Are you happy with SUSE Rancher's feature set?
Yes
Did SUSE Rancher live up to sales and marketing promises?
Yes
Did implementation of SUSE Rancher go as expected?
Yes
Would you buy SUSE Rancher again?
Yes