About Drivers

A Test Kitchen driver is what supports configuring the compute instance that is used for isolated testing. This is typically a local hypervisor (Hyper-V), hypervisor abstraction layer (Vagrant), or cloud service (AWS EC2).

Driver availability depends on the Ruby environment that runs kitchen. A system Ruby install, Cinc Workstation, and Chef Workstation may each provide a different set of installed driver gems. Check the environment you are using before assuming a driver is available:

gem list kitchen-vagrant
chef gem list kitchen-vagrant

Install missing driver gems into that same environment.

Drivers documented here

Driver Target
Amazon AWS (EC2) Amazon EC2
Apache CloudStack Apache CloudStack, Citrix CloudPlatform
DigitalOcean DigitalOcean droplets
Dokken (Docker) Docker containers, optimized for Chef Infra
Google Cloud Platform Google Compute Engine
Hetzner Cloud Hetzner Cloud servers
HashiCorp Vagrant Local hypervisors via Vagrant
Microsoft Azure Azure Resource Manager
Microsoft Hyper-V Local Hyper-V
OpenStack OpenStack, including Rackspace OpenStack Flex
VMware vCenter VMware vCenter
VMware vRealize Automation vRealize Automation

Other driver projects

These drivers exist but are not documented on this site. Check each project for current status before adopting it:

There are other drivers that have existed over the life of Test Kitchen that we do not list here, either because they are unmaintained or have been supplanted by other drivers.