mirror of https://github.com/k3s-io/k3s
8b17db7e0c
Not all users of the E2E framework want to run cloud-provider specific tests. By splitting out the code it becomes possible to decide in a E2E test suite which providers are supported. This is achieved in two ways: - the framework calls certain functions through a provider interface instead of calling specific cloud provider functions directly - tests that are cloud-provider specific directly import the new provider packages The ingress test utilities are only needed by a few tests. Splitting them out into a separate package makes the framework simpler for test suites not using those tests. Fixes: #66649 |
||
|---|---|---|
| .. | ||
| apimachinery | ||
| apps | ||
| auth | ||
| autoscaling | ||
| chaosmonkey | ||
| common | ||
| framework | ||
| generated | ||
| instrumentation | ||
| kubectl | ||
| lifecycle | ||
| manifest | ||
| network | ||
| node | ||
| perftype | ||
| scalability | ||
| scheduling | ||
| servicecatalog | ||
| storage | ||
| testing-manifests | ||
| ui | ||
| upgrades | ||
| BUILD | ||
| README.md | ||
| e2e-example-config.json | ||
| e2e.go | ||
| e2e_test.go | ||
| examples.go | ||
| gke_local_ssd.go | ||
| gke_node_pools.go | ||
README.md
See e2e-tests