- AI/ML will be creeping into absolutely everything in some way, shape or form

- Developers of every shape, size, background and skillset will continue to be the most in-demand talent on the planet, likely leading to a huge bubble that's gonna fuck us eventually.

- JS will continue to dominate everything, NPM will probably encounter some form of MAJOR major outage that halts most of the globe's development + deployment processes, sparking the creation of another registry which will lead to the holy wars of the registries

- Web devs will continue to be stuck supporting IE8.

- Java will probably die out, maintenance halting completely unless you pay Oracle extortionate amounts of money, like single handedly paying every Oracle employee's salary extortionate.

- There'll probably be another big hype on the scale of Docker/k8s that you have to learn because you'll be unemployable without it

- The year is 2078 and WordPress still supports PHP 5.2, that fucking cockroach will outlive us all I swear

- Haters gonna hate

- React gonna react

- Angular gonna... Math?

Learn AWS, they said. It'll be fun, they said.

I want to get off this Mr. fucking DevOps ride. Ansible, Vault, Terraform, Chef, K8S, Circle CI can all go fuck themselves.

My Thursday evening (thanks for the beer!) nerding up on container management

School gave me 3 DigitalOcean droplets to try out Kubernetes in the cloud, awesome!

Wrote an Ansible script to not only simply install docker and add users but also add kubernetes, nice!

Oh wait, error?! Well I should've known this wasn't going to be easy... ah well no problem. Let's see... Ansible is cryptic as always, it can't connect to the API server? Is it even running?

Let's ssh to the master, ah nothing is running, great. Let's try out kubeadm init and see what happens, oh gosh, my Docker version has not been validated! No problem, let's just downgrade!

How do I do that? Oh I know, change the version in the role! Wait that version doesn't exit? Let's travel to Docker's website and see what versions exist of docker-ce, oh I see, it needs a subversion, no problem.

Oh that errors too? Wait then what... Oh I need a ~ and a ubuntu and a 0 somewhere, my mistake!

Let's run it again! Fails!

Same ssh process, oh wait...

Oh god no...

Kubernetes requires 2 cores and these things only have 1...

Welp, time to ask the teachers to resize my droplet by a small amount tomorrow, hopefully I'll get a new error!

----------------------------------------------

My adventure so far with Kubernetes. I'm not installing it for any serious/prod reason, just for educational purposes. K8s seems like 'endgame' to me, like one of the 'big guys' that big enterprises use so I'm eager to throw stuff at a droplet and see what happens.

Going further down the rabbit hole tomorrow!

Wish me luck :3

(And yes, I could've figured this all out beforehand with documentation, but this is more fun in my opinion)

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.

Introducing Rancher

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.

credits to @arungupta kubernetes mom

Just finished my Kubernetes book... This little piece of tech is amazing!!

Everyone rides on k8s today....

But in the end it's just like Docker Swarm and Compose combined.

I don't know if Google is playing Elon Musk anymore.

Just got accepted to DigitalOcean's Kubernetes Limited Availability! Can't wait to test it out 😊

"shiny shiny" time... Lets standup a kubernetes cluster and then find a problem to solve! #BuzzWordDrivenDev

You must've heard of recent unfamous CVE-2019-5736 vulnerability. This morning one of my hosting providers forcefully updated k8s version because of that. They also provide terraform module for k8s, which has "version" field required.

So during regular CI/CD process, TF decided it wants to recreate all existing clusters on that provider, basically wiping out everything there is.

No dataloss or operations disruption was registered, but a day was ruined. Guess nobody to blame except me.

"This service runs outside of k8s so it can only be accessed from other services in prod"

Yay... Don't you love it when things can't be run outside of prod...

I guess these days I work with Golang, gRPC, and Kubernetes. I guess that's a dev stack. Or turning into one at the very least. The only thing that annoys me about this stack, is how different deployments for kubernetes are different for CSPs. The fact that setting up a kubernetes/Golang dev environment is take a lot of time and effort. And gRPC can be a pain in the ass to work with as well. Since it's fairly new in large scale enterprise use, finding best practices can be pretty hard, and everything is "feet in the fire" and "trial by error" when dealing with gRPC.

And Golang channels can get very hairy and complicated really really fast. As well as the context package in Golang. And Golang drama with package managers. I wish they would just settle on GoDeps or vgo and call it a day.

And for the love of God, ADD FUCKING GENERICS! Go code can be needlessly long and wordy. The alternative "struct function members" can be pretty clunky at times.

Learning to like manjaro, a lot, setting up i3 for a workstation and kubernetes cluster with a couple of manjaro workstations with just the cli installed... few gotchas on the way, get Hyper-V enhanced mode working but get a message session error on dbus launch - easy fix it is already launched by lightdm, the cli install doesn't start the network driver by default but can get a whole 3 node k8s cluster running in under an hour from scratch and forward i3 to a nice, fast, little windows x-server that I got for free with Microsoft reward points.. winning!