You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When we want to copy data from pv between different clusters, pretty often we have problems getting a public IP on the source cluster, because when it comes to copying data, usually it is not controllable by ourselves, but the new (destination) has more control.
So, it's much easier to achieve a public IP on the destination cluster, than on the source.
But to make the pv-migrate work, the current implementation requires the public IP on the source cluster, not on the destination, so the migration is not possible because of this.
Describe the solution you'd like
To resolve this problem, will be good to implement a "push" mode, that will start the SSH server on the destination side, and push the data from the source pod to the destination, using the same rsync process.
The text was updated successfully, but these errors were encountered:
I am considering a temporary solution by reversing the source and destination in both cli param and the rsync configuration to sync files in the opposite direction.
Is your feature request related to a problem? Please describe.
When we want to copy data from pv between different clusters, pretty often we have problems getting a public IP on the source cluster, because when it comes to copying data, usually it is not controllable by ourselves, but the new (destination) has more control.
So, it's much easier to achieve a public IP on the destination cluster, than on the source.
But to make the pv-migrate work, the current implementation requires the public IP on the source cluster, not on the destination, so the migration is not possible because of this.
Describe the solution you'd like
To resolve this problem, will be good to implement a "push" mode, that will start the SSH server on the destination side, and push the data from the source pod to the destination, using the same rsync process.
The text was updated successfully, but these errors were encountered: