Re-check previously owned#411
Merged
Merged
Conversation
cnvergence
previously approved these changes
Nov 28, 2025
ntnn
reviewed
Nov 28, 2025
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
mjudeikis
enabled auto-merge (squash)
December 1, 2025 15:23
mjudeikis
force-pushed
the
mjudeikis/previously.claimed
branch
from
December 1, 2025 15:24
dc2fa95 to
add7fcb
Compare
ntnn
approved these changes
Dec 1, 2025
cnvergence
approved these changes
Dec 1, 2025
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
3 participants
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
What Type of PR Is This?
If I create sync relationship using reference (Cert-Manager) and delete the object after - secret might be still lurking. For this, if we still have label indiciating that it was "claimed before" - we need to re-check again.
Related Issue(s)
Fixes #
Release Notes