Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "rancher"
I lost sleep because of Kubernetes...
Rancher you fucking cuck you didn't tell me ahead of time OpenEBS can't RWX YA FOKIN WANKER FUCKING DAFT CUNT PIECE OF SHITE BLOODY BELLEND8
That moment when it takes 4 hours to automate a task which would otherwise take 15min all 2 months to do manually.2
Just needing somewhere to let some steam off
Tl;dr: perfectly fine commandline system is replaced by bad ui system because it has a ui.
For a while now we have had a development k8s cluster for the dev team. Using helm as composing framework everything worked perfectly via the console. Being able to quickly test new code to existing apps, and even deploy new (and even third party apps) on a simar-to-production system was a breeze.
We are now required to commit every helm configuration change to a git repository and merge to master (master is used on dev and prod) before even being able to test the the configuration change, as the package is not created until after the merge is completed.
Rolling out new tags now also requires a VCS change as you have to point to the docker image version within a file.
As we now have this awesome new system, the ops didn't see a reason to give us access to kubectl. So the dev team is stuck with a ui, but this should give the dev team more flexibility and independence, and more people from the team can roll releases.
Back to reality: since the new system we have hogged more time from ops than we have done in a while, everyone needs to learn a new unintuitive tool, and the funny thing, only a few people can actually accept VCS changes as it impacts dev and prod. So the entire reason this was done, so it is reachable to more people, is out the window.3
Updated our rancher setup today and it just completely fucked the server, kubernetes stopped working, rancher stopped working. Guess who's going to install kubernetes manually next week? ;--;2
After a couple of days reading bout CI/CD i find it really compilated for my usecase. Server for jankins server for rancher server for anything and a lot of configurations to make it work. So i gave up and decided to build my own CI tool which turned out to be easiear than all of this. So i wrote a simple cli tool in go which listens on master branch of every directory specified in a .yml file and everytime a new commit is done it pulls the repo and rebuilds the container. Pretty easy without having to deal with all the bullshit15
Yesterday I tried Rancher on a DigitalOcean droplet.
Rancher itself was easy to startup and use. But I couldn't manage to find the Container Volumes on my NFS Server. Even the NFS Server was up and running.
I really felt like a monkey in front of my PC not understanding what Im doing.
I've finally setup a dedicated Docker box with RancherOS and Rancher... Shipyard looked nice as well (the simplicity like beautiful) but the cloud management with Rancher is amazing!
It took me minutes to install the OS, minutes to install Rancher, then on my phone it took minutes to install Jenkins with swarm support!
I'm loving this!
How can it be a galera cluster with three DB servers (running in docker) is slower than a single docker container with mariadb under the same load?6
Anybody got experience with Rancher (https://rancher.com) on Ubuntu?
Checked it out and it looks really well made. You can build a Cluster in Minutes and mount a phyisical storage to it.
Im planning to drop a Full Stack Root Server with it and would be really glad to hear on your opinions 😁3
I spend Way too much time on docker, and this week, rancher !
But totally worth it, it's fun to learn and pretty usefull ^^