From 74751f1f89c116d62c58b11294d818a829c52c8b Mon Sep 17 00:00:00 2001 From: Jirka Kremser Date: Mon, 2 Dec 2024 13:48:37 +0100 Subject: [PATCH] dapr example: http scaler Signed-off-by: Jirka Kremser --- examples/dapr/README.md | 11 +++++------ examples/dapr/nodeapp-so-v3.yaml | 9 ++++++++- 2 files changed, 13 insertions(+), 7 deletions(-) diff --git a/examples/dapr/README.md b/examples/dapr/README.md index e125590..d06cf60 100644 --- a/examples/dapr/README.md +++ b/examples/dapr/README.md @@ -107,15 +107,14 @@ SO ## Scaling Behavior -Each replica of `pythonapp` microservice calls the `nodeapp` microservice each second. Checke the following part of the ScaledObject: -```yaml - metricQuery: 'sum(runtime_service_invocation_req_recv_total{app_id="nodeapp",src_app_id="pythonapp"})' - operationOverTime: 'rate' -``` - Each replica of the pythonapp microservice makes a call to the nodeapp microservice every second. Check the following part of the ScaledObject configuration: +```yaml +metricQuery: 'sum(runtime_service_invocation_req_recv_total{app_id="nodeapp",src_app_id="pythonapp"})' +operationOverTime: 'rate' +``` + - The runtime_service_invocation_req_recv_total metric increments each time the `pythonapp` calls `nodeapp`. - One of the metric dimensions is the pod identity, meaning each pod exposes these metrics with its label attached. - Similar to PromQL, if not all dimensions are specified, multiple metric series will be returned. diff --git a/examples/dapr/nodeapp-so-v3.yaml b/examples/dapr/nodeapp-so-v3.yaml index 95a0d75..098740f 100644 --- a/examples/dapr/nodeapp-so-v3.yaml +++ b/examples/dapr/nodeapp-so-v3.yaml @@ -15,7 +15,14 @@ spec: clampMax: '10' - type: kedify-http metadata: -# todo: + trafficAutowire: service + service: nodeapp-dapr + fallbackService: nodeapp-dapr-original + portName: dapr-http + hosts: nodeapp-dapr.default.svc.cluster.local + scalingMetric: requestRate + targetValue: '10000' + minReplicaCount: 0 advanced: horizontalPodAutoscalerConfig: