Skip to content

Commit

Permalink
Add submariner to volsync env
Browse files Browse the repository at this point in the history
Volsync creates a service on the destination cluster using ClusterIP or
LoadBalancer. The recommended way to make the service accessible to the
source cluster is using submariner export. Minikube has a tunnel command
that can expose services using LoadBalancer, but it is painful to use.

Since our submariner addon requires the broker on a separate cluster,
add a tiny hub cluster.

Work in progress

- volsync does not depend on submariner, but for testing it we must run
  after submariner is deployed and tested on all 3 clusters. So seems
  that we need to treat it like rbd-mirror, and move it to the global
  workers.
- volsync need to access the managed clusters so we can test replication
  both ways (like rbd-mirror).

Signed-off-by: Nir Soffer <nsoffer@redhat.com>
  • Loading branch information
nirs committed Jun 23, 2023
1 parent 54d68f4 commit caa8914
Showing 1 changed file with 13 additions and 0 deletions.
13 changes: 13 additions & 0 deletions test/envs/volsync.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,21 @@
name: volsync

templates:
- name: hub
driver: kvm2
container_runtime: containerd
network: default
cni: kindnet
memory: 2g
workers:
- addons:
- name: submariner
args: [hub, dr1, dr2]
- name: cluster
driver: kvm2
container_runtime: containerd
network: default
cni: kindnet
memory: 4g
disk_size: 50g
addons:
Expand All @@ -20,6 +31,8 @@ templates:
- name: volsync

profiles:
- name: hub
template: hub
- name: dr1
template: cluster
- name: dr2
Expand Down

0 comments on commit caa8914

Please sign in to comment.