Design an Upstream Contribution to a CNCF Service-Mesh Project
Overview
What this challenge is about.
Design a Go module for a CNCF service-mesh control plane and write an RFC with tests. Earn a verifiable certificate.
The scenario
The company is a mid-sized financial-technology firm in London (~380 staff) whose payments platform runs on microservices coordinated by an open-source service-mesh control plane; it currently carries a private fork of that mesh to ship a fix the community has not yet accepted.
The Brief
What you'll do, and what you'll demonstrate.
Design an upstream open-source contribution — RFC, implementation, and engagement plan — that lands the needed control-plane fix and lets the company retire its costly internal fork.
Earning criteria — what you'll demonstrate
- Scope an open-source change conservatively, using non-goals to pre-empt maintainer objections
- Translate business cost (engineer-days on a fork) into an evidence-based upstream-versus-fork return-on-investment argument
- Write implementation and tests that match an existing project's idioms rather than imposing your own
- Plan respectful, norm-aware engagement within a CNCF project's published governance and review process
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Aligned coursework coming soon.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
- Oss Contribution
Apply oss contribution to solve real industry problems and demonstrate production-level capability.
- Rfc Design
Apply rfc design to solve real industry problems and demonstrate production-level capability.
- Pr Etiquette
Apply pr etiquette to solve real industry problems and demonstrate production-level capability.
- Upstream Strategy
Apply upstream strategy to solve real industry problems and demonstrate production-level capability.
- Code Review
Apply code review to solve real industry problems and demonstrate production-level capability.
- Governance Models
Apply governance models to solve real industry problems and demonstrate production-level capability.
Careers
Career paths this challenge builds toward
Completing this challenge demonstrates skills that transfer directly to these roles:
Open Source Software Engineer
This challenge mirrors the daily reality of contributing to a governed open-source project: scoping a change, writing idiomatic code with tests, and shepherding it through community review, which is exactly what an OSS-focused engineer does to ship features that outlive any single employer.
This challenge sharpens
- oss-contribution
- code-review
- rfc-design
Platform / Infrastructure Engineer
Platform engineers constantly weigh maintaining internal forks against upstreaming fixes; designing the RFC, the engagement plan, and the cost case here builds the exact judgment needed to keep a company's cloud-native stack on supportable, community-aligned software.
This challenge sharpens
- upstream-strategy
- governance-models
- pr-etiquette
Staff Software Engineer
Senior technical leaders are measured on influence across organizational boundaries; framing a conservatively scoped proposal, pre-empting objections, and justifying it with ROI is the cross-team persuasion work that defines staff-level engineering impact.
This challenge sharpens
- rfc-design
- upstream-strategy
- code-review