Goal

What is our purpose in implementing this? What are we enabling by doing this work? Time-box goals to 4-6 months.

Decompose the Clusters-service API, background workers, and other components into logical and maintainable individual services.

Benefit Hypothesis:

What are the benefits (to Red Hat, eventually to customers, to the community, etc.)? Does it improve security, performance, supportability, etc? Why is work a priority?

Clusters-service has become a very large monolithic service, resulting in slow and difficult feature development, a long on-boarding process for new engineers, and a large blast radius for breaking changes.

After decomposing CS, we expect to gain:

• Reduced blast radius for breaking changes
• The ability to implement new features and bugfixes for specific or all offerings quickly and efficiently
• Decreased engineer burnout scores
•  

Resources

Add any resources (docs, slides, etc.) pertinent to the definition of the work. These might not be known until later. Update as necessary.

Responsibilities

Indicate which roles and/or teams will be responsible for contributing to the initiative and generally what they might be expected to do.

Members of the multiple existing teams will be expected to design and agree upon a technical framework for decomposition, as well as a migration roadmap. Leaders of the teams will be expected to ensure precautions are taken to avoid introduction of breaking changes.

Success Criteria

Provide some examples of how we will know if we have achieved the goal. What can be measured to determine success? What observable actions/outcomes that can be seen to determine success? Specific, Measurable, Achievable, fits within the Time-box.

Results

Add results here once the Initiative is started. Recommend discussions & updates once per quarter in bullets.