feat(k8-operator/infisicalsecret-crd): multiple secret references #2987
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
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 📣
This PR introduces support for having multiple secret references. It is a very minor change that will allow users to supply multiple managed secret references for where the secrets fetched from Infisical will go to.
If the user is using the old
managedSecretReferencefield, they will get a log in the operator output that says the field will be deprecated in the future. Currently there's no set date for when it will be deprecated, it's just meant to serve as a heads up to users that there is a new field that they should be using.I also refreshed our documentation a bit to be more inline with our other CRD's.
Type ✨