Skip to content

Commit b0e462a

Browse files
authored
Merge pull request #55296 from RichardHoch/dvn_alt_net_conn
2 parents e833598 + 7e81495 commit b0e462a

File tree

1 file changed

+20
-1
lines changed

1 file changed

+20
-1
lines changed

modules/migration-about-configuring-proxies.adoc

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,26 @@ spec:
132132
type: Deny
133133
----
134134

135-
[id="configuring-supplemental-groups-for-rsync-pods{context}"]
135+
[id="choosing-alternate-endpoints-for-data-transfer_{context}"]
136+
=== Choosing alternate endpoints for data transfer
137+
138+
By default, DVM uses an {product-title} route as an endpoint to transfer PV data to destination clusters. You can choose another type of supported endpoint, if cluster topologies allow.
139+
140+
For each cluster, you can configure an endpoint by setting the `rsync_endpoint_type` variable on the appropriate *destination* cluster in your `MigrationController` CR:
141+
142+
[source, yaml]
143+
----
144+
apiVersion: migration.openshift.io/v1alpha1
145+
kind: MigrationController
146+
metadata:
147+
name: migration-controller
148+
namespace: openshift-migration
149+
spec:
150+
[...]
151+
rsync_endpoint_type: [NodePort|ClusterIP|Route]
152+
----
153+
154+
[id="configuring-supplemental-groups-for-rsync-pods_{context}"]
136155
=== Configuring supplemental groups for Rsync pods
137156
When your PVCs use a shared storage, you can configure the access to that storage by adding supplemental groups to Rsync pod definitions in order for the pods to allow access:
138157

0 commit comments

Comments
 (0)