I spent all day yesterday trying to get #terraform to provision some #fedora CoreOS and #RHCOS VMs, but I think I'm going to give up on getting Terraform to generate the ignition files, and injecting them through oVirt. I think the oVirt Ignition support is still a bit buggy.
Instead I'm going to just use terraform to build some blank VMs, and PXE boot them and point them to the ignition scripts.
@mhamzahkhan apparently the way to go is either putting files into the right place or use the default config, maybe you can also use the kernel commandline.
The config spec doesn't mention any network section, which is quite poor :/
@sheogorath I know how to get the ignition file into CoreOS, but the problem I'm having is how to get it to work with terraform. For example, normally I could put a nic_configuration block in my terraform manifest with the static IP to assign, and that is converted to a cloud-init config file, but that doesn't work with ignition. There is an ignition plugin for terraform, but the network config bit isn't "nice" as the cloud-init counter part https://registry.terraform.io/providers/community-terraform-providers/ignition/latest/docs/data-sources/networkd_unit
@mhamzahkhan just out of interest, how do you handle backups in your clusters? It's currently one of my biggest concerns especially since I don't want to develop an own backup mechanism for each application in the cluster.
@sheogorath I'm using https://velero.io/ to backup K8S resources, which drops them into a S3 bucket. It's supposed to be able to backup persistent volume as well, but as I'm using TrueNAS for my persistent storage, I just create a ZFS snapshot of all the PVs, and send the snapshots to another machine.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!