Helm Charts for internal microservices

[dav...@billymob.com]

Hello!

I'm new to k8s and Helm in particular and first of all, I would like to thanks Helm developers, it's really a nice software!

I'm planning to deploy several (tenths) different microservices in a k8s cluster via Helm and i was wondering what's the "best-practice" approach at writing charts in this case. I have two options in mind:
1) create a chart for every microservice
2) create a generic chart customized at install time (basically the env vars and the base image)

Instinctively, I'd go with the second options, as we are talking about templates here and it seems absurd to me to write (copypaste?) N charts that are going to be very similar.
The microservices are customized at run time via environment variables and so one possible question with approach #2 is: how to properly separate values for every MS? One `values.yaml` per microservice?

Thank you very much

--
Davide

[Kris Nova]

I always create a library of small charts and then can optionally bundle them together with a new big chart that is made of the small charts in requirements.yaml 

But that’s just me 😍

Kris Nova

(415)-619-0607

Sent from my iPhone

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-apps" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-...@googlegroups.com.
To post to this group, send email to kubernete...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-apps/8ec5f062-a4e9-430f-81f8-34af91b99acf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.