11/8/2023 0 Comments Dapr kubernetes annotationsShould be set to the same broker connection string used in the kafka-pubsub.yaml file. Should be set to the same topic to which your Dapr deployment subscribed (in this example, demo-topic). Given how Kafka partition offset works, you shouldn’t set that value higher than the total number of topic partitions. The maximum number of replicas for your deployment. Otherwise, set to 0 and KEDA creates the first replica for you. If your application takes a long time to start, it may be better to set this to 1 to ensure at least one replica of your deployment is always running. The minimum number of replicas KEDA creates for your deployment. The frequency in seconds with which KEDA checks Kafka for current topic partition offset. The Dapr ID of your app defined in the Deployment (The value of the dapr.io/id annotation). Let’s review a few metadata values in the file above: Values Manages component updates and Kubernetes services endpoints for Dapr (state stores, pub/subs, etc.) dapr-sidecar-injector: Injects Dapr into annotated deployment pods and adds the environment variables DAPRHTTPPORT and DAPRGRPCPORT to enable user-defined applications to easily communicate with Dapr without hard-coding Dapr port values. Topic: demo-topic bootstrapServers: .local:9092 consumerGroup: autoscaling-subscriber lagThreshold: "5" Name: pollingInterval: 15 minReplicaCount: 0 maxReplicaCount: 10 triggers: HuaweiCloud Cloud Secret Management Service (CSMS)ĪpiVersion: keda.sh/v1alpha1 kind: ScaledObject metadata:.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |