This framework is targeted to run test combinations as a matrix, like:
workload1 deployer1 (subscription)
workload2 x deployer2 (applicationset)
workload3 deployer3 (imperative)
Then in each test combination, it runs workload deploy, protect, failover, relocate, unprotect, undeploy.
It uses go test as fundamental framework, so it is able to utilize go test's output format as well as parallel test features.
Could run this framework in the e2e dir by:
go test -kubeconfig-c1 ~/.config/drenv/rdr-rdr/kubeconfigs/rdr-dr1 -kubeconfig-c2 ~/.config/drenv/rdr-rdr/kubeconfigs/rdr-dr2 -kubeconfig-hub ~/.config/drenv/rdr-rdr/kubeconfigs/rdr-hub -v
Note: need replace with actual kubeconfig files for each k8s if they have different names/locations.
Also could directly run make e2e-rdr in ramen root dir, if deploy minikubes with drenv tool and use 'rdr-' as prefix.
This framework is targeted to run test combinations as a matrix, like:
Then in each test combination, it runs workload deploy, protect, failover, relocate, unprotect, undeploy. It uses go test as fundamental framework, so it is able to utilize go test's output format as well as parallel test features.
Could run this framework in the e2e dir by:
go test -kubeconfig-c1 ~/.config/drenv/rdr-rdr/kubeconfigs/rdr-dr1 -kubeconfig-c2 ~/.config/drenv/rdr-rdr/kubeconfigs/rdr-dr2 -kubeconfig-hub ~/.config/drenv/rdr-rdr/kubeconfigs/rdr-hub -vNote: need replace with actual kubeconfig files for each k8s if they have different names/locations.
Also could directly run
make e2e-rdrin ramen root dir, if deploy minikubes with drenv tool and use 'rdr-' as prefix.