Description of problem:

Not sure if this is a bug or a very small feature, but in discussions with both the Orchestrator and OSL teams, there has been some concern that customers are upgrading OSL outside of the versions that have been validate/tested with Orchestrator. So in this section, we were wondering if we should be more explicit around the expectations so that customers understand the implications:

https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.8/html-single/orchestrator_in_red_hat_developer_hub/index#con-compatibility-guide-for-orchestrator_orchestrator-rhdh

Specifically:

"The following table lists the RHDH Orchestrator plugin versions and their compatible corresponding infrastructure versions."

We were thinking it might be advantageous to state something more firm by adding something along the lines of:

"Using the Orchestrator plugin with any unvalidated/unverified versions of infrastructure cannot be guaranteed to work, and customers will be doing so at their own risk."