Programming

17406 readers

94 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

[email protected]

Mistletoe Package Manager (WIP) -- Run WASM, Get Kubernetes YAML (github.com)

submitted 10 months ago* (last edited 10 months ago) by [email protected] to c/[email protected]

7 comments fedilink hide all child comments

Hey all! I'm looking for some input on an idea I've been kicking around for a while and just started hacking on the past few days. I call it "Mistletoe", and it's yet another Kubernetes package manager, like Helm. I'm writing it due to some frustrations I've had with Helm in the past not supporting more complex cases.

I'm still in the early stages, so only the most trivial parts work, which is why I wanted feedback before I really put the gas on. The cliff's notes are that it's a Kubernetes package manager where the packages are WebAssembly modules that take input YAML strings and output Kubernetes resource YAML strings. It turns out that writing packages for it is pretty braindead simple, so I have high hopes, but please feel free to give me a reality check if I'm spouting nonsense.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 10 months ago (1 children)

So Helm never fell short for me as an end user. As far as that goes, it's near-perfect.

Where it does fall short is as a package writer. A package in Helm is just Kubernetes YAML that's templated in Golang templates. As such, it gets very hard to any logic beyond the most basic, and projects that get larger get very unwieldy.

Hmm, what's your idea for the OCI image format, e.g., how would it work? That might be worth looking into, too.

[–] [email protected] 2 points 10 months ago

OCI allows you to package arbitrary content in a docker image. In this case it would be a collection of k8s yaml files. Two main benefits of this approach are:

Your gitops tool only needs image registry access, not git access
The OCI image contains the final yaml. Your CI pipeline is responsible for generating the image.

Flux already supports this and I other tools to follow.