Antoine Legrand
Chief Technical Officer at CONNY
Berlin, Germany
Summary
🤩
Rockstar🎓
Top SchoolAntoine Legrand is a Berlin-based CTO with 12 years of engineering and leadership experience building cloud-native infrastructure and production-ready Kubernetes platforms. He progressed from full-stack and mobile engineering at startups to senior engineering and management roles at CoreOS and Red Hat, then took the helm as CTO of CONNY. Hands-on across backend, DevOps and SRE domains, he has contributed meaningful features to high-profile open-source projects such as prometheus-operator and kubespray, improving CRD management, labeling consistency and cluster automation. Antoine blends people leadership with deep technical ownership—comfortable shipping code, shaping CI/CD pipelines, and hardening distributed systems at scale. He often surfaces operational improvements that reduce friction for operators (for example, CRD customization and kubectl UX enhancements) and thrives at the intersection of developer experience and production reliability.
12 years of coding experience
11 years of employment as a software developer
2011 Computer Science, 2011 Computer Science at EPITA: Ecole d'Ingénieurs en Informatique
French, English, Spanish
Stackoverflow
1reputation
0reached
0answers
0questions
Github Skills (26)
monitoring10
kubernetes10
crdt10
crt10
automation10
go10
prometheus10
kubernetes-pods10
yaml10
ansible10
ansible-galaxy10
automations10
devops10
rbac9
dockers9
Programming languages (17)
Github contributions (5)
kubernetes-sigs/application
Jun 2018 - Mar 2020
Application metadata descriptor CRD
Role in this project:
Back-end & DevOps Engineer
Back-end & DevOps EngineerContributions:1 review, 13 commits, 10 PRs in 1 year 9 months
Contributions summary:Antoine primarily contributed to the core functionalities of the application's definition and management within the Kubernetes ecosystem. They refactored the application metadata descriptor, implemented additional columns for kubectl outputs, and added RBAC rules for accessing resources. Additionally, they made changes to the e2e test scripts and configuration, as well as changing the name of the manager to kube-app-manager. These contributions suggest a focus on both the application's core logic and its operational aspects.
descriptorkubernetesmetadatacrdk8s-sig-apps
kubernetes-sigs/kubespray
Nov 2015 - Nov 2018
Deploy a Production Ready Kubernetes Cluster
Role in this project:DevOps Engineer
DevOps EngineerContributions:4 releases, 67 reviews, 336 commits in 3 years
Contributions summary:Antoine primarily focused on modifying and updating configuration files and service definitions for a Kubernetes cluster. Their contributions involved adjusting network configurations, including those related to the Calico network plugin. They also made changes to service definitions, such as those for the kube-apiserver and kube-proxy, and updated systemd service files, indicating a strong involvement in infrastructure management and automation. Furthermore, they implemented changes to the tests and CI/CD pipelines.
bare-metalkubesprayhelmproduction-readyansible
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.