I rebuilt a helm chart in Pkl

[MarkSRobinson]

If you've ever had to work with Helm you know it's the worst thing ever. Here's where Pkl comes in, it's actually a great replacement for the absolute quagmire that is YAML and Go Templates. As a learning experience, I wanted to see if I could get all the useful functionality of Helm in Pkl, and the answer is yes.

You can use the chart raw or extend it with user-friend Pkl syntax

amends "@chart/chart.pkl"

chart {
  services {
    default {
      metadata {
        labels {
          ["help"] ="I'm stuck in a yaml factory"
        }
      }
    }
  }
}

You can see the whole source code here - https://github.com/MarkSRobinson/nginx-pkl

[holzensp]

I like this! The one thing that stands out a little bit is that a chart.pkl has a property chart. It feels a little repetitive.

Is it worth trying to build a repository somewhere of ported common Helm charts, so that people know where to go when they find themselves in the same place as you?

[MarkSRobinson]

The one thing that stands out a little bit is that a chart.pkl has a property chart. It feels a little repetitive.

I agree. My goal with the naming was to establish something that was absolutely clear what was going on. So I picked clarity over brevity. I'm totally open to changing it if we can figure out a good way to do it.

Is it worth trying to build a repository somewhere of ported common Helm charts

In the short term, I think that would be a good idea. Long term, you want to avoid depending on a single source. There are a lot of large projects (eg Docker or NPM) where the ecosystem has a major burden due to having a single source.