The KubeCon around the Kubernetes technology was one of the events I dreamed to attend since I’m focusing on the CloudNative solutions. I had the great opportunity to attend the KubeCon & CloundNativeCon in Amsterdam with my colleague Benoît Entzmann.
There is now CNCF-hosted Co-located events adding more topics and interesting sessions. This is community-driven, vendor-neutral events hosted and managed by the CNCF. ArgoCD, Cilium, Linkerd have now their own conference. Here is the list of CNCF-hosted Co-located events.
Unfortunately, all the above events were already sold out when we decided to come at the KubeCon.
During the 1st day Keynote, Chris Aniszczyk CTO of the CNCF mentioned that for this year, the increase of the number of participants was just amazing reaching more than 10’000 people. The number of CNCF projects also increased a lot. I feel that the main message of this Keynote is that there is a real need for contributors to help maintainers – more projects but seems less contributors.
The keynote was interesting, I learned that there are new certifications available in the CNFC cert path.
I noticed a project that I would like to follow: The scalable, reliable, MySQL-compatible, cloud-native database. I’m quite sure my database colleagues Elisa Usai & Saïd Mendi would love to do a presentation during our next dbi xChange event. I would encourage them to have a look at vitess.io.
After the keynotes I participated to the following sessions
- Learn the Helm Code Base and PR Review Process
- Emissary-Ingress: Self-Service APIs and the Kubernetes Gateway API
- Argo CD Core – A Pure GitOps Agent for Kubernetes
- How to Turn Release Management from Duty to Fun: Lessons Learned Building the Cluster API Release Team
- Highly Available Routing with Multi Cluster Gateways
Following some information about the sessions.
Learn the Helm Code Base and PR Review Process.
Scott Rigby, Andrew Block & Karena Angell were holding the session and explained rapidly what helm is. They focus the session on drawing attention to the need for contributors. Anybody could help not only by developing but also in doing review, documentation, bugs triage and other stuff that may not require high level of expertise. We explored the git repository with the composed directory explaining each of them. How the source code of the helm tool is composed. It was interesting but to be honest, I was thinking that we would have to describe which new features are in the pipe or other cool stuff around the futur of helm. It seems that maintainer are already overloaded and except maintaining the code there is no real new features or at least it was not covered during this session.
Emissary-Ingress: Self-Service APIs and the Kubernetes Gateway API
Lance Austin and Flynn Buoyant provides update on the emissary-ingress, including new features since the time it was introduced in Detroit. They also explained the needs of having a self-service, developer centric configuration tools for APIs.
Argo CD Core – A Pure GitOps Agent for Kubernetes
The speakers, specially the co-creator of Argo provides description of the Argo CD component architecture, showing the internal layer saying that the core is decoupled from the UI. The core can be easily used by Kubernetes Administrator to deploy several applications along to multi-cluster. A demonstration was done to show how Kube Admin could use Argo CD as a pure GitOps Agent.
I think you now have an overview of the session I’ve followed today, it’s a complete program during the KubeCon & CloudNativeCon. I had to choose between several streams as there were interesting other sessions in parallel. I’m really happy to be part of this event but now it’s time to take a bier with my colleague Benoît and see what will do tonight – visiting Amsterdam most probably.