Top expert inKubernetes and Cloud-Native TechnologiesCloud-Native DevOps with Kubernetes
David Eads is a Distinguished Engineer with 11+ years focused on backend and DevOps for cloud-native platforms, currently leading architecture and reliability work at Red Hat from Raleigh, NC. He combines deep Kubernetes and OpenShift expertise—contributing to core projects like kubernetes/kubectl, client-go, and OpenShift operators—with practical operator and installer improvements for real-world cluster stability. His work spans API design, code generation, certificate and security handling, and tooling for artifact and data gathering, reflecting both systems-level rigor and operational pragmatism. Notably, he has driven modularization and dependency cleanup in Kubernetes repos and added security-aware introspection features to the must-gather tooling. Colleagues rely on him to bridge complex API server internals with deployable operator patterns and to shepherd upgrades across large, distributed codebases. He holds multiple engineering degrees from NC State and blends long-term enterprise experience at IBM with a decade of open-source stewardship.
11 years of coding experience
20 years of employment as a software developer
Bachelor’s Degree Computer Science, Bachelor’s Degree Computer Science at North Carolina State University
Helpers for going from apis and clients to useful runtime constructs
Role in this project:
Back-end & DevOps Engineer
Contributions:397 reviews, 396 commits, 380 PRs in 4 years 8 months
Contributions summary:David primarily contributed to the OpenShift library-go repository with a focus on enhancing the project's cryptographic capabilities. They added crypto helpers, created a controller package, and implemented functions to read YAML. Furthermore, the user introduced features for handling TLS and HTTP serving configurations, including the ability to manage and process certificate and key information, showcasing a strong understanding of networking and security principles within the project. Additionally, the user was responsible for performing multiple upgrades and maintaining the vendor dependencies.
Canonical location of the OpenShift API definition.
Role in this project:
Backend Developer
Contributions:1 release, 927 reviews, 325 commits in 7 years 6 months
Contributions summary:David primarily contributed to defining and updating the OpenShift API definition. Their work included refactoring code related to deployment configurations, adding scope restrictions to OAuth clients, adding clusterquota projection for associated projects, and implementing a "what-can-i-do" endpoint. The user also made significant changes related to PodSecurityPolicy review APIs and image stream tags.
apiopenshiftlocationkubernetesdefinition
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.