There was some recent changes to Minikube that added a hard
dependency on that file being there which are not caught by
upstream testing since they don't test with the "none" VM
driver.
This adds the file to workaround the issue so that it can
complete the bootstrap of the cluster.
Change-Id: I3869350ae620721ea4e755e50facd0291a7772d3
Minikube provides addons and we can enable specific addons by passing the --addons arg when using minikube cli
Change-Id: I8d10e3a3dde1070b5c79406285035dacb59dddc8
The minikube v1.10.x is appending the systemd-resolved conf always.
So to workaround this problem, do a patch after deployment.
Change-Id: I813151761ebeb24b3d78f2a5a6c96ca6ffd81f21
This patch refactors ensure-kubernetes to use the new generic role
to allow it to be cross-platform in the future.
Change-Id: Ic90c8973431823814c7e6b122f4ef25a67d64c2f
This adds a custom ansible-lint rule at .rules/ZuulJobsNamespaceLoopVar.py
that enforces the loop var policy described at:
https://zuul-ci.org/docs/zuul-jobs/policy.html#ansible-loops-in-roles
It also updates existing roles to follow the policy.
Change-Id: I92b2ff56a1c2702542fc07b316f1809087a4c92f