Following the operator API evolution discussion, we added a runtime defaulting mechanism that relies on special annotations to persist state.

We should have a place in user documentation that explains:

• how this runtime defaulting mechanism works
• that annotations will remain in the CR indefinitely, and why
• which annotations are currently active and which are obsolete

We should also have a reminder to update the above, located in the code near the definition of defaulting flows (once https://issues.redhat.com/browse/ROX-29199 is done).