Files
coredns/.travis/kubernetes
Yong Tang a2bd9ad3f5 Use docker container (instead of binary) for kubectl and travis cleanup (#352)
This fix uses docker container for kubectl. Since Kubernetes docker
image hyperkube has already been downloaded and it consists of
kubectl, there is really no need to download kubectl binary again.

This fix cleans up the Kubernetes related travis setup and removes
unneeded scripts.

This fix also fixes several mismatches of the Kubernetes version used,
so that any changes in version in the future only need to update .travis.yml.

Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
2016-10-20 11:06:15 -07:00
..
2016-10-05 16:17:52 +01:00

Test scripts to automate kubernetes startup

Requirements: docker

The scripts in this directory startup kubernetes with docker as the container runtime. After starting kubernetes, a couple of kubernetes services are started to allow automatic testing of CoreDNS with kubernetes. The kubernetes integration tests in test/kubernetes_test.go depend on having some sample services running. The scripts in this folder automate the launch of kubernetes and the creation of the expected sample services.

To start up kubernetes and launch some sample services, run the script setup_k8s_services.sh.

$ ./setup_k8s_services.sh

After running the above scripts, kubernetes will be running on the localhost with the following services exposed:

~~ NAMESPACE NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE default kubernetes 10.0.0.1 443/TCP 48m demo mynginx 10.0.0.168 80/TCP 9m demo webserver 10.0.0.28 80/TCP 2m test mynginx 10.0.0.4 80/TCP 2m test webserver 10.0.0.39 80/TCP 2m ~~