e2e: Add a submariner validation test to the e2e Validation suite

[raghavendra-talur]

It could be useful to have a simple submariner validation test in the validation suite. Sometimes the submariner connection is broken and exiting early on detecting that would be better than running the tests and failing at a later point.

Note: validation suite is supposed to be a readonly suite and therefore the test shouldn't create any namespace or pods to verify the connection. We can only check for the details in the hub and the managed clusters to verify that submariner is setup correctly.

[raghavendra-talur]

@nirs @ShyamsundarR @BenamarMk Do you think this is a valid issue?

[nirs]

It could be useful to have a simple submariner validation test in the validation suite. Sometimes the submariner connection is broken and exiting early on detecting that would be better than running the tests and failing at a later point.

It can be useful for ocp clusters, with drenv cluster we already test the cluster during creation, so we know that submariner is working, and we know that we can replicate pvcs with volsync via submariner.

But if we will have #1702 this check can be there. Lets wait with this until we make more progress on the tool.

Note: validation suite is supposed to be a readonly suite and therefore the test shouldn't create any namespace or pods to verify the connection. We can only check for the details in the hub and the managed clusters to verify that submariner is setup correctly.

There is no way to test without creating a service export and import and using them to access one cluster from the other - as we do in the submariner self test:
https://github.com/RamenDR/ramen/blob/main/test/addons/submariner/test

I think there is no issue to create a temporary namespace like e2e-validation-xyz and deleting it after the test. I thinks that subctl is doing stuff like this.