feat(harbor-scanner-sysdig-deploy): Allow usage of an existing secret for cliScanning #2254
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
Signed-off-by: Stephen Hwang <126002920+sthwang-metal@users.noreply.github.com>
…adding a new feature
mavimo
approved these changes
May 16, 2025
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 this PR does / why we need it:
This allows the jobs spun up when cliScanning is enabled to use a secret with a different name than 'harbor-scanner-sysdig-secure.fullname'. This is useful if there is a secret defined with the same name for a different purpose.
This is a cherry-pick of PR:
#2247
Checklist
feat(agent,node-analyzer,sysdig-deploy):)