![]() * Bump kvci to latest (new rook ceph) Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com> * Switch testing lanes to 1.32/1.31 Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com> * address some common make target failures this addresses common annoying flakes with make targets or adds logging to be able to debug them Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com> --------- Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com> |
||
---|---|---|
.. | ||
conformance.json | ||
image | ||
provider.sh | ||
README.md | ||
version |
K8S with mdev support in a Kind cluster
Provides a pre-deployed k8s cluster that runs using kind The cluster is completely ephemeral and is 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
The following needs to be executed as root. Please refer to the name of the directory to get the kind version.
export KUBEVIRT_PROVIDER=kind-x.yz
make cluster-up
The cluster can be accessed as usual:
$ cluster-up/kubectl.sh get nodes
NAME STATUS ROLES AGE
kind-x.yz-control-plane Ready master 6m14s
Bringing the cluster down
make cluster-down
This destroys the whole cluster.
Setting a custom kind version
In order to use a custom kind image / kind version, export KIND_NODE_IMAGE, KIND_VERSION before running cluster-up. For example in order to use kind 0.9.0 (which is based on k8s-1.19.1) use:
export KIND_NODE_IMAGE="kindest/node:v1.19.1@sha256:98cf5288864662e37115e362b23e4369c8c4a408f99cbc06e58ac30ddc721600"
export KIND_VERSION="0.9.0"
This allows users to test or use custom images / different kind versions before making them official. See https://github.com/kubernetes-sigs/kind/releases for details about node images according to the kind version.
- In order to use
make cluster-down
please make sure the rightCLUSTER_NAME
is exported.