Is your feature request related to a problem? Please describe.
There may be cases where there's no network path between the source and destination clusters and this case is covered by the local strategy but that seems to use k8s port-forwarding putting extra load on the API server.
Describe the solution you'd like
This strategy could use the same approach as the existing local strategy but create the LBs and use them for tunnelling instead of k8s port forwarding.
Describe alternatives you've considered
The local strategy would work for my use case but it will be a problem for larger amounts of data.
Additional context
The port-forward approach is still valid for some use cases but trying to use the LB first could be a good option to alleviate the impact on the API server.
Is your feature request related to a problem? Please describe.
There may be cases where there's no network path between the source and destination clusters and this case is covered by the local strategy but that seems to use k8s port-forwarding putting extra load on the API server.
Describe the solution you'd like
This strategy could use the same approach as the existing local strategy but create the LBs and use them for tunnelling instead of k8s port forwarding.
Describe alternatives you've considered
The local strategy would work for my use case but it will be a problem for larger amounts of data.
Additional context
The port-forward approach is still valid for some use cases but trying to use the LB first could be a good option to alleviate the impact on the API server.