containerized-data-importer/cluster-up/cluster/k8s-1.13.3
Alexander Wels f8dad13db6
Update kubevirtci images to refresh certificates. (#973)
Signed-off-by: Alexander Wels <awels@redhat.com>
2019-09-24 19:08:24 -04:00
..
provider.sh Update kubevirtci k8s version to 1.15.1 2019-08-15 08:24:34 -04:00
README.md Update kubevirtci images to refresh certificates. (#973) 2019-09-24 19:08:24 -04:00

Kubernetes 1.13.3 in ephemeral containers

Provides a pre-deployed Kubernetes with version 1.13.3 purely in docker containers with qemu. The provided VMs are completely ephemeral and are recreated on every cluster restart. The KubeVirt containers are built on the local machine and are then pushed to a registry which is exposed at localhost:5000.

Bringing the cluster up

export KUBEVIRT_PROVIDER=k8s-1.13.3
export KUBEVIRT_NUM_NODES=2 # master + one node
make cluster-up

The cluster can be accessed as usual:

$ cluster/kubectl.sh get nodes
NAME      STATUS     ROLES     AGE       VERSION
node01    NotReady   master    31s       v1.13.3
node02    NotReady   <none>    5s        v1.13.3

Bringing the cluster down

export KUBEVIRT_PROVIDER=k8s-1.13.3
make cluster-down

This destroys the whole cluster. Recreating the cluster is fast, since k8s is already pre-deployed. The only state which is kept is the state of the local docker registry.

Destroying the docker registry state

The docker registry survives a make cluster-down. It's state is stored in a docker volume called kubevirt_registry. If the volume gets too big or the volume contains corrupt data, it can be deleted with

docker volume rm kubevirt_registry