A few of the top of my head...
- UI for managing all the major resources (that isn't read-only or "insert large properly-formatted yaml file here")
- Access control integration to other systems like AD
- Grouping multiple namespaces into "Projects" and doing RBAC and Secret definition/assignment at that level instead of duplicating yourself for every namespace
- You only have GKE clusters today but if tomorrow you want something on Amazon or your company acquires a team with existing stuff in Azure you can still have one place to manage it
Somewhat reminiscent of the early 2000's fad to abstract over databases when in reality folks never 'swap out the db' on real projects.
Having a simple way to run your own block storage that could withstand node failures / network issues would be fantastic.
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.
It's been mostly painfree, occasionally there are bugs in Rancher but nothing has been a show stopper.
- PersistantVolumeClaims: I tried to launch a Postgresql workload and didn't get a warning that I should configure EBS before
- I tried installing rancher on my machine and later found out that the nodes need to reach rancher
- 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
It's good to see they have got their focus right with version 2.
Getting the command to import a cluster is ~5 calls from a brand new server container.. Login with admin/admin, set a better password, set the server-url, create a cluster and get the registration token/command for it.
We are still in closed beta but if you are interested, please sign up and we will activate your account asap.
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.
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.
