Ryan Fredette
Senior Software Engineer at Red Hat
Raleigh, North Carolina, United States
Summary
🤩
Rockstar🎓
Top SchoolRyan Fredette is a Senior Software Engineer with 13 years of experience building cloud-native networking and infrastructure software, currently at Red Hat after a long tenure at Nuage Networks. He brings deep hands-on expertise in networking, virtualization, and operators—evidenced by contributions to OpenShift's cluster-ingress-operator and API where he improved ingress deployment stability, tuning, and documentation. A pragmatic polyglot (C/C++, Python, Java, Perl) comfortable across Linux environments and CI/CD/DevOps workflows, he pairs systems-level thinking with practical performance and QA experience from early roles at NetApp and Extreme Networks. Ryan’s foundation in embedded systems and robotics (lead programmer on a FIRST team) informs a hardware-aware approach to software design that surfaces in IoT and networking projects. Outside work he’s an avid winter-sports enthusiast and manual-transmission driving enthusiast, a detail that hints at his preference for hands-on control and precision.
13 years of coding experience
4 years of employment as a software developer
Bachelor of Science (BS), Computer Science, Bachelor of Science (BS), Computer Science at North Carolina State UniversityGreen Hope High School
Stackoverflow
1reputation
0reached
0answers
0questions
Github Skills (15)
k8s-operator10
kubernetes10
go10
openshift10
operator-sdk10
api-design10
kubernetes-pods10
operator10
cicd9
yaml9
swagger9
docker8
testing8
dockers8
aws6
Programming languages (5)
Github contributions (5)
openshift/cluster-ingress-operator
Dec 2020 - Sep 2022
The Cluster Ingress Operator manages highly available network ingress for OpenShift
Role in this project:
Back-end Developer & DevOps Engineer
Back-end Developer & DevOps EngineerContributions:141 reviews, 31 commits, 44 PRs in 1 year 9 months
Contributions summary:Ryan primarily focused on modifying and improving the cluster ingress operator's deployment and configuration. Contributions include requesting appropriate memory for the ingress-operator container, fixing issues related to the endpoint publishing strategy, and pruning stale deployment status. The user also updated dependencies and added test cases to improve the operator's stability and functionality. These changes reflect work across both back-end logic and DevOps areas.
ingress-networkingress-controlleropenshiftoperatoringress
openshift/api
Mar 2021 - Jun 2021
Canonical location of the OpenShift API definition.
Role in this project:Back-end Developer
Back-end DeveloperContributions:26 reviews, 10 commits, 7 PRs in 3 months
Contributions summary:Ryan primarily contributed to the OpenShift API definition, focusing on enhancements and adjustments to the IngressController resource. Their work included adding configuration options for threading, implementing tuning options, and refining timeout settings. The changes involved modifications to the API definition files, deepcopy functions, and swagger documentation to reflect the new features. The user also refactored the code by combining structs.
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.