Revisit CRD Status conditions (and reason, messages, etc...) #902
Description
Proposal
We should revisit the conditions to make them useful for users. Too much unrelated info makes the status not useful for users and generates a lot of noise on CRD.
We should also refactor the "conditions code" to make it closer to KEDA's "conditions code". Standardization will help as more than having 2 ways for doing the same thing
Use-Case
No response
Is this a feature you are interested in implementing yourself?
Yes
Anything else?
No response