mirror of https://github.com/linkerd/linkerd2.git
b50ae6290d
* Add support for k3d in integration tests KinD doesn't support setting LoadBalancer services out of the box. It can be added with some additional work, but it seems the solutions are not cross-platform. K3d on the other hand facilitates this, so we'll be using k3d clusters for the multicluster integration test. The current change sets the ground by generalizing some of the integration tests operations that were hard-coded to KinD. - Added `bin/k3d` to wrap the setup and running of a pinned version of `k3d`. - Refactored `bin/_test-helpers.sh` to account for tests to be run in either KinD or k3d. - Renamed `bin/kind-load` to `bin/image-load` and make it more generic to load images for both KinD (default) and k3d. Also got rid of the no longer used `--images-host` option. - Added a placeholder for the new `multicluster` test in the lists in `bin/_test-helpers.sh`. It starts by setting up two k3d clusters. * Refactor handling of the `--multicluster` flag in integration tests (#4995) Followup to #4994, based off of that branch (`alpeb/k3d-tests`). This is more preliminary work previous to the more complete multicluster integration test. - Removed the `--multicluster` flag from all the tests we had in `bin/_test-helpers.sh`, so only the new "multicluster" integration test will make use of that. Also got rid of the `TestUninstallMulticluster()` test in `install_test.go` to keep the multicluster stuff around, needed for the more complete multicluster test that will be implemented in a followup PR. - Added "multicluster" to the list of tests in the `kind_integration.yml` workflow. - For now, this new "multicluster" test in `run_multicluster_test()` is just running the install tests (`test/integration/install_test.go`) with the `--multicluster` flag. Co-authored-by: Kevin Leimkuhler <kevin@kleimkuhler.com> |
||
|---|---|---|
| .. | ||
| ISSUE_TEMPLATE | ||
| workflows | ||
| CODEOWNERS | ||
| PULL_REQUEST_TEMPLATE.md | ||
| dco.yml | ||
| stale.yml | ||