-
Notifications
You must be signed in to change notification settings - Fork 155
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
Drop support of LimitRange and NetworkPolicy resources from Tenant #740
Comments
@prometherion I love the idea, but I have the following concern - for |
@MaxFedotov if well understanding #736 is blocking write operations on |
Exactly, replicated resources write operations are blocked to tenant owners, but obviously if the cluster administrator deletes those ones there's the |
I think we should postpone this refactoring to v0.6.0 since the upcoming one is already busy with a new feature and we should proceed one by one since the documentation must be aligned properly. |
With the implementation of
{Global}TenantResource
we started having a sort of overlap with the Tenant API:spec.limitRanges.items
andspec.networkPolicies.items
allow specifying a set of resources that must be replicated across the Tenant namespaces, and this can be easily achieved starting from v0.2.0 with the new APIs that replicate objects.If we're going to accept this proposal the change must be considered a breaking change, and I'd vote to rename the current expected milestone (v0.4.0) to be considered a major one (v1.0.0), since end users would need to manually migrate the replicated resources to the new API kind.
@bsctl @MaxFedotov @oliverbaehler let's start the discussion!
The text was updated successfully, but these errors were encountered: