#helm (2019-12)

Archive: https://archive.sweetops.com/helm/

2019-12-29

Pierre Humberdroz
karuppiah7890/helm-schema-gen

Generate values yaml schema for your Helm 3 charts - karuppiah7890/helm-schema-gen

:--1:1

2019-12-09

Pierre Humberdroz

yea I can agree with this.. Well lets see if they will start providing some actual value to hub.helm.sh but let’s see.

Pierre Humberdroz

Anyways: How do you people share secrets between multiple templates in a helm chart without reconfiguring them in every single template? In this case I have a pre upgrade hook, two cronjobs, a queue worker and a webservice they all share the same config. Currently I am using

env: {{ .Files.Get "shared/env.yaml" | nindent 14 }}

but this does not allow me to use {{ .Values }} inside of shared/env.yaml

jedineeper

I thought the v1 charts in the stable/incubator repo were posted to hub.helm.sh anyway? Glad to see they are breaking up the monolith though.

Pierre Humberdroz

they are .. but you can only maintain your charts new ones are not added anymore.. I just saw an uprise of helm repos and was wondering since a couple of them did not follow the specification.

roth.andy

@jedineeper Helm Hub is just a marketplace of sorts. It’s a centralized place to advertise your (distributed) charts.

roth.andy

stable and incubator are 2 of many distributed chart repos now that are advertised on Helm Hub

Pierre Humberdroz

it is basically a npmjs.com without a centralised registry in the background.

jedineeper

yep

Pierre Humberdroz

While I think the mono repo was not the best idea a centralised package registry is. since I have seen a couple of repositories already changing the digest of a release

1
jedineeper

hopefully it’ll encourage more contributions as well, I can imagine a few people scared off by the concept of contributing to such a huge repo

Pierre Humberdroz

imho it is more complex now .. You have to maintain the repo .. which can be a little bit more tricky see: https://github.com/ruguodangshi/ruguodangshi.github.io/commit/37949e2b5e0ec0339181497ad5c0ab2aa4eb35a9

Update index.yaml · ruguodangshi/[email protected]

Contribute to ruguodangshi/ruguodangshi.github.io development by creating an account on GitHub.

Erik Osterman

I think helm-git should just be a first class method of accessing a registry

Update index.yaml · ruguodangshi/[email protected]

Contribute to ruguodangshi/ruguodangshi.github.io development by creating an account on GitHub.

roth.andy

that kind of stuff is done automatically. There are multiple tools out there

jedineeper

that’s just a bad git merge? it happens?

Pierre Humberdroz

right but it is on “production” i have to wait for the maintainer to fix it.

jedineeper

I don’t see how that changes from a central mono repo to an individual one per chart/maintainer?

Pierre Humberdroz

b/c the stable repo has a pipeline they check for linting errors etc.

Pierre Humberdroz

now it is up to each single repo maintainer to take care of these things.

2019-12-08

roth.andy

They finally figured out that the monolithic approach sucks. It takes weeks to get someone to look at PRs.

roth.andy

Helm 3 will support stable/incubator just fine

roth.andy

It just won’t add stable by default

roth.andy

Helm Hub is becoming the new “go-to” spot to find helm charts.

roth.andy

Discover & launch great Kubernetes-ready apps

2019-12-07

Pierre Humberdroz

anyone here know why stable / incubator helm repos are being depricated ? https://github.com/helm/charts#deprecation-timeline?

helm/charts

Curated applications for Kubernetes. Contribute to helm/charts development by creating an account on GitHub.

Steven

Sounds like it has to do with release of Helm v3 and API v2 (which that repo is not going to support)

Pierre Humberdroz

yea saw that as well.. but I actually liked that there is more or less one official helm repo similiar to how NPM acts as the central registry of node packages.

Steven

I’m guessing there is a new one somewhere for API v2

2019-12-04

    keyboard_arrow_up