Closed timothystewart6 closed 1 year ago
After days of trying to get a Vagrant pipeline running in Kubernetes using GitHub actions, I am finally abandoning this work. Not because itβs too hard, but because the container needs more access than I want to give to something running in Kubernetes.
VirtualBox would kind of work, but it requires host network access to configure the virtual nics, along with VirtualBox dkms which at that point I fell like using Vagrant with a VM provider or a full VM is better for this type of work. If I ever feel up to it, I will create a dedicated VM for this or write Vagrant provider config for Proxmox.
Proposed Changes
Checklist
site.yml
playbookreset.yml
playbook