Tuesday the 12th May is two weeks after announcing deprecation of the
install-* roles [1] and the date we should starting throwing an error
message to direct the user to use the renamed ensure-* role instead.
[1]
http://lists.zuul-ci.org/pipermail/zuul-announce/2020-April/000071.html
Change-Id: Ie2474c5c0704aa44f51bdd5d7afddb8c7e4e578b
The install-kubernetes role is now failing due to the fact that
minikube now requires conntrack. This patch solves this.
Change-Id: I1e59d5e9255064646bd8e8c6b6edb2c34d45b516
minikube has added a new "feature" which pre-loads a blob of data
with everything it needs that we can't disable, with a fallback.
we're currently downloading ~500MB and failing to use it because
it's compressed by lz4 which we don't have in images, this change
adds that to the package list.
Change-Id: If74faf2b21d564fa23253ea2eb5378457f055735
Per settings mentioned at: https://minikube.sigs.k8s.io/docs/tasks/debug/
The current logging level is very minimal for tracking down any
potential k8s issues.
Change-Id: I4ebd694481de936f9df790a46e195b251a803c5f
By default kubernetes wants to use the local resolvers on the host
system. But in many cases the local resolver may be 127.0.0.1 which is a
different localhost on the host system then in the container network
namespaces. To address this disconnect you can supply a different
resolv.conf with a list of nameservers to use instead. Add support for
this.
Note that the test currently only uses ipv4 resolvers because by default
k8s has no support for ipv6.
Change-Id: I3c0d7d88613e2c9112e809f036aef3dfeaf7ab72
With the arrival of ansible-lint 4, comparisons to literal boolean
values are now forbidden. Adjust the new violations accordingly and
remove the rule 601 exclusion.
Change-Id: I18ba2d7d41fabaff35d10d520037188c7d9d1249
It seems like new minikube changed the default minikube config
permission. This change ensures the minikube config is owned by
the ansible_user
Change-Id: Ic1af1541fb1f32253678f989d7b62d21074514d5
vass