Can a single TriggerAuthentication object be used for multiple triggers? #1911
Answered
by
zroubalik
amirschw
asked this question in
Q&A / Need Help
-
Suppose I have a ScaledObject with multiple triggers - can I use the same TriggerAuthentication object for all triggers? Is this recommended? Or should I create a different TriggerAuthentication for each trigger? Example with two triggers (azure-queue and azure-servicebus): apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
name: myapp
namespace: keda
spec:
cooldownPeriod: 1800
maxReplicaCount: 10
minReplicaCount: 2
pollingInterval: 15
scaleTargetRef:
name: myapp
triggers:
- authenticationRef:
name: myapp
metadata:
messageCount: "5"
namespace: ns
subscriptionName: sub
topicName: topic
type: azure-servicebus
- authenticationRef:
name: myapp
metadata:
accountName: account
queueLength: "500"
queueName: queue
type: azure-queue
---
apiVersion: keda.sh/v1alpha1
kind: TriggerAuthentication
metadata:
name: myapp
namespace: keda
spec:
podIdentity:
provider: azure |
Beta Was this translation helpful? Give feedback.
Answered by
zroubalik
Jun 28, 2021
Replies: 1 comment 1 reply
-
Yeah, that was the original purpose behinds introducing TA :) |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
amirschw
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yeah, that was the original purpose behinds introducing TA :)