Improve CRDs to write events to the resources

[tomkerkhove]

Proposal

Improve CRDs to write events to the resources so that cluster admins/app operators can inspect the CRDs and see what is going on.

Things that come to mind is:

• Scale to/from 0
• Authentication failures
• Fallback of trigger
• Triggers becoming active
• ...

Use-Case

Improve experience for cluster admins/app operators troubleshooting issues.

Anything else?

No response

[zroubalik]

I suppose this proposal is about improving the Status of the CRs created by users in the cluster. Not about the CRDs created by installation. I agree, the status exposed by each resource should be improved.

[tomkerkhove]

That, and provide updates in the event section around scaling - Actually what is proposed in #3822 to bring it closer to the resource.

Think this, but tailored to KEDA/scaling actions:

[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]

Example use-case: #4074 (reply in thread)

[tomkerkhove]

Any thoughts on this @kedacore/keda-maintainers?

[zroubalik]

+1

[JorTurFer]

+1

[SpiritZhou]

HI @tomkerkhove I noticed that some events are added. Here are the event list and example: https://github.com/kedacore/keda/blob/main/pkg/eventreason/eventreason.go

Could you specify what events should be added?

[JorTurFer]

I think that some of them like:

• KEDAScaleTargetActivated
• KEDAScaleTargetDeactivated
• ScaledJobCheckFailed
• ScaledObjectCheckFailed
• ScaledObjectReady
• ScaledJobReady

But also other new events for things like failures on authentication