Keda is not able to read Redis metadata ( address OR host+port) even though they are defined clearly in the scaled object.
Keda is able to scale in/out the deployment based on Redis list size..
And keda-operator deployment logs are
"error":"error getting scaler for trigger #0: error parsing redis metadata: no address given or host given. Address should be in the format of host:port or you should provide both host and port",
Keda is not able at all to read Redis from trigger's metadata
docker.io/kedacore/keda:1.4.1Deploy the ScaledObject :
```sh
apiVersion: keda.k8s.io/v1alpha1
kind: ScaledObject
spec:
cooldownPeriod: 30
maxReplicaCount: 10
minReplicaCount: 1
pollingInterval: 15
scaleTargetRef:
deploymentName: queue-worker-academy-laravel
scaleType: deployment
triggers:
## Specifications
- **KEDA Version:*`image: docker.io/kedacore/keda:1.4.1`* Keda is installed [from the Helm repository](https://kedacore.github.io/charts/index.yaml)
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
keda kube-system 1 2020-07-01 00:00:48.04236 +0300 +03 deployed keda-1.4.2 1.4.1
```
Similar to #560 .. but it is still persistent
Hi @abdennour, I found it very confusing, but address should actually reference the env var that contains the address in the target container... It should not be an address. Can you try that?
Ah! really ?
so if we will haveaddress: REDIS_ADDRESS..
This means REDIS_ADDRESS is an environment variable assigned to pods of the reference deployment .
In this case, REDIS_ADDRESS must be defined in queue-worker-academy-laravel.
Please correct me if i am mistaken ?
Also, what is the right syntax:
address: REDIS_ADDRESSaddress: ${REDIS_ADDRESS}@abdennour yeah that's correct, address: REDIS_ADDRESS should get it done
thank you @eexwhyzee . I will give it a trial
Did it fix your issue?
We will test it !