Finally last weekend I did the CKA exam, I was procrastinating it a bit in part because I didn’t know what to expect since Kubernetes is huge and I thought that each day extra I spend reading about it would help me. TLDR; I did pass the exam and if you work daily with Kubernetes or variants as Openshift you will be ok, they are not trying to catch you in some weird question that not even Kelsey would know how to answer 😀

This was originally posted on deis.com. Kelsey Hightower gave a really interesting talk at ContainerSched about how to create your own scheduler using the Kubernetes HTTP API. The talk was awesome. It’s incredible to see what kind of things you can do with a base system as good as Kubernetes. However, I missed one thing. The example provided by Kelsey was a Go application. Which is the main language used with Kubernetes.

As you may know, yesterday, GitHub has presented a way to verify your commits on their platform. This is not something new, it’s part of the git protocol, but now, they will show a fancy “verified” label everytime you push a signed commit. Cool? Yeah, pretty cool. One of the problems I always had since I know GPG is to keep my keys locally. I am pretty sure that some other people take care of their keys as if they were part of their family, but I didn’t feel that need yet.

This was originally posted on k8s.uk. If you don’t know about Kong yet, you should take a look. It’s an Open Source API Gateway, they define themselves as: “The open-source management layer for APIs, delivering high performance and reliability.” and they are quite right. I was playing with Kong lately at work (jobandtalent.com, we are hiring!) and I think that it could be pretty awesome as a entry layer to your microservices platform running in Kubernetes.

packetbeat is one of the best application performance management tools in the opensource community. It’s now part of the beats that Elastic provide us to monitor our applications. What it does is analyze our data packets to send some useful information to ElasticSearch. After the introduction you probably realize that we will need: ElasticSearch installed and if you want to see something useful you will need Kibana as well. There is a guide for getting started that explains the process pretty clearly.

For a pet project I needed Pligg which is kinda a social network site in the style of the old-digg (with karma and this kind of things). Installing a LAMP system is kinda boring stuff, so, for that and for the sake of learning I decided to go with Docker & Fig. Sadly or luckily, every time that I dockerize something I find a lot of unexpected problems that slow me down, but… you always learn something!

I had a system that was creating a different log for each worker. Those logs where in the form: /var/log/baselog, /var/log/baselog.1, /var/log/baselog.2 and so on. I wanted to tail them but they were being updated simultaneously so the output of the tail was being a mess. I am a tmux user since few months ago (if you aren’t, you should!) so I’ve decide to open all of them in different tmux panes.