Commit Graph

7 Commits (539438ed2f9eab77abfe91e2aaca2295db274af3)

Author SHA1 Message Date
Steven Powell 4e33f96173 add timeout and force to kubectl command 2023-03-01 13:07:46 -08:00
Sharif Elgamal 8cf0a18069 no need to reverse file order for kubectl delete 2021-10-26 11:46:29 -07:00
Sharif Elgamal aaf85032f4 fix unit test part deux 2021-10-26 10:34:46 -07:00
Sharif Elgamal 77da350d83 fix unit test 2021-10-26 09:01:58 -07:00
Thomas Stromberg bd627f13e4 Plumb config.ClusterConfig throughout addon validation code 2020-03-10 17:49:47 -07:00
Priya Wadhwa 15a5209841 Update unit tests 2020-01-22 14:23:32 -08:00
Priya Wadhwa 7247a7dee6 Switched to using kubectl apply and kubectl delete for addons
kubectl apply with --prune wasn't working because it requires the
--namespace flag to be passed in and we have multiple namespaces for
addons.

We tried to split up addons within /etc/kubernetes/addons by
namespace, but this didn't work when disabling dashboard addon because
there were no files left in the kubernetes-dashboard subdirectory. So,
kubectl apply complained when trying to prune dashboard because no files
were being passed in.

So, I ended up removing all dependencies on prune and instead running
`kubectl apply` when enabling an addon and running `kubectl delete` when
disabling an addon.
2020-01-22 14:18:20 -08:00