3 ms·
> this isn’t what Kubernetes is really for. i'm guessing that writing dyson in Nim is a tacit acknowledgement of that: if this were something geared toward pr
by auvrw 7y ago
> this isn’t what Kubernetes is really for.
i'm guessing that writing dyson in Nim is a tacit acknowledgement of that: if this were something geared toward production ecosystems, it would be in golang like kubernetes? although there is the helm luafication, so perhaps dyson is part of a fringe of non-golang k8s auxilliaries.
another way to implement this is with a 'static CMS' where there are still static pages except built into a situated deploy. the 'cultish' (cultic? anyway) aspect of k8s appears to be to phrase all the things in terms of k8s constructs rather than using k8s constructs as a foundation and abstracting out.
i learned about 'rollout' from the CI portion of this post, although initial attempts to search for a comprehensible description of it fail.
- xena 7y agoHonestly dyson is just something I wrote for myself to see how difficult it would be to write. I don't expect anyone else to use it. The tool is also a punny name, because you'd need to terraform a dyson sphere before you(r apps) can live in it. I just wanted something with easy templating syntax like this: https://github.com/Xe/within-terraform/blob/master/dyson/src/dysonPkg/deployment_with_ingress.yaml https://github.com/Xe/within-terraform/blob/master/dyson/src... The fact that cligen (https://github.com/c-blake/cligen https://github.com/c-blake/cligen) exists too makes it super easy for me to define subcommands of the thing: https://github.com/Xe/within-terraform/blob/master/dyson/src/dyson.nim#L127-L128 https://github.com/Xe/within-terraform/blob/master/dyson/src...