kilo/e2e/setup.sh

#!/usr/bin/env bash
# shellcheck disable=SC1091
. lib.sh

setup_suite() {
	create_cluster "$(build_kind_config 2)"
}
e2e: reuse kind cluster across suites Currently, each test suite spins up its own kind cluster, which results in longer e2e test times as each test suite needs to wait for the cluster to be ready and for images to download. This commit creates two new virtual test suites that are run before and after the actual e2e tests and are responsible for creating and destroying a kind cluster respectively. Any test suite that needs a fresh cluster can still spin up its own using the `create_cluster` helper in the lib.sh file. Signed-off-by: Lucas Servén Marín <lserven@gmail.com> 2021-07-02 12:32:36 +00:00			`#!/usr/bin/env bash`
			`# shellcheck disable=SC1091`
			`. lib.sh`

			`setup_suite() {`
e2e: allow parameterizing kind config This commit allows the kind cluster configuration to be parameterized at call time. This enables the test suite to build multiple clusters with different configurations, e.g. different CIDRs, different numbers of nodes, etc. Signed-off-by: Lucas Servén Marín <lserven@gmail.com> 2021-07-05 11:14:23 +00:00			`create_cluster "$(build_kind_config 2)"`
e2e: reuse kind cluster across suites Currently, each test suite spins up its own kind cluster, which results in longer e2e test times as each test suite needs to wait for the cluster to be ready and for images to download. This commit creates two new virtual test suites that are run before and after the actual e2e tests and are responsible for creating and destroying a kind cluster respectively. Any test suite that needs a fresh cluster can still spin up its own using the `create_cluster` helper in the lib.sh file. Signed-off-by: Lucas Servén Marín <lserven@gmail.com> 2021-07-02 12:32:36 +00:00			`}`