K8s is better anyway, at least if you have the hardware for it. It's just slightly more complex to set up, but it sounds like you may already be over that hurdle.

If you want a new technology to have to resist dropping everything to play with, may I suggest CUE? Stands for Configure, Unify, Execute. If you're not familiar, it's a json superset that turns json-style data into networks of programmed relationships. Like if you want to send the same deployment to three different clusters, which have differently configured CD components, and (for example) you want to vary the databases or message queues you use based on the core microservice or what else has been deployed in the cluster, you can build out these relationships in CUE and merge them with another .cue module that defines how to render files for each destination cluster, automatically producing all yaml manifests that you would otherwise have to write by hand.

But absolutely, do what you were going to get done today. It's not a cool technology at all, there's really no need to keep thinking about it.