[HN Gopher] Helm-Compose - The Docker-compose like tool for K8s ...
___________________________________________________________________
Helm-Compose - The Docker-compose like tool for K8s development
Author : tuunit
Score : 40 points
Date : 2023-08-28 13:48 UTC (9 hours ago)
(HTM) web link (seacrew.github.io)
(TXT) w3m dump (seacrew.github.io)
| doctoboggan wrote:
| How does this differ from the "umbrella chart" pattern? I am able
| to install my whole stack with a single call to `helm install`. I
| will admit the dependency handling (subchart naming), and
| enabling/disabling is a little clunky but it does have everything
| needed.
| temptemptemp111 wrote:
| [dead]
| qntty wrote:
| Now we just need an orchestrator for all of our helm charts
| tuunit wrote:
| A docker-compose like tool for multi helm chart deployment
| handling. Primarily meant to be used for development, to be able
| to quickly deploy all dependent services and tools from within a
| single yaml file.
| don-code wrote:
| We've been using Helmsman (https://github.com/Praqma/helmsman)
| for the same use case. It supports some other creature comforts
| (automatic fetching of parameters from AWS SSM, chart ordering,
| etc.) and seems a bit more mature.
| aliencat wrote:
| Sharing a tool that I wrote to convert docker-compose file to
| kubernetes deployment YAML: https://docker2kube.app.enting.org/
|
| Hope it helps someone!
| gorkish wrote:
| how does this tool differ from kompose
| nlunbeck wrote:
| I'm all for the idea of using the compose spec for other configs
| -- its so elegant and its always nice to see everything in one
| place.
| mati365 wrote:
| Why not just use podman quadlet and systemd?
| seymon wrote:
| What are the benefits over using helmfile?
| https://helmfile.readthedocs.io/
| seabrookmx wrote:
| Or dependencies? https://helm.sh/docs/helm/helm_dependency/
| MuffinFlavored wrote:
| Or just kubectl apply a bunch of yaml files?
|
| or argocd / helm charts?
| SOLAR_FIELDS wrote:
| Those two are not like what grandparent is saying. Helm
| dependencies are native to helm like docker compose is
| native to docker. Kubectl apply a bunch of yaml files is
| like saying "run a bunch of docker files instead of docker
| compose" and argocd isn't the same realm, that is a hosted
| solution that requires a remote k8s cluster. I guess you
| could run it locally but you would be making commits to a
| git repo for iteration which would be slow annoying and
| painful. It solves an entirely different problem set to
| this one, it's not meant to solve local dev iteration
| loops.
|
| The comparison of helm compose and helm dependencies is
| much more apples to apples as they essentially solve the
| exact same problem in similar way
| MuffinFlavored wrote:
| Well said/good points. What's your preferred way to
| orchestrate deployments/configs/resources/workloads into
| k8s?
| SOLAR_FIELDS wrote:
| Into k8s? I do like Argo/flux as it's declarative. It
| works for most normal use cases. I would recommend that
| if you have a typical use case go with that first.
| Declarative and pull based deploys are quite powerful.
|
| For local/hybrid stuff there's things like Tilt that can
| be combined with a push based approach that is a simple
| helm install.
|
| If you have something fancy though you'll probably have
| to write some custom orchestration pushed based tooling.
| I would reach for a tool like Dagster, Prefect or
| Temporal for that kind of thing.
|
| You probably don't need that unless you're doing multi
| tenant multi cloud deployments though. Even terraform is
| a decent deploy tool if you don't want to go all in on
| helm/flux/argo etc
___________________________________________________________________
(page generated 2023-08-28 23:01 UTC)