kubectl get scaledobject only displays one trigger

[amirschw]

Report

For scaled objects with multiple triggers, kubectl get scaledobject only shows the first trigger:

~ $ k get scaledobject myapp
NAME           SCALETARGETKIND      SCALETARGETNAME   MIN   MAX   TRIGGERS     AUTHENTICATION   READY   ACTIVE   AGE
myapp          apps/v1.Deployment   myapp             1     2     prometheus                    True    True     7d

~ $ k get scaledobject myapp -o jsonpath='{.spec.triggers[*].type}'
prometheus cpu

Expected Behavior

All trigger types should be displayed

Actual Behavior

Only the first trigger is displayed

Steps to Reproduce the Problem

1. create a scaled object with two triggers
2. run kubectl get scaledobject

Logs from KEDA operator

N/A

KEDA Version

2.2.0

Kubernetes Version

1.19

Platform

Microsoft Azure

Scaler Details

any (e.g. prometheus, cpu, memory)

Anything else?

No response

[amirschw]

I took a closer look and found it's actually a kubectl issue with CRDs: kubernetes/kubectl#517.
LMK if you want me to close this one or keep it open until it's fixed upstream.

[tomkerkhove]

Thanks for checking! It's ok to keep it open.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

[tomkerkhove]

This is done in #2047, OK to close @zroubalik ?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed due to inactivity.

[SpiritZhou]

The CRD spec of scaleobject has added JSONPath to show all triggers. But kubectl still does not support displaying array type of printcolumn. kubernetes-sigs/controller-tools#652

[zroubalik]

Yes, that's the problem. Maybe we can workaround this by an additional Status field, that will be basically a string of all triggers. And then use this status field while printing the stuff by cli.