Issue Description: 

Within RHOSE we use OSD clusters for both our control plane and data plane. OSD frequently updates the supported version(s), so we should have a process that ensures we have a controlled rollout of new OSD versions to our control plane and data plane.

In particular for our data plane, we should have a process for promoting a new version of OSD through our environments so that we have a chance to test RHOSE data plane components with the latest version of OSD, before it is applied to our production environment.

Acceptance Criteria: 

• Define a process for tracking the schedule of updates available for our OSD clusters
• Define a process for applying an OSD update to our environments, ensuring that lower environments are updated first e.g dev before stage, stage before production
• Provide an SOP or automation for making the upgrade process easily repeatable 
• Provide a simple way of tracking the versions of our OSD clusters in each environment
• Provide an audit trail for when our OSD clusters were upgraded and by whom

Additional Information: 

• Consider if we can manage the OSD versions via GitOps to provide us with the audit trail capabilities