ad133069aa
As part of the move to helm v3, we migrated how we setup deploying kubernetes from a series of playbooks to using a bash script. This had the advantage of being easier to follow and deploy locally, as well as easier to debug when an issue arose. While the kubeadm-aio was very useful in the past to help lower run-times, currently it appears that optimizations in our jobs have seem to mitigate a lot of the issues that were lessened with the AIO. Change-Id: If0c6a97aed4083307a9b6f5beb4ec525e8103e01 |
||
---|---|---|
.. | ||
build-helm-packages | ||
clean-host/tasks | ||
deploy-apparmor/tasks | ||
deploy-docker | ||
deploy-jq/tasks | ||
deploy-package | ||
deploy-python/tasks | ||
deploy-python-pip | ||
deploy-selenium/tasks | ||
describe-kubernetes-objects/tasks | ||
disable-local-nameserver/tasks | ||
gather-host-logs/tasks | ||
gather-pod-logs/tasks | ||
gather-prom-metrics/tasks | ||
gather-selenium-data/tasks | ||
helm-release-status/tasks | ||
osh-run-script | ||
osh-run-script-set | ||
override-images | ||
setup-firewall/tasks | ||
upgrade-host |