Description of problem:

Need to specify the submariner version to download for disconnected environments

Version-Release number of selected component (if applicable):

All

How reproducible:

Always

Steps to Reproduce:

When following the instructions to configure submariner for ACM on disconnected clusters, customers will review this section first

https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.9/html/networking/networking#configuring-submariner-disconnected

Actual results:

Customers may inadvertently mirror the wrong version of the submariner operator version for the ACM release they are using by grabbing the latest instead of the version that was tested with ACM. For example, the latest version of submariner is 0.18.0 while for ACM 2.9, the customer should be using submariner 0.16.0.

This is highlighted in our documentation in this section, which is below where the current disconnected instructions start.

https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.9/html/networking/networking#using-a-customized-submariner-subscription

Expected results:

We should state exactly which submariner operator version that needs to be mirrored for the version of ACM that the customer is planning to install submariner on in the "Configuring Submariner on disconnected clusters" section. Section 1.4.1.1

Additional info: