-
Notifications
You must be signed in to change notification settings - Fork 63
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
The migration resource should be cluster-scoped #26
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Another reason to make the StorageVersionMigration API cluster-scoped: if there are two migration requests in two namespaces for the same resource, it's just confusing. |
Fixed by #37 |
A migration object represent a request to migrate a resource. There is no use case to have migration objects scattered in namespaces.
/assign
The text was updated successfully, but these errors were encountered: