In addition to the YAML configuration file, Conformance EE supports command-line flags for controlling test execution behavior.
| Flag | Default | Description |
|---|---|---|
--datacenters |
"" |
Comma-separated list of datacenters to test |
--kube-versions |
"" |
Comma-separated Kubernetes versions to test |
--skip-cluster-creation |
false |
Skip cluster creation; use existing clusters |
--skip-cluster-deletion |
false |
Keep clusters after tests (useful for debugging) |
--update-clusters |
false |
Upgrade existing clusters before running tests |
./e2e.test --datacenters=dc-1,dc-2
./e2e.test --kube-versions=1.31,1.32
When debugging test failures, use --skip-cluster-deletion to keep clusters alive for investigation:
./e2e.test --skip-cluster-deletion
If clusters from a previous run are still available, skip creation:
./e2e.test --skip-cluster-creation
Upgrade existing clusters to the next Kubernetes version before running tests:
./e2e.test --update-clusters --skip-cluster-creation
Since Conformance EE uses Ginkgo v2, all standard Ginkgo flags are also available:
| Flag | Description |
|---|---|
--ginkgo.v |
Verbose output |
--ginkgo.nodes=N |
Number of parallel Ginkgo nodes |
--ginkgo.focus="pattern" |
Run only specs matching the regex pattern |
--ginkgo.skip="pattern" |
Skip specs matching the regex pattern |
--ginkgo.label-filter="expression" |
Filter specs by Ginkgo labels |
--ginkgo.dry-run |
List all specs without executing them |
./e2e.test --ginkgo.focus="canal"
./e2e.test --ginkgo.nodes=8