-
Notifications
You must be signed in to change notification settings - Fork 35
Description
What would you like to be added (User Story)?
In the current implementation of the import controller, the Rancher management Cluster is only created once and never updated again.
Any modification to the original CAPI Cluster will not translate to the Rancher management Cluster. Any change to it, for example to edit the user readable description for the Cluster, will require a re-import, which is not exactly a user friendly workflow, especially for small cosmetic changes.
Detailed Description
The import process should keep syncing the CAPI Cluster to the Rancher management Cluster at any change.
The controller should:
- Watch the CAPI Cluster
- On CAPI Cluster mutation, update the Rancher management Cluster
It is not unclear why this is not the case already. Possibly an overlooked implementation detail or a conscious design choice. This needs to be investigated further.
There is a risk that reconciling the Rancher management Cluster will lead to unexpected conflicts with Rancher and/or create endless resource versions for the management Cluster resources due to inconsistent resource mutations.
See: https://github.com/rancher/turtles/blob/v0.25.1/internal/controllers/import_controller_v3.go#L302
Anything else you would like to add?
No response
Label(s) to be applied
/kind feature
Metadata
Metadata
Assignees
Labels
Type
Projects
Status