From 42f5a947b3b0d87a089bc935f616bf64b658b288 Mon Sep 17 00:00:00 2001 From: Miles-Garnsey Date: Thu, 10 Mar 2022 15:53:37 +1100 Subject: [PATCH] Add proposed changes for the CLI to support multi-cluster tests. Signed-off-by: Miles-Garnsey --- keps/0008-multi-cluster.yaml | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/keps/0008-multi-cluster.yaml b/keps/0008-multi-cluster.yaml index 5ad98130..b0728eed 100644 --- a/keps/0008-multi-cluster.yaml +++ b/keps/0008-multi-cluster.yaml @@ -50,3 +50,14 @@ If the kubeconfig setting is set, then it will be used for all Kubernetes operat Note that the `kubeconfig` setting on the `TestStep` would be unaffected by the global Kubernetes configuration, so the `--kubeconfig` flag, `$KUBECONFIG` environment variable, etc, will be ignored for these steps. A namespace is generated for each `TestCase` and this needs to be created in each cluster referenced by `TestSteps` within the `TestCase`. At the beginning of the `TestCase`, the generated namespace will be created in every cluster used in the `TestCase`. The namespaces will also be deleted at the end if `--skip-delete` is not set. + +## Proposal - CLI + +Because running multi-cluster tests entails a far more complex set of configurations we propose to make use the the following command line options illegal when the `TestSuite` calls for a multi-cluster configuration: +- --kind-config +- --kind-context + +We propose that the following CLI flags should apply across all clusters when a multi-cluster `TestSuite` is defined: + +- --skip-cluster-delete +- --start-kind \ No newline at end of file