v1.15.0
,latest
(v1.15.0/Dockerfile)v1.14.3
, (v1.14.3/Dockerfile)v1.13.7
, (v1.13.7/Dockerfile)v1.12.9
, (v1.12.9/Dockerfile)v1.11.9
, (v1.11.9/Dockerfile)v1.10.12
, (v1.10.12/Dockerfile)v1.9.10
, (v1.9.10/Dockerfile)v1.8.15
, (v1.8.15/Dockerfile)v1.7.16
(v1.7.16/Dockerfile)v1.6.13
, (v1.6.13/Dockerfile)v1.5.8
, (v1.5.8/Dockerfile)v1.4.12
, (v1.4.12/Dockerfile)v1.3.10
, (v1.3.10/Dockerfile)v1.2.6
, (v1.2.6/Dockerfile)v1.1.8
, (v1.1.8/Dockerfile)v1.0.7
, (v1.0.7/Dockerfile)
This container provides the Kubernetes client kubectl which can be used to interact with a Kubernetes cluster
make docker_build
docker run --rm lachlanevenson/k8s-kubectl:``git rev-parse --abbrev-ref HEAD`` --server=http://<server-name>:8080 get pods
In order to get kube spec files accessible via the kubectl container please use the following data container that exposes a data volume under /data. It dumps everything under cwd in the data container.
cat ~/bin/mk-data-container
#!/usr/bin/env sh
WORKDIR="$1"
if [ -z $WORKDIR ]; then
WORKDIR='.'
fi
cd $WORKDIR
echo "FROM debian:jessie\n\nVOLUME [ '/data' ]\n\nCOPY * /data/" > ./Dockerfile.data-container
docker rm data
docker build -f ./Dockerfile.data-container -t temp/data .
docker run --name data temp/data
rm ./Dockerfile.data-container
docker run --rm -it --volumes-from data k8s/kubectl:<tag> --server=http://<server-name>:8080 create -f /data/controller.yml