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

Blocking replicated resources write operations put in place by tenant owners #736

Merged
merged 4 commits into from
Mar 28, 2023

Conversation

prometherion
Copy link
Member

Closes #732.

@MaxFedotov @oliverbaehler @bsctl WDYT of this? Essentially, replicated resources managed through a GlobalTenantResource or a TenantResource cannot be deleted or edited by Tenant Owners. This leads to avoiding an inconsistent state of the replicated resources.

Keep in mind that resources can be deleted by admin users or k8s controller managers.

@netlify
Copy link

netlify bot commented Mar 23, 2023

Deploy Preview for capsule-documentation canceled.

Name Link
🔨 Latest commit 234aab2
🔍 Latest deploy log https://app.netlify.com/sites/capsule-documentation/deploys/641da978ce41d100080ce002

@bsctl
Copy link
Member

bsctl commented Mar 23, 2023

@prometherion that's looks good. Just suggest to use the same strategy for all types of tenant resources, i.e. blocking vs reconciliating. Do we have different ways to handle tenant resources in the current implementation?

@prometherion
Copy link
Member Author

Just suggest to use the same strategy for all types of tenant resources

We can discuss it in a new issue/discussion for the upcoming release, but definitely it would be interesting, although breaking from the API perspective because, if I understood correctly, it means moving the NetworkPolicy and LimitRange definitions from the Tenant API to the GlobalTenantResource.

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

Successfully merging this pull request may close these issues.

Prevent replicated resources by TenantResource to get deleted by the Tenant Owner
2 participants