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.
Rancher introduced alsmost week ago k3s, a lightweight Kubernetes Distribution. In the YouTube video below you hear Shannon Williams and Darren Shepherd from Rancher talk about K3S, what it is, the usecases and demo of K3S. https://youtu.be/5-5t672vFi4 k3sis a fully compliant, production-grade Kubernetes distribution that maintains an absolutely tiny footprint. Weighing in at less than 40 MB, it only needs 512 MB of RAM to run. This means it’s perfect for all kinds of computing that requires a minimal about of memory and space.
This month the following two flings were updated: vSphere PKS Plugin PowerCLI for VMware Cloud on AWS Here are the detailed logs of the updated flings: vSphere PKS Plugin: Version 1.0.2 - Build 224045 Adds support for PKS v1.3 Minor bug fixes PowerCLI for VMware Cloud on AWS Version 18.104.22.16822238 Added Remove-* cmdlets Added/updated Get-* cmdlets based on latest VMC API definition