Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KEP-0008: Multi-cluster - Proposals for CLI Changes #345

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions keps/0008-multi-cluster.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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