-
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 with clusterclass #5499
✨ Clusterctl move with clusterclass #5499
Conversation
/hold |
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.
First pass
This is definitely going in the right direction, I have only some nits on tests/builders
0551b6f
to
90db0e3
Compare
90db0e3
to
b254592
Compare
Can we unhold? |
/hold cancel Yes, the other PR is merged. |
/lgtm |
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.
Looks good to me.
A few questions to confirm my understanding of clusterctl move
.
clusterctl move
currently only moves entire namespaces, correct? So we don't have to care about which Cluster is using which ClusterClass and if the ClusterClass can already be moved, etc. ...
I assume this PR enable clusterctl move, backup and restore with ClusterClass?
I wonder if we should have an e2e test for clusterctl move at some point (not in this PR). Out of curiosity, did you test it manually to make sure it works and we're not missing anything?
b254592
to
ea33388
Compare
ea33388
to
fc2bbbb
Compare
Yes, clsuterctl move operated on one namespace. Since ClusterClasses are also namespaced and a cluster can only use a clusterclass in the same namespace we can be sure that if a cluster is moving then the associated ClusterClass is also moving. To add to that ClusterClass is treated as a root of the graph. So ClusterClass along with all the associated templates (nodes in the clusterclass graph) will move along with it.
Yes. Backup and restore also uses the same underlying tooling as move. So once this PR will also support backup and restore.
Yes, I am already working on adding e2e tests for clusterctl move. I tested this a few times manually. After solving this I did not hit any other issues. |
Great, thx! |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini 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 |
What this PR does / why we need it:
This PRs add ClusterClass support to
clusterctl move
command.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #5445