Christian Schlotter
Senior Software Engineer at NVIDIA
Ellwangen, Baden-Württemberg, Germany
Summary
🤩
Rockstar🎓
Top SchoolChristian Schlotter is a Senior Software Engineer with 13 years designing, operating, and hardening large-scale Kubernetes platforms, from running Daimler’s fleet of 750+ clusters since k8s v1.6 to contributing core features in Cluster API and kube-state-metrics. He blends backend, cloud and DevOps expertise—particularly around Cluster API providers for vSphere and OpenStack—having driven maintainership, CI/E2E test coverage and Kubernetes compatibility work at VMware, Broadcom and Red Hat. Known for pragmatic refactors and reliability engineering, he’s implemented upgrade workflows, security improvements and metric enhancements that reduced operational churn and prevented regressions. Based in Ellwangen, Germany, he brings hands-on experience with kubeadm, container runtimes, and building CI for large cloud-native projects, plus a background in IT security from his computer science degree.
14 years of coding experience
10 years of employment as a software developer
Bachelor of Science (B.Sc.) Computer Science - IT-Security, Bachelor of Science (B.Sc.) Computer Science - IT-Security at Aalen University
Github Skills (24)
monitoring10
kubernetes10
observability10
back-end-development10
lifecycle10
testing10
cloud-infrastructure10
cicd10
go10
prometheus10
openstack10
kubernetes-pods10
cluster-api10
cloud-services10
devops10
Programming languages (13)
Github contributions (5)
kubernetes-sigs/cluster-api
May 2021 - Jan 2023
Home for Cluster API, a subproject of sig-cluster-lifecycle
Role in this project:
Back-end & DevOps Engineer
Back-end & DevOps EngineerContributions:1692 reviews, 69 commits, 331 PRs in 1 year 8 months
Contributions summary:Christian contributed to the `kubernetes-sigs/cluster-api` repository, primarily focusing on infrastructure and deployment related changes. Their work included preventing duplicated files in cloudinit, improving testing by migrating tests to envtest, and implementing features for cluster upgrades. The user also implemented functionality for the runtime SDK including the ability to handle ca injection to ensure https requests are valid and created an annotation hook for managing the lifecycle of running clusters.
cluster-apisubprojectk8s-sig-cluster-lifecycle
kubernetes-sigs/cluster-api-provider-openstack
Mar 2021 - May 2022
Cluster API implementation for OpenStack
Role in this project:Back-end & Cloud Engineer
Back-end & Cloud EngineerContributions:84 reviews, 19 commits, 10 PRs in 1 year 2 months
Contributions summary:Christian primarily focused on enhancing the OpenStack provider for the Cluster API implementation. Their contributions involved refactoring security group reconciliation logic, improving logging, and optimizing the load balancer service. Furthermore, they addressed Kubernetes compatibility issues, implemented changes to reset cluster status, and modified the code to prevent recreating status.network. These changes collectively improved the functionality and stability of the OpenStack integration within the Kubernetes ecosystem.
cluster-apiopenstackk8s-sig-cluster-lifecycle
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.