Oh I get it now, the other k8s cluster IS the therapist. That's funny. And not at all an accurate description of my life. Anyway, I have a cronjob—I mean appointment—to get to.
Uli
Unfortunately, that is not how therapy works.
I really do love it. But to be fair, I should probably also be in therapy.
K3s is a Rancher-based lightweight Kubernetes, more geared toward deploying on resource-constrained environments like ARM devices.
So, let's modify CoreDNS and update the cluster version then. Don't want to? Interesting.
Gets hated on just because it's complex. You and I are the same, Military Industrial Complex. You know, aside from all of the killing, but I'm not about to stop now.
If it's a Western-style book, yes that is so! And by ascending numerical order, I mean number 1 on the left side. When you put English language Book One on the shelf spine facing out, its cover gets turned to the right side (unless it is upside-down!), touching back cover of Book Two. But Manga will have front cover of Book One snug against the left side of the bookshelf, and its back cover touches front cover of Book Two. You should go try it with your books, just to see it happen. Feels good.
I imagine there being a commercial where some old man (let's say 40 or so) says, "You kids need to stop grinding your skateboards on these rails or I'll call the cops."
And one of them says, "What skateboards, gramps?"
And he looks around and his jaw drops and everyone does secret handshakes and laughs except for the old man who scowls and shouts something irate that gets drowned out by cool boombox music.
Rhode Istan
I like that when I line them up on a shelf in numerical order, all the pages are lined up in order as well, with the end of one book touching the start of the next.
A tragedy on another scale.
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.