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 |
||
|---|---|---|
| .. | ||
| scale | ||
| BUILD | ||
| OWNERS | ||
| dns.go | ||
| dns_common.go | ||
| dns_configmap.go | ||
| dns_scale_records.go | ||
| doc.go | ||
| example_cluster_dns.go | ||
| firewall.go | ||
| framework.go | ||
| ingress.go | ||
| ingress_scale.go | ||
| kube_proxy.go | ||
| network_policy.go | ||
| network_tiers.go | ||
| networking.go | ||
| networking_perf.go | ||
| no_snat.go | ||
| proxy.go | ||
| service.go | ||
| service_latency.go | ||
| util_iperf.go | ||