How I saved 200K/yr in direct costs writing 0 code lines in K8s

A single Kubernetes ingress threatened a critical analytics system. The fix? A zero-code logging pipeline that saved over $200,000.

#1about 5 minutes

Introduction to scientific software in research facilities

Research facilities like DESY use complex, custom-built instruments and software to conduct experiments such as protein crystallography.

#2about 3 minutes

The challenge of migrating a legacy analytics engine

The project's goal was to migrate a custom analytics engine from OpenStack to Kubernetes without a costly rewrite, saving an estimated $200k.

#3about 2 minutes

A no-code log pipeline with HAProxy and Fluent Bit

A solution was implemented using an HAProxy ingress controller to pipe logs to Fluent Bit, which then split them to feed the existing analytics scripts.

#4about 3 minutes

Tools and techniques for Kubernetes development

The project was developed using tools like MicroK8s for sandboxing, echo services for speed, and ksniff with Wireshark for traffic analysis.

#5about 6 minutes

Connecting developer work to motivation and key takeaways

Understanding the financial impact of technical tasks boosts motivation, and the key takeaways are to decompose problems technically and motivate yourself and your peers.