[TUTORIAL] HOWTO : Wrapper Script to Use Fedora CoreOS Ignition with Proxmox cloud-init system for Docker workloads

For our Docker Swarm / Kubernetes container orchestration projects, we migrated from CoreOS distribution to Fedora CoreOS distribution.
can i ask, from your point of view, the advantages/disadvantages for swarm, kubernetes, okd and openshift ?

i setup in the next couple of days an OKD/openshift, which is based on fedora CoreOS. as i understood kub and swarm have some advantages and some disadvantages but okd has the best of both worlds (even they are very similar)

the swarm is defiantly the easiest setup, kub i dont know but as i read its amost as okd/openshift - 1 trillion steps
 
@Geco-iT .. thank you for making this wrapper!

I am curious as to why this section of code was needed:

1744566073218.png

Because of my lack of experience I do not understand why it takes, what appears to be, two ignition files to complete the VM creation.

I have looked at the operational diagram on the wiki but could you please explain the mechanics of what problem the reboot solves?

John
 
Last edited:
How do you restore a back to another machine ? It shouts that I needs the ign file.

Bash:
Fedora CoreOS: Generate other block based on template... [done]

Fedora CoreOS: Generate ignition config... [done]

kvm: -fw_cfg name=opt/com.coreos/config,file=/etc/pve/geco-pve/coreos/103.ign: can't load /etc/pve/geco-pve/coreos/103.ign: Failed to open file â/etc/pve/geco-pve/coreos/103.ignâ: No such file or directory

TASK ERROR: start failed: QEMU exited with code 1

What about live migrations ?