Why
In some scenarios it is useful to add a non blocking warning to a user on how a custom resource was parsed and reconciled. This will highlight unintended consequences of fields added or omitted from the spec of the custom resource.

How
Investigate existing patterns used in OpenShift/Kubernetes for adding warnings to the Status block and implement one small example in the 3scale Operator to act as a precedent for other controllers.

If we encounter an warning the reconciler should continue.

We should allow for multiple warning messages to be added to the CR