Remove separate Prime/Community builds. #2041
Description
What would you like to be added (User Story)?
This issue is about implementing proposal number 4 of the pinning ADR: https://github.com/rancher/turtles/blob/main/docs/adr/0016-capi-version-pinning.md
Having separate builds is a complication for building, testing, and it represents a conceptual overhead in the Turtles architecture.
Currently there are too many ways of overriding providers tags and images and it all differs depending on the Turtles build type:
- Hardcoded in Turtles
- ClusterctlConfig
- CAPIProvider.spec.version
Detailed Description
Considerations:
- The decision has been made already to release turtles-chart-providers with turtles-chart, following the same release process and schedule.
- To support airgap scenarios, turtles-chart-providers is already pinning images and versions, they can be used for CAPIProvider overrides and pinning as well.
Proposal:
- Remove the hardcoded clusterctlconfig from Turtles
- Only build one Turtles artifact for Prime and Community
- Use the turtles-providers-chart to pin Certified providers versions
- (Optional) Deprecate ClusterctlConfig, it's no longer necessary and only creates confusion. CAPIProvider API should be used instead for image overrides and version pinning.
- (Optional) Let Rancher install turtles-providers-chart together with Turtles as system chart, if Prime. Note it would be best to be able to select which providers to install, so these options need to be exposed at user level.
Anything else you would like to add?
No response
Label(s) to be applied
/kind feature