Description of problem:

When submariner is not installed on a Regional DR setup, and the intention is to check whether globalnet is required on the setup or not, odf cli dr-prereq check doesn't tell this information.

When below cmd is run on say C1 (for peer cluster C2)-

odf get dr-prereq sagrawal-nc1
Info: Submariner is not installed.
Error: no matches for kind "Cluster" in version "submariner.io/v1"

When below cmd is run on say C1 (for same cluster C1)-

odf get dr-prereq sagrawal-nc2
Info: Submariner is not installed.
Error: no matches for kind "Cluster" in version "submariner.io/v1"

This is not at all useful because the decision to enable/disable globalnet has to be taken before installing submariner and not after.

Hence the current implementation is not useful for customers.

Version-Release number of selected component (if applicable):
ODF CLI 4.17
OCP 4.17.0-0.nightly-2024-10-14-225948

How reproducible:

Steps to Reproduce:
1. On a 4.17 setup, before installing submariner on it, run odf cli cmd to check if globalnet is needed or not.

On C1-

odf get dr-prereq <PeerManagedClusterName(ClusterID)>

2.
3.

Actual results: When submariner is not installed, odf cli dr-prereq check doesn't tell if globalnet is required or not on the setup

Expected results: When submariner is not installed, odf cli dr-prereq should be able to tell whether globalnet is required or not on the setup depending upon service networks being used on the managed clusters.

Additional info: