d023f3d25d
Back in the v1alpha2 days the fuzzer test needed to be disabled. To ensure that there were no config breaks and everything worked correctly extensive replacement tests were put in place that functioned as unit tests for the kubeadm config utils as well. The fuzzer test has been reenabled for a long time now and there's no need for these replacements. Hence, over time most of these were disabled, deleted and refactored. The last remnants are part of the LoadJoinConfigurationFromFile test. The test data for those old tests remains largely unused today, but it still receives updates as it contains kubelet's and kube-proxy's component configs. Updates to these configs are usually done because the maintainers of those need to add a new field. Hence, to cleanup old code and reduce maintenance burden, the last test that depends on this test data is finally refactored and cleaned up to represent a simple unit test of `LoadJoinConfigurationFromFile`. Signed-off-by: Rostislav M. Georgiev <rostislavg@vmware.com> |
||
|---|---|---|
| .. | ||
| app | ||
| test | ||
| .import-restrictions | ||
| BUILD | ||
| kubeadm.go | ||
| OWNERS | ||