Skills
☁️ Cloud Native & Kubernetes
My primary focus lies in the Cloud Native ecosystem, specifically Kubernetes. I have 8+ years of hands-on experience in designing, building, and maintaining production-grade platforms.
- Orchestration: Kubernetes (Production clusters, GKE, Vanilla), Helm, Kustomize
- Observability: Prometheus, Grafana
- GitOps: Flux
- Networking: CNI plugins, Ingress Controllers (Nginx)
- Storage: CSI drivers, Persistent Volumes
💻 Software Development
I am a polyglot programmer with a strong preference for Go when building cloud-native tools and controllers.
- Go (Golang): Building Kubernetes Operators, Microservices, CLIs, and backend services (e.g., OpenFero)
- Python: Scripting, automation, and data processing
- Web Technologies: Vue.js, JavaScript, HTML5, CSS3 (for dashboards and UIs)
- Shell: Bash/Zsh scripting for system administration and automation
🛠️ DevOps & Platform Engineering
I believe in “Everything as Code” and self-service platforms.
- CI/CD: GitHub Actions, Jenkins
- Infrastructure as Code: Terraform, Ansible
- Containerization: Docker, containerd
- Operating Systems: Linux (Ubuntu, Debian), RaspberryPi
- Cloud Platforms: Google Cloud, OpenStack
💡 Core Competencies
- Architecture: Kubernetes Architecture, Hybrid-Cloud Strategy, Microservices
- Platform: Internal Developer Platforms (IDPs), Self-Service Portals
- Processes: GitOps Workflows, Cloud Migration, Cost Optimization
- Development: API Development, Full-Stack Web Apps
OPENFERO EVOLUTION: BUILDING THE FOUNDATION FOR COMMUNITY-DRIVEN SELF-HEALING FRAMEWORK
Photo by Helena Lopes on Unsplash Hi guys, in late 2022, I shared the story of my hobby project “OpenFero: The journey to a self-healing platform”. What started as a personal project to extend Kubernetes’ self-healing capabilities has evolved significantly over the past two and a half years. Today, I’m excited to provide an update on OpenFero’s journey and highlight some of the exciting new features and developments.
Read moreWHY KUBERNETES NEEDS SO MANY IPS
Photo by Shubham Dhage on UnsplashForeword Foreword Why can the networks of a GKE/Kubernetes cluster become so “big”? This article answers this very question. As the name suggests, the Google Kubernetes Engine is based on the open source project Kubernetes. Kubernetes requires 4–5 networks in each installation variant as a basis for further calculations, which Kubernetes or, more precisely, the container network interface provider (CNI) can/may use.
Read moreWHEN A SELF-SERVICE PORTAL IS NOT ENOUGH
Photo by Emanuel Ekström on Unsplash temporary namespace manager (tenama) Today’s article is about another service that I was able to develop and open-source during my work as a platform engineer. With the following anecdote, I would also like to lay the foundation for my current “story” of why we developed tenama. What happenend so far In the environment I work in, we build our on-premise Kubernetes clusters very heavily based on open source products. In recent years, it has been important to us to source our components as directly as possible from the open source community and thus have the opportunity to give direct feedback to the community and also to be able to deliver the occasional bug fix.
Read moreRESOURCE MANAGEMENT IN KUBERNETES
Photo by Growtika on Unsplash Foreword In the following chapter we will discuss the topics CPU requests, CPU limits, memory requests and memory limits. We will try to go into details here only so far as to build an understanding of the foundation of Kubernetes Resources Management. For those who are interested in the topic and want to learn more, I recommend the official documentation https://kubernetes.io/docs/tasks/configure-pod-container/assign-cpu-resource/.
Read moreTHE JOURNEY TO A SELF-HEALING PLATFORM
Photo by Austin Kehmeier on Unsplash Hi guys, my first story is about my hobby project “OpenFero”. Open Fero is a little play on words from the Latin “opem fero”, which means “to help” and the term “OpenSource”. Hence the name “openfero”. The scope of OpenFero is a framework for self-healing in a cloud-native environment. Beginning of the journey In my ongoing time as a Kubernetes Platform Engineer, I’ve always wondered, “Isn’t there a solution to take the self-healing principle of Kubernetes further?” Kubernetes itself already offers some self-healing features but often only for the application and services running on top of it.
Read more