Repository navigation
🐛 Fix Delete of PartialObjectMetadata for kinds not in the scheme - #3631
Open
DerekFrank wants to merge 1 commit into
Open
DerekFrank wants to merge 1 commit into
DerekFrank wants to merge 1 commit into
Conversation
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: DerekFrank The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
Since v0.25.0 the typed client decodes the delete response (controller-runtime#3472). For a
PartialObjectMetadataof a kind that isn't in the client's scheme, that decode fails whenever the server returns the object, for example when finalizers hold it. The caller getsno kind "..." is registeredeven though the delete succeeded.PartialObjectMetadatadeletes now go through the unstructured client, which decodes any kind.I only ran into this working on an update to Delete() that stores the response, I'm not actually sure if it can hit anyone in practice
Tests
A regression test in
client_test.godeletes a ChaosPod held by a finalizer through a client whose scheme doesn't have ChaosPod. It fails without this change.Release note: Fix
DeleteofPartialObjectMetadatafor kinds not in the scheme returning an error after the object was deleted.