Using secret on triggers metadata attribute #373
robertmujica
started this conversation in
Ideas
Replies: 1 comment 8 replies
-
You can do this by using TriggerAuthentication (https://keda.sh/docs/2.1/concepts/authentication/#re-use-credentials-and-delegate-auth-with-triggerauthentication) |
Beta Was this translation helpful? Give feedback.
8 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Wondering if it is possible to use secret's value instead of hardcoded values during triggers definition
so instead of doing this
metadata:
bootstrapServers: localhost:9092
consumerGroup: my-group # Make sure that this consumer group name is the same one as the one that is consuming topics
topic: test-topic
# Optional
lagThreshold: "50"
offsetResetPolicy: latest
authenticationRef:
name: keda-trigger-auth-kafka-credential
we would do something like
name: secret-name
metadata:
bootstrapServers: BOOTSTRAP_SERVER_FROM_SECRET
consumerGroup: my-group # Make sure that this consumer group name is the same one as the one that is consuming topics
topic: TOPIC_FROM_SECRET
# Optional
lagThreshold: "50"
offsetResetPolicy: latest
authenticationRef:
name: keda-trigger-auth-kafka-credential
so we don't have to duplicate this value and expose value for security reasons across a repo.
Beta Was this translation helpful? Give feedback.
All reactions