techno-tim / k3s-ansible

The easiest way to bootstrap a self-hosted High Availability Kubernetes cluster. A fully automated HA k3s etcd install with kube-vip, MetalLB, and more. Build. Destroy. Repeat.
https://technotim.live/posts/k3s-etcd-ansible/
Apache License 2.0
2.41k stars 1.05k forks source link

Self hosted runners #136

Closed timothystewart6 closed 1 year ago

timothystewart6 commented 2 years ago

Proposed Changes

Checklist

timothystewart6 commented 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.