Spec the status reporting behaviour

[alexsnaps]

Using limitador server as an example to illustrate the scope of this issue:

When a new RateLimitPolicy is added or modified it will ultimately be reflected as a change to a ConfigMap mounted on the Limitador pod. While things can go "wrong" along the way to the CM, all actors are "k8s aware" and can reflect any status changes so to report to the users. It is necessary for us to decide how to report these back up the chain to the user. But when things make it to Limitador, the server as no way to report back to k8s. So we need to decide how Limitador could for instance report a syntax error in a Condition back to the matching RateLimitPolicy (possibly translating to "what" actually triggered the condition to be "generated" in this "invalid" form).

• Spec it all in a RFC
  • Kuadrant Policies Status conditions/states architecture#9
• Implementation work
  • Readiness probe Authorino

[alexsnaps]

Dup // see Kuadrant/architecture#9