<p>I'm using <a href="https://keda.sh/" rel="nofollow noreferrer">KEDA</a> to scale my pods on EKS cluster. I want to have trigger enabled on both CPU and Memory based scalers in the ScaledObject so here is my code chunk:-</p>
<pre><code>spec:
  scaleTargetRef:
    name: workload-processor
  cooldownPeriod: 120
  minReplicaCount: 1
  maxReplicaCount: 3
  triggers:
  - type: cpu
    metadata:
      type: AverageValue
      value: &quot;70&quot;
  - type: memory
    metadata:
      type: AverageValue
      value: &quot;70&quot;
</code></pre>
<p>I'm trying to use both types of triggers (cpu and memory) here in same YAML file. When I run the <code>kubectl get scaledobject</code> command then it shows triggers enabled only on CPU but not on both including memory:-</p>
<pre><code>NAME                          SCALETARGETKIND      SCALETARGETNAME   MIN   MAX   TRIGGERS   AUTHENTICATION   READY   ACTIVE   FALLBACK   AGE
workload-processor-keda-scaler   apps/v1.Deployment   workload-processor   1     3     cpu                         True    True     Unknown 
</code></pre>
<p>Am I doing anything mistake here? How can I enable the trigger for both? Should I write two separate scaledobject YAML files (one for CPU and another for Memory)?</p>

<p>Functionally it has got all the triggers when I do <code>kubectl get scaledobject -o yaml</code>. The problem is with the CRD itself as it is not able to display all the triggers on CLI. It is an existing bug and have been already reported here <a href="https://github.com/kedacore/keda/issues/1943" rel="nofollow noreferrer">https://github.com/kedacore/keda/issues/1943</a></p>
