-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Closed
Labels
QA/Marea/provisioning-v2Provisioning issues that are specific to the provisioningv2 generating frameworkProvisioning issues that are specific to the provisioningv2 generating frameworkrelease-noteNote this issue in the milestone's release notesNote this issue in the milestone's release notesstatus/release-note-addedteam/area2/scteam/hostbustersThe team that is responsible for provisioning/managing downstream clusters + K8s version supportThe team that is responsible for provisioning/managing downstream clusters + K8s version support
Milestone
Description
Today, Rancher runs the cluster-api controllers in an embedded fashion, see: https://github.com/rancher/rancher/blob/8bee06f75426e17c2ef7bacf11a0554a4754efb2/pkg/provisioningv2/capi/capi.go for a reference. Unfortunately, this makes maintenance of cluster-api versions a nightmare. For example, we can't bump from v1.2 to v1.3 or v1.4 because of K8s and controller-runtime dependencies.
We should move to running the cluster-api controllers in a more traditional fashion, i.e. run the controllers in a pod managed by the cluster-api operator.
cc: @richardcase this is going to be important for you folks.
richardcase
Metadata
Metadata
Assignees
Labels
QA/Marea/provisioning-v2Provisioning issues that are specific to the provisioningv2 generating frameworkProvisioning issues that are specific to the provisioningv2 generating frameworkrelease-noteNote this issue in the milestone's release notesNote this issue in the milestone's release notesstatus/release-note-addedteam/area2/scteam/hostbustersThe team that is responsible for provisioning/managing downstream clusters + K8s version supportThe team that is responsible for provisioning/managing downstream clusters + K8s version support