Today I got the email from Google saying that I passed the Google Cloud Associate Engineer certification. Last Friday I took the exam at a Kryterion test center and got the pass score but had to wait till the final approval from Google. At my current job I don’t work with Google Cloud but more with Microsoft Azure, AWS and data center environments. Google certification was on my list of certifications I wanted to look into.
A month or so ago I started with building a homelab for running Kubernetes. I choose Raspberry Pi’s to run my workloads on. I started with the use of kubeadm to deploy Kubernetes and chose the blog of Alex Ellis as my starting point. I ran into some problems in my attempts to get it working but finally I succeeded to get it working. Soon after that Rancher Labs, released K3S which was targeted at edge and iot solutions and perfect for running on Raspberry Pi’s.
As I already explained in my earlier post, this was my first KubeCon | CloudNativeCon that I attended. What I liked about KubeCon was the diversity in sessions and that it was often a difficult choice per time slot which session to attend. For me this congress was next to attending sessions also about networking with vendors and other attendees. There were a lot of good opportunities and I spoke to a lot of people.
This year I’m going to KubeCon | CloudNativeCon which is held in Barcelona from Monday, May 20, 2019 - Thursday, May 23. This is my first KubeCon and I’m really looking forward to the sessions and the meetings I have scheduled Here is list of tips which kind of apply to every conference I have attended. Wear comfortable shoes Take a powerbank/ adapters with you Build your agenda using the agenda builder Leave time between session.
In my post about first experience with k3s I blogged about setting up my k3s based cluster on Raspberry PI’s. Since that post I have added two more nodes Raspberry Pi’s and also updated to the 0.3.0 version of k3s. 1 2 3 4 5 6 7 pi@k3s-master-1:~ $ kubectl get nodes NAME STATUS ROLES AGE VERSION k3s-master-1 Ready master 4h11m v1.13.5-k3s.1 k3s-node-1 Ready node 129m v1.13.5-k3s.1 k3s-node-2 Ready node 118m v1.
Rancher has released v0.2.0.of k3s. Information of the new release is in this article. As soon as I have some time and I have added two extra nodes to the cluster, I’m going to add the cluster to my Rancher server. I have upgraded my Raspberry Pi’s to v0.2.0. The process of upgrading is really simple. Just download the new version and replace the old version of k3s with the new version and restart.