Refactor test suite to remove K3s container dependency (#971)

- Removed K3s container setup and teardown logic from CLI and E2E test suites.
- Simplified Kubernetes client initialization by eliminating the need for K3s container.
- Updated InitFromKubeconfig function to no longer require K3s container as a parameter.
- Deleted unused HelmInstaller and RESTClientGetter implementations.
- Cleaned up logging functions related to K3s and Helm operations.
This commit is contained in:
Enrico Candino
2026-07-02 10:10:48 +02:00
committed by GitHub
parent fa16898689
commit 3db4cc0652
10 changed files with 20 additions and 747 deletions
+1 -6
View File
@@ -106,12 +106,7 @@ When running the tests the namespaces used are cleaned up. If you want to keep t
KEEP_NAMESPACES=true make test-e2e
```
The e2e and cli tests run against the cluster configured in your KUBECONFIG environment variable. Running the tests with the `K3K_DOCKER_INSTALL` environment variable set will use `tescontainers` instead:
```
K3K_DOCKER_INSTALL=true make test-e2e
```
The e2e and cli tests run against the cluster configured in your KUBECONFIG environment variable. Make sure K3k is installed on that cluster (e.g. with `make install`) before running them.
We use [Ginkgo](https://onsi.github.io/ginkgo/), and [`envtest`](https://book.kubebuilder.io/reference/envtest) for testing the controllers.