This repository has been archived by the owner on Apr 4, 2023. It is now read-only.

Automated testing of Navigator databases on multi-node Kubernetes clusters #359

Open

wallrj opened this issue May 15, 2018 · 0 comments

Labels

Milestone

Member

wallrj commented May 15, 2018 •

edited

Loading

/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

jetstack-bot added the kind/feature label

wallrj added this to the v0.3 milestone

wallrj mentioned this issue

Cassandra E2E tests fail on a multi-node cluster because we use hostpath volumes #351

Closed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.