Have you solved a tricky problem recently? Do you have an “epic story” from production that taught you a valuable lesson?
We are opening up the Challenges category for community contributions, and we want YOU to design the next adventure.
Creating a challenge is one of the best ways to demonstrate your expertise and help others level up their skills in the open-source ecosystem. Whether it’s a Kubernetes misconfiguration, an Observability puzzle, or a CI/CD pipeline that needs saving.
If it can be solved, it can be a Challenge.
Why contribute a Challenge?
-
Build Your Reputation: Show the community (and potential employers) that you don’t just know the tech, you can teach it.
-
Give Back: Help newcomers bridge the gap between “reading documentation” and “fixing real problems.”
-
Rewards & Spotlights: Top contributors get featured in a spotlight and receive exclusive community rewards!
What makes a good Challenge?
We focus on Vendor-Agnostic and Open Source technologies. A great challenge usually has three parts:
-
The Hook (The “Adventure”): A short story setting the scene. (e.g., “The junior dev deleted the secret, and now the pod is crashing…”)
-
The Broken State: A snippet of code, a manifest, or a repo that is “broken” or needs implementation.
-
The Solution: A clear, verifiable goal. (e.g., “The application should return a 200 OK status.”)
How to Contribute
-
Reply to this thread with a rough concept or idea.
-
Our team will review it, help you polish the “Story” aspect, and verify the technical solution.
-
Once approved, we will publish it as an official Adventure with credit to you!
Let’s build the ultimate open-source training ground, one broken pod at a time. 