This repository was archived by the owner on Apr 4, 2023. It is now read-only.
This repository was archived by the owner on Apr 4, 2023. It is now read-only.
Automated testing of Navigator databases on multi-node Kubernetes clusters #359
Description
/kind feature
Our E2E tests currently run on a single node minikube cluster and we run ad-hoc manual tests on multi-node clusters.
Instead, we want to run all our E2E tests on a multi-node cluster so that we can test:
- Larger multi-node database clusters
- database pod multi-node scheduling ( anti-affinity)
- database pod re-scheduling (node failures)
- changes of IP address
- multi-nodepool (multi rack / dc) scheduling
- effects of network policy on database clusters