KubeVirt cluster-sync

KubeVirt cluster-sync A workflow diagram generated by Archify. 01 / Developer shell 02 / Bazel build (hack/dockerized) 03 / Target cluster (kubevirtci) EX / Failure cluster-up cluster-sync cluster-up · make target · Developer shell › cluster-up cluster-up make target Provision · nodes + registry · Target cluster (kubevirtci) › cluster-up · up.sh Provision nodes + registry up.sh cluster-sync · DOCKER_TAG=devel · Developer shell › cluster-sync cluster-sync DOCKER_TAG=devel cluster-clean · KV CR, CRDs · Target cluster (kubevirtci) › cluster-sync · background cluster-clean KV CR, CRDs background Build + push · bazel, registry:5000 · Bazel build (hack/dockerized) › cluster-sync · cluster-build Build + push bazel, registry:5000 cluster-build Manifests · pullPolicy Always · Bazel build (hack/dockerized) › cluster-sync · manifests.sh Manifests pullPolicy Always manifests.sh cluster-deploy · operator + KV CR · Target cluster (kubevirtci) › cluster-sync cluster-deploy operator + KV CR Abort · clean failed, exit 1 · Failure › cluster-sync Abort clean failed, exit 1 hack/dump.sh · on deploy failure · Failure › cluster-sync hack/dump.sh on deploy failure provider up.sh in parallel wait $CLEAN_PID trap EXIT Legend make target script step cleanup / failure kubevirtci

cluster-up

  • • hack/cluster-up.sh sources kubevirtci up.sh for $KUBEVIRT_PROVIDER (k8s-1.3x VMs, kind-*, minikube, external)
  • • kubeconfig: kubevirtci/_ci-configs/<provider>/.kubeconfig; ephemeral providers expose registry:5000

cluster-sync

  • • cluster-clean runs in the background while images build and push with DOCKER_TAG=devel
  • • cluster-deploy applies testing infra, the operator, then the KubeVirt CR and waits for Available

On the SEV server

  • • KUBEVIRT_PROVIDER=external with your kubeconfig and a DOCKER_PREFIX the nodes can pull
  • • kind nodes are containers with no root misc cgroup, so sev-esids is never advertised (PR 17638)