We use Rancher 1.6 at my job and it has been widely and rapidly adopted by all of our development teams.<p>All of our processes are containerized now, even going as far as moving off license restricted (e.g. SSIS) software to open source alternatives to unify our process.<p>It's been mostly painfree, occasionally there are bugs in Rancher but nothing has been a show stopper.
Everybody who wants to run Rancher with zero initial setup can use our managed Kubernetes/Rancher service which we launched today: <a href="https://www.KubeBox.com" rel="nofollow">https://www.KubeBox.com</a><p>We are still in closed beta but if you are interested, please sign up and we will activate your account asap.<p>Personally, I think Rancher 2.0 is a fantastic add-on to any Kubernetes cluster for managing projects, users, groups, permissions and workloads and I would like to congratulate Rancher to their release.
Tried for an hour to use this version, here's some things that I struggled with:<p>- PersistantVolumeClaims: I tried to launch a Postgresql workload and didn't get a warning that I should configure EBS before<p>- I tried installing rancher on my machine and later found out that the nodes need to reach rancher<p>- I configured Pipeline with Github but I cannot find any ressource about what to do next, I assume that it is a CI service but it's not explicit
I choose Rancher 1.x for a large project at my last place, it allowed Researchers to run their algorithms wrapped up in containers. From the start Rancher was the perfect solution that checked all the boxes: really easy to use web interface, LDAP Authentication, automatic deployment of hosts, easy to wrap up deployments into catalog items. But after a few months it was just so unbelievably buggy due to the products maturity.<p>It's good to see they have got their focus right with version 2.
I've been using it with Cattle for more than a year now, I've saved thousands of dollars in PaaS bills thanks for my little Rancher cluster. I just setup a new Rancher 2.0 cluster controlplane and dashboard in Scaleway Paris with a Worker in Digital Ocean NY. I'm starting to migrate all my apps from the 1.6 to the new cluster. I haven't tried the new CI/CD thing, but it looked great in the training sessions.
Heavy rancher user here for managing Kubernetes clusters, the Rancher team has been an absolute dream to work with, fast to fix issues, and have created a super solid product. Very excited for the migration to 2.x from 1.x (:
As a heavy user of Rancher 1.6 this is amazing news!<p>The only gripe I have is the api is not as functional as 1.6, It's lacking features such as upgrading a pod. Other than that it's looking better than ever.
I have been using Rancher for almost two years now on dedicated servers. Never had any major problems and thanks to it I have saved hundreds of thousands of $.
I love the concept of Rancher for someone working in Corporate Atmosphere - where I have to install everything on the companies infrastructure and all the GKE, Fargate and Azure Kubernetes is not allowed... But the people at Rancher failed to recognize that they need to support clustering without any manual intervention to actual click through their UI to achieve clusters - give me an automated joining of clusters method - if you want me to adopt Rancher.