Hacker News Reader

Comment by INTPenis | Hacker News Reader

I was one of those backwards people who opposed containers, until late 2019.

My start was the official kubernetes docs, step by step. Try everything, write it down, make ansible playbooks. Even used some of their interactive training modules, but I quickly had my own cluster up in vagrant so didn't really need the online shell.

Now we have two clusters at work, I have ansible playbooks I'm really happy with that help me manage both our on-prem clusters and my managed LKE with the same playbooks.

I'm completely sold on this container thing. :)

View on HN

>Now we have two clusters at work

Running your two tightly coupled distributed monoliths of your front and back office systems no doubt!

Heh no single project, staging and prod. In fact prod isn't ready, that's when I need to start learning HA control plane.

Do the playbooks rely on kubeadm internally for setup?

Are they OSS by any chance? And what kind of tasks do they do?

Yes but I won't link them.

They are focused only on CentOS 7, you might be able to find them yourself. As far as I can tell they include everything except persistent storage and HA control plane.

Just use Kubespray, not much sense in wasting time writing your own unless your intention is specifically learning how to manage cluster setup with stateless Ansible

I actually looked at kubespray first but first of all it did not work out of box as promised. And to troubleshoot it you basically had to know about kubernetes already.

So it made a lot of sense to start at the official docs. And while I'm reading the docs, why not build the cluster at the same time. And while I'm building the cluster, why not write each step down in Ansible so I won't have to repeat myself.

So end result is my own ansible setup that I'm happy with and I know inside and out.

It always bothered me to run other people's ansible playbooks. I'm too much of a control freak.

Reply on news.ycombinator.com