Hey there, it’s me again with my cursed project. Last time is said “i basically reinvented Kubernetes”. But the voices won and I legit did.
Last time it was a cursed novelty. A random script made by some autistic dude with too much time on its hand.
Now it’s become its own project, with ecosystem and overpriced .io domain. For no reason other than : It’s cursed, but it works beautifully.
Every Kind is handled by its distinct code. Everything is pluggable, nothing is hardcoded. The next layer of hell is for someone else to write Docker Swarm extensions. Won’t be me.
I am, again, very sorry. Sorry for releasing this thing into the world as a complete, working, product.
And sorry for keeping spamming it. I will stop, i promises (the voices will never)
CallMeAl@piefed.zip 3 weeks ago
Sorry if this is a silly question, but what is the use case for this?
actionjbone@sh.itjust.works 3 weeks ago
Attempted satiation of the curse. Probably.
pokexpert30@jlai.lu 3 weeks ago
The real question is “why would anyone want to use this”. The answer “People are lazy and prefer using docker compose over k3s”.
I maintain several helmfiles repo, and people asked me “but where docker compose” . So there is your docker compose github.com/…/compose-deployment.md
dimeslime@lemmy.ca 3 weeks ago
I hate that you hate to write this, but good work doing it. I never understood why people perceive k3s as hard and then write pages of docker compose yaml instead. Admittedly my day job got me a CKA, but running k3s at home is barely a step up from docker compose.
CallMeAl@piefed.zip 3 weeks ago
Yeah, that tracks. It sounds like Type 1 Laziness: people who don’t want to do anything.
I sense you make this because you are Type 2 Lazy: Happy to learn and make 100 new things to avoid having to do a boring thing more than once. That’s something I can both appreciate and relate to.