containerized-data-importer/cluster-up/cluster/kind-1.31
Alex Kalenyuk 8949310eb2
Update kubevirtci with new rook ceph, 1.32 lanes (#3624)
* 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>
2025-03-05 21:21:31 +01:00
..
conformance.json Update kubevirtci with new rook ceph, 1.32 lanes (#3624) 2025-03-05 21:21:31 +01:00
image Update kubevirtci with new rook ceph, 1.32 lanes (#3624) 2025-03-05 21:21:31 +01:00
provider.sh Update kubevirtci with new rook ceph, 1.32 lanes (#3624) 2025-03-05 21:21:31 +01:00
README.md Update kubevirtci with new rook ceph, 1.32 lanes (#3624) 2025-03-05 21:21:31 +01:00
version Update kubevirtci with new rook ceph, 1.32 lanes (#3624) 2025-03-05 21:21:31 +01:00

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 right CLUSTER_NAME is exported.