Issues facing in cleaning up the service mesh.

As part of POV , we are trying to install our workload in ROSA .
Previously we tried to install the Redhat ServiceMesh 1 and faced some configurations challenges, due to which we had to clean up and reinstall with the ServiceMesh 2 version.

Unfornutately what we see if that ServiceMesh operator is not present in the installed Operator section. However we can see the ServiceMeshMemberRole and ServiceMeshControlPlane instance are still present and stuck.
E.g

C:\Users\sanu_s>oc get smmr
NAME READY STATUS AGE
default 0/2 ReconcileError 3d1h

C:\Users\sanu_s>oc get smcp
NAME READY STATUS PROFILES VERSION AGE
basic 6/9 PausingInstall ["default"] 3d1h

For the SMMR we see the below error.
Member Statuses:
Conditions:
Last Transition Time: 2022-12-11T03:44:52Z
Message: Namespace another-of-your-projects does not exist
Reason: NamespaceNotExists
Status: False
Type: Reconciled
Namespace: another-of-your-projects
Conditions:
Last Transition Time: 2022-12-11T03:44:52Z
Message: Namespace your-project does not exist
Reason: NamespaceNotExists
Status: False
Type: Reconciled
Namespace: your-project

And for the SMCP

Conditions:
Last Transition Time: 2022-12-11T03:43:58Z
Message: Installing mesh generation 1
Reason: ResourceCreated
Status: False
Type: Installed
Last Transition Time: 2022-12-11T03:43:58Z
Message: Paused until the following components become ready: [istio-egress istio-ingress]
Reason: PausingInstall
Status: False
Type: Reconciled
Last Transition Time: 2022-12-11T03:43:58Z
Message: Paused until the following components become ready: [istio-egress istio-ingress]
Reason: PausingInstall
Status: False
Type: Ready
Readiness:
Components:
Pending:
kiali
Ready:
grafana
istio-discovery
mesh-config
prometheus
telemetry-common
tracing
Unready:
istio-egress
istio-ingress

Our basic requirement is to have multiple microservice running and we need a gateway ( Isitio gateway / Ingress etc etc) and routing to the microservice by handling by matching the context path ( E.g creating VirtualService ). Is there any such documentation which we can refer ?

Route Service is not a options as we need to handle the multiple API changes in our consumer application which is not the desired architecture.