Blocking replicated resources write operations put in place by tenant owners #736
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #732.
@MaxFedotov @oliverbaehler @bsctl WDYT of this? Essentially, replicated resources managed through a
GlobalTenantResource
or aTenantResource
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.