-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🌱 clusterctl move ClusterResourceSets #3243
🌱 clusterctl move ClusterResourceSets #3243
Conversation
/milestone v0.3.7 |
771e8ee
to
9040843
Compare
9040843
to
088f89b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
/assign @sedefsavas
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vincepri The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@@ -275,7 +275,7 @@ func getMoveSequence(graph *objectGraph) *moveSequence { | |||
// NB. it is necessary to filter out nodes not belonging to a cluster because e.g. discovery reads all the secrets, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In L120, do we need to check control plane ready condition instead of clusterObj.Status.ControlPlaneReady
?
In my setup I don't see Status.controlPlaneReady anymore.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is required to install the CNI in order to get Status.controlPlaneReady
088f89b
to
fbd8d9a
Compare
/test pull-cluster-api-e2e |
1 similar comment
/test pull-cluster-api-e2e |
/lgtm |
What this PR does / why we need it:
This PR extends clusterctl move so it will manage to move the ClusterResourceSet objects defined in a namespace.
TL;DR of the changes: during the discovery phase that is executed before Move, we are identifying ClusterResourceSet and their descendants; those objects will be included in the move scope.
NB.
this PR will remain WIP until #3107 merges
/assign @vincepri
/assign @sedefsavas