DNS debugging documentation is using a busybox image as example. This image has different known issues with the way it resolves the DNS names in k8s, creating confusion with users that try to follow the docs. The e2e tests use a custom small image ~4.3MB for DNS testing with all the necessary tools. Also, the fact that this image is being used for the k8s e2e testing guarantees it's compatibility. |
||
---|---|---|
.. | ||
admin | ||
application | ||
audit | ||
configmap | ||
controllers | ||
debug | ||
federation | ||
minikube | ||
podpreset | ||
pods | ||
policy | ||
service | ||
windows | ||
README.md | ||
examples.go | ||
examples_test.go |
README.md
Note: These tests are importing code from kubernetes that isn't really meant to be used outside the repo. This causes vendoring problems. As a result, we have to work around those with these lines in the travis config:
- rm $GOPATH/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery
- rm $GOPATH/src/k8s.io/kubernetes/vendor/k8s.io/apiserver
- rm $GOPATH/src/k8s.io/kubernetes/vendor/k8s.io/client-go
- cp -r $GOPATH/src/k8s.io/kubernetes/vendor/* $GOPATH/src/
- rm -rf $GOPATH/src/k8s.io/kubernetes/vendor/*
- cp -r $GOPATH/src/k8s.io/kubernetes/staging/src/* $GOPATH/src/