Sorry guys for replying so late to this. It was really hectic as we were preparing the 2.0 launch and certainly things did not die down after. The team has been really busy preparing patch releases as we prepare to quickly address issues found by our users and customers. Let me try to summarize and provide comments to many of the concerns found in this thread:
Documentation - We admit documentation was really poor when we launched. Some of it were poor assumptions made on our part but either way, it was our fault on not making that better. Just last week, we ran an internal “doc-a-thon” where every engineer in Rancher dedicated a day to properly document the features they worked on. In the coming days, you will start seeing the new docs appear as they have been reviewed by peers, QA, and our doc writer. Rest assured, this will be corrected soon.
Installation - I think we were a bit ambitious in how many ways we wanted to provide installation. Actually, most of the pain were caused on having to deal with TLS certs. Currently, we are looking at adding a Helm chart to install Rancher as well as making configuring certs easier going forward. This should be right after 2.0.3 ships in the coming weeks.
Kubernetes Workload UX - A lot of angst were also generated by, frankly speaking, understanding k8s itself. If you already knew k8s, you probably felt this easier to use after getting your cluster up and running. If you were a previous Cattle user or never used k8s itself, it is definitely not as intuitive when compared to 1.0. We can related I can promise you that you will see improvements in our workload UX (which hopefully should replace dashboard) in the coming releases to address this. Kubernetes is a very powerful tool, but it hasn’t always been easy to understand how to fully use it, especially when compared to Docker/Compose (Cattle). This isn’t something I’ll be honest can’t be instantly addressed as a bug fix because it require some thought to how to best present this UX to our users. It’s been also a challenge for our team. We had thought our initial version was good enough even though we knew it was still harder to use when compared to Cattle, but clearly it hasn’t been. However, I can promise you, this is something we do plan making better!
Is this ready for primetime? The answer is yes. We built Rancher on top of k8s and leverage their CustomResourceDefinition (CRD) and controller framework. K8s, is essentially, ready for primetime and it’s been proven, really by our users and the general k8s community, that have already been running workloads using k8s. I won’t go into exact details, but I can tell you some of the tools you use everyday (from the financial to media segment, and many others) are already being powered by both Rancher 2.0 and Kubernetes.
For those of you that used Rancher 1.0 when we went GA in 2016, you know that we are constantly addressing issues found whenever possible. Obviously, the scale of users have changed since we launched over 2 years ago so our response hasn’t been as quick as I’d like. However, I assure you that we are constantly and doing our best to address problems as they are found. This has always been the case, and will continue to be the case going forward. In 2.1, we are providing two things to help our 1.x users. (1) A tool to help migrate Cattle workloads to K8s workloads. (2) A set of guides/docs to help understand what was in 1.0 and how to recreate those in 2.0. We are already working on that now and as soon as they are ready, we’ll release it.
For those that are using this for the first time, I simply ask for patience. We pride ourselves in making sure we create a product that is easy to use. We are not satisfied with what we have built so far although I’m not sure it can ever meet our high expectations. But, I can promise you that we will continue to help you and to quickly address issues as they are found.
Hopefully, this does address some of the concerns you guys may have. As always if you have questions, concerns, or improvements you’d like to see, please let us know. Everything is open source so if you’d like to help us out, please do! While 2.0 may have been created from what we believe it should be, just like 1.6, a big part of our product has always been driven by our users and customers. Let me know what else you’d like answered, and I’d be happy to.