On my previous post I created a project on BitBucket and defined a basic pipeline to run some tests on the code.

As I said on my previous post, I changed jobs and I’m learning a lot of new things.

This weekend I tried Rancher Kubernetes Engine thanks to my colleague Juan who managed to create a couple of playbooks to deploy a Cluster Manager and a Managed Cluster from scratch.

I’m a bit worried about the CentOS’ lifecycle policy change, which will do CentOS 7 last after CentOS 8 reaches its EOL, and it is said than a father shouldn’t bury his son.

I decided to perform additional experiments with VMWare Tanzu, but unfortunately, tanzu clusters on docker didn’t survive reboots, so I had to create another cluster, this time a standalone cluster.

I’ve been wanting to know more about VMWare’s Tanzu kubernetes distribution for a while, and when I got the release announcement of Tanzu Community Edition, I wanted to test it.

My first setup of a kubernetes cluster lacked HA features because I didn’t completely understood the procedure and ran directly into the abyss.

I created my first AWS account on 2012 for training purposes but I closed it several years ago because I wasn’t using it at all.

I was arguing this week about the convenience of giving some users permission to launch containers, putting them on the “docker” group.

Infrastructure-as-Code or IaC is one of the game-shifting techniques in use today.