Epic: Support Family Providers in our Releasechannel #30
Description
Understand the Epic
Currently we do not support family providers in our Releasechannel such as:
- gcp
- aws
- azure
We want to support these as well
Context / Background
Our users should be able to add family providers as managed components to their setups.
User Stories or tasks
I as a maintainer of a MCP landscape want to add family providers as managed components to my MCP landscape
I as a customer of an mcp landscape want to install family providers as managed components
I as a maintainer of a MCP landscape want to mirror family providers the same way as standard providers into my own OCI registry as OCM components.
I as a maintainer of a MCP landscape want to add provider families just by adding the main family provider.
What is required to accept the Epic as finished.
- Releasechannel supports whole provider families to be added
- Releasechannel mirrors provider families
- mirrored provider families change their family provider location to a mirrored one
Dependencies of this Epic
- new OCM localization feature could help achieve this, check status on that.
Risks of this Epic
- provider families are more complex then single providers, as they all need the main family provider as a dependency. This also needs to be localized to a mirrored releasechannel registry
- to solve this, we need to rewrite the image paths via crossplane:
Known Stakeholders of this Epic
- maintainers of MCP landscapes
- users of MCP landscapes
Milestone Definitions for this Epic.
- Mirroring family providers with relocalization
- Making family providers available as OCM components in releasechannel
- integrating popular family providers into control-plane-operator (gcp, aws, azure)
Metrics Definition for this Epic.
- provider families are mirrorable through releasechannel
- provider families are addable in releasechannel
Any further valuable resources.
https://docs.crossplane.io/latest/concepts/image-configs/#rewriting-image-paths