test(e2e): add OwnerReference GC behavior test #463
Merged
Conversation
This file contains 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
njhale
force-pushed
the
test-ownerref-gc
branch
from
34adb20 to
ff9d512
Compare
- Adds AddOwner function with blocking parameters to ownerutil - Adds OwnerReference GC behavior test
njhale
force-pushed
the
test-ownerref-gc
branch
from
ff9d512 to
215f526
Compare
ecordell
pushed a commit
to ecordell/operator-lifecycle-manager
that referenced
this pull request
Mar 8, 2019
test(e2e): add OwnerReference GC behavior test
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.
Description
Adds an e2e test on OwnerReference behavior to ensure a resource with multiple OwnerReferences will not be garbage collected when one of its owners has been deleted.
Test Case:
Motivation
OLM can make use of this expected behavior to drive features like managed resource adoption in self-hosted upgrades, permission management in CSV upgrades, etc. Currently, there is a lack of Kubernetes documentation on the effect multiple OwnerReferences have on garbage collection. This test is required ensure OwnerReferences interact with garbage collection as we expect.