Show identityId of pod identity in kubectl get triggerauthentication -o wide

[tomkerkhove]

Proposal

Show identityId of pod identity in kubectl get triggerauthentication -o wide to simplify investigation.

It should not specifically be a new field but can be azure-workload (foo) and azure-workload (default)/azure-workload when no identity ID was specified

Use-Case

No response

Is this a feature you are interested in implementing yourself?

No

Anything else?

No response

[JorTurFer]

Currently, that value is generated from .spec:

But we could introduce an internal status field with the information. The problem here IMHO will be that the real use case isn't azure-workload (foo), it is azure-workload (c27bf924-db20-4972-a528-b96ecb878895).
I'm not totally sure if this will be useful. we can't provide other info more than the given GUID

[tomkerkhove]

The problem here IMHO will be that the real use case isn't azure-workload (foo), it is azure-workload (c27bf924-db20-4972-a528-b96ecb878895).

That is the same actually, I was just lazy and used foo as example for app ID :)

I'm not totally sure if this will be useful. we can't provide other info more than the given GUID

That is exactly what is needed to be able to see if the App ID was correctly configured without having to open the YAML which I had to do due to #4528 (comment)

[JorTurFer]

Is the GUID useful? I mean, just having 2 states could solve it? My doubts are related with the GUID itself, maybe something like azure-workload (defalt) and azure-workload (provided) or something similar could be more useful, not having 36 characters in the output for seeing the GUID

[tomkerkhove]

Yes it is useful, because then you see what is configured. Provided is not very useful as you still have to check the details while the GUID shows exactly what you need imo

[tomkerkhove]

Any thoughts on this @kedacore/keda-maintainers?