Jeremy Facchetti
Paris, Ile-de-France
Summary
🤩
RockstarJeremy Facchetti is a pragmatic back-end and DevOps engineer based in Paris with nine years of hands-on experience building and hardening Kubernetes-related platforms and tooling. He contributes to notable open-source projects such as Azure Red Hat OpenShift RP and loft-sh/vcluster, focusing on maintainability, refactoring, testing, and operational improvements like k3s/k0s integrations and distroless file-copy utilities. Jeremy excels at simplifying complex operational flows—streamlining token handling, moving deployments into syncer containers, and improving network policy and service CIDR handling—to make cloud-native systems more reliable and easier to operate. Known for clean, idiomatic changes (e.g., waitgroups and error-code clarifications), he blends pragmatic engineering with attention to long-term maintainability. Colleagues describe him with a wry sense of adventure—“international bandit”—that hints at curiosity and a preference for exploring unconventional solutions.
9 years of coding experience
German, English, French
Github Skills (14)
kubernetes10
go10
devops10
back-end-development10
kubernetes-pods10
vcluster10
networking9
testing9
apidoc9
api9
cicd8
cloud-native7
dockers7
docker7
Programming languages (5)
Github contributions (5)
Azure/ARO-RP
Mar 2022 - Jan 2023
Azure Red Hat OpenShift RP
Role in this project:
Back-end Developer
Back-end DeveloperContributions:674 reviews, 96 commits, 153 PRs in 10 months
Contributions summary:Jeremy primarily contributed to the back-end aspects of the Azure Red Hat OpenShift RP project. Their commits focused on improving code quality and maintainability, as evidenced by changes to error codes, the use of idiomatic waitgroups, and the removal of unnecessary function definitions. They also implemented refactoring and testing of proxy-related functionalities.
red-hatopenshifthatkubernetesazure
loft-sh/vcluster
Nov 2023 - Sep 2024
vCluster - Create fully functional virtual Kubernetes clusters - Each vcluster runs inside a namespace of the underlying k8s cluster. It's cheaper than creating separate full-blown clusters and it offers better multi-tenancy and isolation than regular namespaces.
Role in this project:Back-end & DevOps Engineer
Back-end & DevOps EngineerContributions:139 reviews, 120 PRs, 34 pushes in 10 months
Contributions summary:Jeremy primarily contributed to simplifying and improving the codebase's operational aspects. They streamlined the token flow in the k3s integration. They also refactored the k0s deployment process, moving its execution to the syncer container. Moreover, the user implemented a file copy utility, a critical feature for distroless container environments. They made several improvements related to network policy and service CIDR.
clustershelmvclusterk8scheaper
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.