Remove the embedded clusterctl Config
kind/refactorarea/build-and-release
This issue is about removing the embedded config-community.yaml and config-prime.yaml.
The CAPI Core provider can be pinned by the Turtles chart.
The certified providers can be pinned using the Turtles Providers chart.
Without a need for embedded configs, the separate community/prime builds can also be removed, to simplify the release process.
Last but not least, the `enableAutomaticUpdate` CAPIProvider feature should be disabled on the Turtles Providers chart (since the version is going to be pinned explicitly). Still to evaluate if it makes sense to deprecate this feature already or to do it together with ClusterctlConfig deprecation if any, as some users may be using this API in combination with `enableAutomaticUpdate` to pin providers versions.
0 条评论