chore: remove unused Vagrant release image (#13625)

* chore: remove unused Vagrant release image

Signed-off-by: Kay Yan <kay.yan@daocloud.io>

* docs: keep Vagrant image retirement in release notes

Signed-off-by: Kay Yan <kay.yan@daocloud.io>

---------

Signed-off-by: Kay Yan <kay.yan@daocloud.io>
This commit is contained in:
Kay Yan
2026-10-10 08:17:16 +00:00
committed by GitHub
parent b1881b5a3e
commit 131fd144cc
5 changed files with 3 additions and 63 deletions
+2 -2
View File
@@ -9,11 +9,11 @@ See [.gitlab-ci.yml](/.gitlab-ci.yml) and the included files for an overview.
Kubespray has 2 types of GitLab runners, both deployed on the Kubespray CI cluster (hosted on Oracle Cloud Infrastructure):
- pods: use the [gitlab-ci kubernetes executor](https://docs.gitlab.com/runner/executors/kubernetes/)
- vagrant: custom executor running in pods with access to the libvirt socket on the nodes
- vagrant: custom executor running jobs inside KubeVirt VMs
## Vagrant
Vagrant jobs are using the [quay.io/kubespray/vagrant](/test-infra/vagrant-docker/Dockerfile) docker image with `/var/run/libvirt/libvirt-sock` exposed from the host, allowing the container to boot VMs on the host.
Vagrant jobs use the `quay.io/kubespray/vm-kubespray-ci` VM image configured in [.gitlab-ci/vagrant.yml](/.gitlab-ci/vagrant.yml). Vagrant and libvirt run inside the KubeVirt VM to provision the test nodes.
## CI Variables