containerized-data-importer/cluster-up/cluster/README_VGPU.md
Alex Kalenyuk fed4d7a604
Update kubevirtci, 1.29 lanes (#3023)
* Update kubevirtci

May help with nfs lane flaking:
https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_containerized-data-importer/3017/pull-containerized-data-importer-e2e-nfs/1731266718799499264
Looks like the nfs server is working but mount commands from nfs csi against it are timing out.

Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>

* Use crictl to prepull images

https://github.com/kubevirt/kubevirtci/pull/1100

Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>

* Add W/A for NFS OOMKills

Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>

* Switch testing lanes to 1.29/1.28

Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>

---------

Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>
2024-03-25 23:41:20 +01:00

1.4 KiB

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.

export KUBEVIRT_PROVIDER=kind-1.x-vgpu
make cluster-up

The cluster can be accessed as usual:

$ cluster-up/kubectl.sh get nodes
NAME                  STATUS   ROLES    AGE     VERSION
vgpu-control-plane   Ready    master   6m14s   v1.x.y

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.