DevOps Q&A

Why It Matters

The discussion highlights operational trade-offs teams face when implementing zero-downtime secret rotation and secure, daemonless image builds, affecting reliability and compliance choices; it also underscores the importance of Cluster API tooling and tracking Kubernetes API changes for maintainable, self-managed clusters.

Summary

In a casual DevOps Q&A, participants discussed practical approaches to secret rotation, recommending tools like Reloader and noting that seamless updates depend on application behavior (file mounts update easily, environment variables often require restarts). For container image builds without a Docker daemon they weighed options including Kaniko (and its forks like ChainGuard), Buildpacks, and Podman, advising Kubernetes-native builders when running in-cluster. They also touched on Cluster API for self-managed Kubernetes on bare metal—mentioning Metal3 and Canonical MAAS as provider options—and the ongoing need to monitor Kubernetes API deprecations. The session mixed technical guidance with lighthearted Argo CD vs. Flux banter throughout.

Original Description

Viktor, Kostis, and Scott answer your questions about DevOps, Kubernetes, Cloud, AI, SREs, and anything else.