52ee5d0fff
* Docs: update CONTRIBUTING.md * Docs: clean up outdated roadmap and point to github issues instead * Docs: update note on kubelet_cgroup_driver * Docs: update kata containers docs with note about cgroup driver * Docs: note about CI specific overrides
1.1 KiB
1.1 KiB
CI Setup
Pipeline
- unit-tests: fast jobs for fast feedback (linting, etc...)
- deploy-part1: small number of jobs to test if the PR works with default settings
- deploy-part2: slow jobs testing different platforms, OS, settings, CNI, etc...
- deploy-part3: very slow jobs (upgrades, etc...)
Runners
Kubespray has 3 types of GitLab runners:
- packet runners: used for E2E jobs (usually long)
- light runners: used for short lived jobs
- auto scaling runners: used for on-demand resources, see GitLab docs for more info
Vagrant
Vagrant jobs are using the quay.io/kubespray/vagrant docker image with /var/run/libvirt/libvirt-sock
exposed from the host, allowing the container to boot VMs on the host.
CI Variables
In CI we have a set of overrides we use to ensure greater success of our CI jobs and avoid throttling by various APIs we depend on. See: