a684bb9f5b
* Ensure k8s apply works with check mode Update the new predicted object with fields from the previous object before applying in check mode Don't log output of `file` with `state: absent` on huge virtualenvs! Fixes #60510 * Use openshift client fix to improve apply for check mode Use new apply_object method to get a better approximation of the expected object in check mode. Requires released upgrade to openshift * Add changelog fragment for k8s apply check mode fix * Update changelogs/fragments/60510-k8s-apply-check-mode.yml Co-Authored-By: Felix Fontein <felix@fontein.de> |
||
---|---|---|
.. | ||
defaults | ||
files | ||
meta | ||
tasks | ||
aliases | ||
README.md |
Wait tests
wait tests require at least one node, and don't work on the normal k8s openshift-origin container as provided by ansible-test --docker -v k8s
minikube, Kubernetes from Docker or any other Kubernetes service will suffice.
If kubectl is already using the right config file and context, you can just do
cd test/integration/targets/k8s
./runme.sh -vv
otherwise set one or both of K8S_AUTH_KUBECONFIG
and K8S_AUTH_CONTEXT
and use the same command