Migrate scan kubernetes finalizers to avoid warnings about non-recommended finalizer url structure #3226
Conversation
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
non-recommended finalizer url structure
We've been getting this warning logged in the operator for a while now:
```txt
{"level":"info","ts":"2025-08-20T19:00:44Z","msg":"metadata.finalizers:
\"s3.storage.securecodebox.io\": prefer a domain-qualified finalizer
name including a path (/) to avoid accidental conflicts with other
finalizer writers"} ```
This should resolve this.
Related migration code removal ticket secureCodeBox#3225
Signed-off-by: Jannik Hollenbach <jannik.hollenbach@owasp.org>
✅ Deploy Preview for docs-securecodebox canceled.
|
|
Reet00
approved these changes
Aug 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Description
We've been getting this warning logged in the operator for a while now:
{"level":"info","ts":"2025-08-20T19:00:44Z","msg":"metadata.finalizers: \"s3.storage.securecodebox.io\": prefer a domain-qualified finalizer name including a path (/) to avoid accidental conflicts with other finalizer writers"}This should resolve this.
Related migration code removal ticket #3225
Checklist