Chris Henzie
Senior Software Engineer - Google Cloud
Sunnyvale, California, United States
Summary
🤩
Rockstar🎓
Top SchoolChris Henzie is a Senior Software Engineer at Google Cloud with 11 years of experience building and hardening cloud-native infrastructure, specializing in Kubernetes node, container runtime, and storage subsystems. He has driven production-focused contributions across Kubernetes and CSI ecosystems—improving CSI spec integrations, multi-architecture builds, and e2e testing for high-profile projects like kubernetes/kubernetes and several kubernetes-csi drivers. His background spans roles at Google, Meta, Twitch and Sunrun, blending backend engineering with DevOps and QA automation to improve reliability and release tooling. Known for pragmatic fixes—such as stabilizing volume snapshot tests and mapping PV access modes to CSI capabilities—he focuses on bridging spec changes to real-world deployments. Based in Sunnyvale, he brings a Berkeley EECS foundation and a track record of shipping robust storage and runtime improvements that quietly lower operational risk at cloud scale. An underappreciated strength is his simultaneous fluency in controller logic and build/release systems, which helps shipsystem-level changes land smoothly.
11 years of coding experience
12 years of employment as a software developer
Bachelor of Science (BS) Electrical Engineering Computer Science, Bachelor of Science (BS) Electrical Engineering Computer Science at University of California, Berkeley
Github Skills (33)
e2e-testing10
kubernetes10
docker10
volumes10
apidoc10
testing10
e2e-test10
storage10
test-framework10
build-system10
dockers10
cicd10
gcp10
automation10
go10
Programming languages (14)
Github contributions (5)
kubernetes-csi/csi-driver-host-path
Jun 2021 - Nov 2022
A sample (non-production) CSI Driver that creates a local directory as a volume on a single node
Role in this project:
DevOps Engineer
DevOps EngineerContributions:7 reviews, 10 commits, 5 PRs in 1 year 5 months
Contributions summary:Chris primarily focused on enhancing the build and release process within the repository. This included updating build platforms, improving build timeouts, and configuring multi-architecture builds using Docker buildx. Furthermore, they updated dependencies, integrated CSI spec v1.5.0 and addressed access mode constraints for single node deployments.
single-nodek8s-sig-storagevolumecsi-drivernon-production
kubernetes-csi/external-provisioner
Mar 2021 - Jan 2022
Sidecar container that watches Kubernetes PersistentVolumeClaim objects and triggers CreateVolume/DeleteVolume against a CSI endpoint
Role in this project:Back-end Developer
Back-end DeveloperContributions:4 releases, 17 reviews, 17 commits in 10 months
Contributions summary:Chris primarily focused on enhancing the `external-provisioner` for Kubernetes CSI. Their contributions included removing redundant logging statements, aligning the project with CSI specification v1.5.0, and updating Kubernetes dependencies. They also implemented logic to map persistent volume access modes to CSI access modes based on driver capabilities. These changes are crucial for ensuring the provisioner's compatibility and proper function within a Kubernetes environment.
sidecark8s-sig-storagesidecar-containerpersistentvolumeclaimwatches
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.