I'd like to create an ephemeral DigitalOcean VM for testing out automation, Ansible code and various other things, and have it survive for exactly X number of hours, after which it is forcibly terminated without warning. Why would I want something like that? Simple - a truly ephemeral machine, which
I've now got a basic setup for deploying machines via Foreman in Proxmox, but it's a little click-intensive. What if I could create the machine in Foreman and it automatically created the machines in Proxmox? Enter foreman-fog-proxmox [https://github.com/theforeman/foreman_fog_proxmox]. Somewhat strangely named due to its
It's time to test out Foreman properly, and deploy a machine. Preparation Navigate to Hosts -> Provisioning Setup -> Operating Systems. Opening the Operating Systems panel in Foreman.We see there's already an operating system - Debian 11.3 - which was created/discovered because our host machine runs it.
I've joined Mastodon, apparently just before "the big announcement" (spoiler: Elon Musk buying Twitter). Nothing against Twitter! I'll still be there [https://twitter.com/gnomethrower] as @gnomethrower, but I'll also be on Mastodon via aus.social [https://aus.social] - you can find me on Mastodon as @firstname.lastname@example.org
Friday's shenanigans [https://raptorswithhats.com/cleaning-up-the-lab-time-for-self-hosted-dns/] started innocently enough - "I'll just rip out the DHCP server and run my own, and completely restructure the subnets, and..." as it started, soon led to a rabbithole. Where the last post left off, my "simple" DHCP solution was not working. This, as
I'm going to take the opportunity to wipe the Kubernetes cluster, which I think might be worth doing regularly anyways to prove it can be done. Ideally everything difficult-to-create or "big" should be stored in MooseFS. I went through the same procedure as before to create a K3s cluster: Unfortunately
Having learned a bit about Kubernetes, Rancher and K3S, I've decided I don't like how I setup Rancher originally. I'd like to set it up on a single-node k3s installation, with dns-01 based TLS certificates [https://github.com/rancher/rancher/issues/26850], at rancher.windowpa.in, without exposing it to
Now it's time to get Docker installed. There are plenty of ways to do this, but luckily Rancher provides a handy script that will install it in one line [https://rancher.com/docs/rancher/v2.6/en/installation/requirements/installing-docker/] . Install Docker... wings@k8s-1:~$ curl https://releases.rancher.com/install-docker/