Skip to content
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

move registry custom resource to be cluster scoped #38

Closed
bparees opened this issue Oct 15, 2018 · 0 comments
Closed

move registry custom resource to be cluster scoped #38

bparees opened this issue Oct 15, 2018 · 0 comments
Assignees

Comments

@bparees
Copy link
Contributor

bparees commented Oct 15, 2018

Since we only want one registry per cluster anyway (can't actually tolerate more than one) and because finalizers deadlock themselves when the finalizer and the resource being finalized run in the same namespace, we need to switch the registry resource CRD to be cluster scoped instead of namespace scoped.

/cc @deads2k

/assign @legionus

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants