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.

Last week I deployed a jenkins container and a buildah container on docker in order to create docker images without requiring access to a Docker daemon.

Jenkins is considered by most people the best automation server around, it can automate almost any task using its plugins: can connect to any ssh capable hosts and run commands, execute ansible playbooks, run maven command, push packages or images to a remote repository, etc.

After completing Mumshad Mannambeth’s Certified Kubernetes Administrator (CKA) with Practice Tests course it was time to deploy my first kubernetes cluster for practice.

After having the graylog stack working it was time to add some security, even elasticsearch was running on an isolated network, some elements were exposed to the local network such as haproxy or rsyslog, that meant some flaw in their code could compromise the whole deployment.