Hey everyone! I'm on a mission to spruce up my resume with some operator-based projects as I transition into my first role as a Kubernetes developer. While I'm keeping an eye out for open-source projects where I can help out, I feel like I also need to tackle some personal projects to really showcase my skills. I've been brainstorming for project ideas but haven't landed on anything yet.
I want to work on something that highlights my ability to use multiple controllers, CRDs, a manager, and validating/mutating webhooks, while also keeping my code clean and well-organized with necessary tests. One idea I have is to create a CRD for managing RBAC more effectively, but I've noticed a similar project called rbac-manager that might be losing steam. If anyone has experience with it, I'm curious about potential improvements for that project.
I also thought of adding another CRD to regulate which actions an RBAC role can't perform across namespaces or clusters, kind of like what policy agents do but simpler and tailored for RBAC.
What do you think would be a useful and challenging addition to this project? Honestly, I'm not too worried about the idea being groundbreaking—I'm just looking for a solid challenge that shows I have a grasp on controllers and the operator pattern. If you have other project ideas, I'd love to hear them too!
2 Answers
It sounds like you're considering writing a custom operator, right? It can be tough to nail down a solid idea unless you're facing a specific issue at work or maybe even using AI tools for inspiration. Best of luck with it!
You could check out an open-source project that's available only via helm chart but has some ongoing needs, like day-2 operations. Building an operator for that could really enhance the project while letting you gain hands-on experience. Plus, having a community around it means your work will likely be appreciated and used! You could keep expanding on it over time.
What do you mean by 'day 2 ops'? That sounds intriguing!