Brad Ison

Platform Engineer

Berlin, Germany
email-iconphone-icongithub-logolinkedin-logotwitter-logostackoverflow-logofacebook-logo
Join Prog.AI to see contacts
email-iconphone-icongithub-logolinkedin-logotwitter-logostackoverflow-logofacebook-logo
Join Prog.AI to see contacts

Summary

🤩
Rockstar
Brad Ison is a Site Reliability Engineer with 14 years of experience building and hardening cloud-native infrastructure across OpenShift, Istio, and OpenStack ecosystems. Based in Berlin and currently at Authzed, he blends SRE rigor with hands-on DevOps and backend development—contributions include namespace-aware deployments and TLS handling in the OpenShift machine-api-operator and test/framework improvements in Istio. His background at Red Hat, CoreOS and Rackspace reflects deep expertise in operator-driven automation, monitoring resilience, and scaling APIs. An active open-source contributor, Brad has shipped pragmatic fixes and features that improve observability and multi-tenant deployments in widely used projects. He favors practical, infrastructure-first solutions and often tackles edge cases—like region/zone reconciliation and ignition user-data handling—that keep large clusters reliable in production.
code15 years of coding experience
job13 years of employment as a software developer
github-logo-circle

Github Skills (32)

autoscaling10
service-mesh10
kubernetes10
docker10
apidoc10
testing10
test-framework10
dockers10
cicd10
go10
openshift10
api10
prometheus10
kubernetes-pods10
yaml10

Programming languages (17)

MDXJavaC++RustMakefileGoHTMLGroovy

Github contributions (5)

github-logo-circle
Machine API operator
Role in this project:
userDevOps Engineer & Backend Developer
Contributions:17 commits, 21 PRs, 143 comments in 1 year 6 months
Contributions summary:Brad's contributions center around enhancing the machine-api-operator for the OpenShift platform. They implemented features allowing deployment into specific namespaces, requiring adjustments to TLS assets and the operator's configuration. Furthermore, the user made changes to reconcile region and zone labels on Machine objects, and modified the codebase to utilize the cluster's operator status conditions and correctly reflect the desired state. The commits also include changes related to vsphere cloud provider integration, including support for passing ignition user-data.
operator
Manage the OpenShift monitoring stack
Role in this project:
userDevOps Engineer
Contributions:24 reviews, 44 commits, 20 PRs in 11 months
Contributions summary:Brad primarily focused on maintaining and improving the OpenShift cluster monitoring operator. Their contributions included removing obsolete service monitors, fixing typos, and refactoring code related to Grafana and user-workload monitoring. The user also implemented a retry mechanism for API errors, ensuring greater resilience in the monitoring system. Furthermore, they added support for disabling Grafana deployment and enabled the use of federated targets in the Thanos querier.
monitoringopenshift
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.
Request Free Trial