Heuristically forsee breaking changes of components used in all ManagedControlPlanes #130
Description
Description
As an operating team of openMCP, I would like to enable my organisation with latest and greatest operators.
Operators introduce new versions and include breaking changes.
For operators/providers in our hands, we heavily invest in upgrade tests to make upgrading experience as seemless as possible,
for external/open-source operators, we cannot achieve this.
We want to mitigate this pain though.
Technical Steps
TODO
Out of scope
- automatically approve changes in
ReleaseChannels
Acceptance criteria
- Report on upcoming breaking changes for all components used is generated, guiding on versions