Contributor Spotlight: Rishi Mondal

Some contributors show up with a question. Rishi Mondal showed up with merged pull requests worth of context.

He’s a Site Reliability Engineer at Obmondo, a CNCF project maintainer, and a Docker Captain — a designation that puts him in the top 1% of contributors and community leaders in the global container ecosystem. That’s not a collection of titles. It’s the output of someone who has spent years doing the actual work across Kubernetes, distributed systems, and open-source infrastructure, and who keeps showing up after the patch lands.

The arc from participant to mentor

Rishi completed Google Summer of Code twice. That means he’s been through the full experience: landing in an unfamiliar codebase, shipping real changes under real deadlines, and earning trust from maintainers who have no reason to give it until you do.

What’s more telling is what came next. Rather than move on, he came back as a mentor — now serving as a GSoC Mentor with CNCF and OWASP, and as an LFX Mentor with the Linux Foundation. That’s a different kind of contribution. It’s not about shipping features; it’s about making sure the next person in has a cleaner path than you did.

That instinct — build the contributor, not just the code — is exactly what open source needs more of at scale, and it’s part of why Rishi’s presence in the community carries weight beyond his commit count.

Visibility that was earned

Rishi has spoken at KubeCon India and KCD Delhi 2026, and his contributions have been recognized by CNCF leadership at KubeCon India. He’s been selected as a delegate for the Harvard Project for Asian and International Relations (HPAIR) and as a Linux Foundation LIFT Scholar. He’s completing a Master of Computer Applications at Techno College Hooghly under Makaut University — apparently while doing everything else listed above.

None of this happened overnight. The visibility followed the work, which is the right order.

Why the database problem is personal

Rishi’s interest in OpenEverest isn’t theoretical. As an SRE who manages stateful workloads on Kubernetes, he runs directly into the problem the project exists to solve.

Kubernetes handles stateless services well. Databases are a different story. Teams end up patching together multiple operators with inconsistent APIs and fragile operational patterns. The alternative — managed DBaaS — trades away control and introduces vendor dependency. Neither option is satisfying when you’re the one carrying the pager.

OpenEverest takes a different approach: a single, Kubernetes-native control plane with declarative APIs for provisioning, scaling, backups, and recovery across multiple database engines. Vendor-neutral by design, which means it runs the same way whether you’re on cloud or on-premises, without locking you into anyone’s ecosystem.

As a CNCF Sandbox project, it also operates with open governance and community-driven development — the kind of foundation that makes long-term investment sensible.

“Contributing to OpenEverest aligns directly with the real-world challenges I solve as an SRE,” Rishi says. “It represents a meaningful step toward building a unified, open, and scalable data infrastructure layer within the Kubernetes ecosystem.”

The other stuff

When he’s not in front of a terminal, Rishi plays cricket, builds robots, and runs Raspberry Pi experiments. He approaches hardware the way a good SRE approaches production: break it deliberately, figure out why, rebuild it better.

He roams the city with friends when the debugging sessions run long enough to warrant it. And he has a well-documented habit of dropping Family Guy references into conversations that had absolutely nothing to do with Family Guy. Whether perfectly timed or entirely unnecessary is, apparently, beside the point.

We’re glad to have Rishi in the OpenEverest community. Connect with him on GitHub, LinkedIn, or his LFX Mentorship profile.

To get involved with OpenEverest yourself: