You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
metallb: Remove metallb-operator submodule and all metallb references
MetalLB is no longer needed in this repository. This removes the
git submodule, feature-configs, test paths, namespace variables,
and all related script/documentation references.
Copy file name to clipboardExpand all lines: cnf-tests/README.md
+4-11Lines changed: 4 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,13 +15,12 @@ Table of Contents
15
15
16
16
The conformance test suites verify that the operators we maintain are working properly on CNF-enabled clusters. The suites are "validationsuite", "configsuite", and "cnftests". The underlying Ginkgo test suites run by each suite can be found in the `TESTS_PATHS` variable in `hack/common.sh` in the root directory.
17
17
18
-
To prevent dependency conflicts, we use git submodules to store external repositories: `cluster-node-tuning-operator`, `metallb-operator`, and `sriov-network-operator`, in the path `cnf-tests/submodules`.
18
+
To prevent dependency conflicts, we use git submodules to store external repositories: `cluster-node-tuning-operator` and `sriov-network-operator`, in the path `cnf-tests/submodules`.
19
19
20
20
21
21
To specify the desired commit of the external repositories, we expose the following environment variables:
- IPERF3_BITRATE_OVERRIDE - set a maximum bitrate for iperf3 to use in ovs_qos tests
63
-
- SKIP_LOCAL_RESOURCES - use default test resource of dependant test suites, using hardcoded defaults instead, needed to successfuly run the metallb e2e tests
62
+
- SKIP_LOCAL_RESOURCES - use default test resource of dependant test suites, using hardcoded defaults instead
64
63
65
64
## Test Reports
66
65
@@ -72,12 +71,6 @@ The tests produce two kinds of outputs, which are stored in the directory specif
@@ -88,7 +81,7 @@ A JUnit-compliant XML file is produced for each test suite: `junit_cnftests.xml`
88
81
89
82
### Test Failure Report
90
83
91
-
A report containing information about the cluster state (and resources) for troubleshooting is produced for each failed test. For example, if a test fails in the metallb suite, the logs are dumped into the following file: `metallb_failure_report.log`.
84
+
A report containing information about the cluster state (and resources) for troubleshooting is produced for each failed test.
0 commit comments