Description of problem: After the proper installation of the Submariner Addon following the https://red.ht/38CuIcT guide for ACM 2.2, there is an example for the definition of the ServiceExport in order to enable Service Discovery for Submariner that have a deprecated API and failed when you create the object in the RHACM v2.2: ``` # oc --context=hubcluster apply -f service-export-cluster1.yaml error: unable to recognize "service-export-cluster1.yaml": no matches for kind "ServiceExport" in version "lighthouse.submariner.io/v2alpha1" ``` Version-Release number of selected component (if applicable): 2.2 How reproducible: Install submariner in a RHACM v2.2 and try to add an object with the lighthouse.submariner.io/v2alpha1 API version as the documentation says: apiVersion: lighthouse.submariner.io/v2alpha1 kind: ServiceExport metadata: name: nginx namespace: default Install Steps to Reproduce: 1. Install RHACM 2.2 2. Install submariner following the official docs (https://red.ht/38CuIcT). 3. Deploy the Service Proxy object with the example that is in the official docs Actual results: error: unable to recognize "service-export-cluster1.yaml": no matches for kind "ServiceExport" in version "lighthouse.submariner.io/v2alpha1" Expected results: Created the service export object and connect the two services through submariner ipsec tunnels. Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Red Hat Advanced Cluster Management 2.2.2 security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:1168