adding support for setting up the secretKey in both user provided sec… #355
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
…ret or Komodor generated secret
amit9192
requested review from
MickaelAlliel,
nirbenator and
Moran-k
as code owners
Moran-k
reviewed
Feb 24, 2025
| initialDelaySeconds: 5 | ||
| periodSeconds: 5 | ||
| failureThreshold: 3 | ||
| failureThreshold: 3git |
There was a problem hiding this comment.
Suggested change
| failureThreshold: 3git | |
| failureThreshold: 3 |
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.
A customer uses external secrets and would like to utilize different key names per cluster to support easier automation of cluster onboarding.
I'm debating whether this should also be part of the Komodor agent chart managed secret but implemented it for both currently.