🐛 tenancy/workspace-deletion: try harder with the admin client to delete the LogicalCluster #3119
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.
Summary
The front-proxy might return errors when looking for the
LogicalCluster
on workspace deletion,especially when the
LogicalCluster
is already gone, and it returns a 403. This PR adds another attempt through the workspace admin client.Related issue(s)
Fixes #
Release Notes