# Deploy Ignition Gateway with Ansible/Chef/Puppet/Powershell DSC or in Kubernetes **URL:** \ **Category:** General Discussion\ **Created:** [October 9, 2018, 7:10am UTC](https://forum.inductiveautomation.com/t/deploy-ignition-gateway-with-ansible-chef-puppet-powershell-dsc-or-in-kubernetes/20042 "2018-10-09T07:10:45Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [October 12, 2018, 12:18pm UTC](https://forum.inductiveautomation.com/t/deploy-ignition-gateway-with-ansible-chef-puppet-powershell-dsc-or-in-kubernetes/20042/3 "2018-10-12T12:18:02Z")
You might find inspiration from the Vagrant scripts discussed here: > [@Vagrant-based Ignition Development VM](http://forum.inductiveautomation.com/t/vagrant-based-ignition-development-vm/14873): > > Howdy folks. I thought I’d share something I’ve put together and have been using for spinning up Ignition development VMs on my workstation. It uses the [Vagrant](https://vagrantup.com) product (which utilizes an underlying VM provider, such as VirtualBox). I’ve setup the Vagrantfile (which is the initialization and definition file for it) to automatically install Java, MySQL, and Ignition. It can make for a pretty awesome way to quickly spool up an independent image. Also feel free to check out the Getting Start… --- _[View the full topic](https://forum.inductiveautomation.com/t/deploy-ignition-gateway-with-ansible-chef-puppet-powershell-dsc-or-in-kubernetes/20042)._