Hi folks!

Welcome back to our second meetup of 2021, we have the usual fantastic speakers, plus networking on Rambly with your fellow techies!

6:45 Kick off
7:15 Eventually Consistent Testing for Kubernetes Controllers (Joel Speed, Red Hat)
7:45 Why you should take care of infrastructure drift (Stephane Jourdan, driftctl)
8:15 Break
8:30 Replicated block storage with LINSTOR (Robert Altnoeder, LINBIT HA-Solutions GmbH)
9:00 Wrap up

See you there!

Cheryl (@oicheryl)

Eventually Consistent Testing for Kubernetes Controllers (Joel Speed, Red Hat)
Building Kubernetes controllers has become much easier over the past couple of years with the introduction of the Kubebuilder, Operator SDK, Controller-Runtime and Controller-Tools projects. However, due to the nature of controllers, testing them is very difficult! For example,
the Kubernetes API is complex with many edge cases, so how can you reliably mock it for testing? The answer is don’t! Instead, use envtest, a system provided by controller-runtime that allows you to write test suites that use a real Kubernetes API server and avoid mocks and fakes. In this talk, you will learn about envtest, how it works and how to test controllers using it. You will also learn patterns, limitations and gotchas for testing controllers and how to use Ginkgo and Gomega to write eventually consistent test suites to reliably test your controller’s behaviour.

Joel is a Software Engineer working on the OpenShift Machine API and Kubernetes Cluster API projects. Joel has been working with Kubernetes since 2017, previously at Pusher as a Cloud Infrastructure Engineer, now at Red Hat. As well as his interest and involvement in the Kubernetes community, Joel is also known for his involvement in the single Single Sign-On space, being a maintainer on Dex and OAuth2 Proxy. Find Joel on twitter @JoelASpeed.

Why you should take care of infrastructure drift (Stephane Jourdan, driftctl)
As infrastructure as code (IaC) becomes widely adopted by users with heterogenous skillsets, and as IaC codebases become larger and larger, it becomes harder to track drift. Drift is a deviation between the actual infrastructure state and the IaC codebase. It causes issues for security posture management, collaborative work, and maintenance. It’s hard to improve what you can’t measure! Can we define good metrics for drift? Developers track unit tests coverage to track how well unit tests match application code over time. Can we use an analogy and define infrastructure code coverage to track how well IaC matches the actual infrastructure state? In this talk, we will show how minor infrastructure drift can cause issues. We will then introduce various ways to track IaC coverage, and how we can use them to bring visibility into the state of infrastructure and anticipate common drift issues. We will end the talk by showing our own free and open source tool driftctl, (just released under Apache-2.0 licence) that tracks IaC coverage and warns of infrastructure drift.

CTO and entrepreneur, I’ve built, maintained and automated infrastructures for 20 years. Currently founder at CloudSkiff where we aim to protect codified cloud infrastructures, starting by building driftctl (Open Source CLI that measures Infrastucture-as-Code coverage, and tracks infrastructure drift). Author of “Infrastructure-as-Code Cookbook”, working remotely for the last 10+ years in Canada and Europe. Also co-launched and run a community radio. I'll be speaking at FOSDEM this year. I'm on Twitter: @sjourdan

Replicated block storage with LINSTOR (Robert Altnoeder, LINBIT HA-Solutions GmbH)
An overview of LINSTOR, a free open source software defined storage system that provides replicated block storage for various consumers, such as virtualization and containerization platforms

Principal Architect at LINBIT, I've worked for LINBIT since 2013 and formerly worked for SolveDirect and as a contractor for IBM.