feat: update keda CRD to new field serviceAccountName#897
Open
mario-valente wants to merge 1 commit into
Open
Conversation
Member
|
Hi @mario-valente, Thanks for the contribution. Could you please clarify whether this PR updates the entire CRD/schema from a specific upstream KEDA version, or whether it cherry-picks only the missing individual fields? If it is based on an upstream version, could you please share which KEDA version you used? |
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
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.
Adds the missing
serviceAccountNamefield to thecredentialobject underhashiCorpVaultin theTriggerAuthenticationCRD schema (keda.sh/triggerauthentication_v1alpha1.json).This field is present in the upstream KEDA CRD but was missing from this catalog entry.