-
Notifications
You must be signed in to change notification settings - Fork 288
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
Add Cluster Mover #7790
Add Cluster Mover #7790
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #7790 +/- ##
==========================================
+ Coverage 73.39% 73.46% +0.06%
==========================================
Files 576 577 +1
Lines 35622 35735 +113
==========================================
+ Hits 26144 26251 +107
- Misses 7826 7827 +1
- Partials 1652 1657 +5 ☔ View full report in Codecov by Sentry. |
Can we read the eksa objects from the kind cluster, pause the cluster and then apply those objects to the "management" cluster? |
0a3d7c7
to
09271e6
Compare
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tatlat 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 |
Issue #, if available:
Description of changes:
Currently for creation of management clusters, we apply EKS-Anywhere resources and waiting for conditions twice (once on bootstrap and again on workload). This causes the create command to take longer than necessary. This PR adds a way to move resources between clusters, which should shorten the time it takes to create management clusters.
Testing (if applicable):
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.