I’m wondering on how would be a migration process to helm3 ?
The Kubernetes Package Manager. Contribute to helm/helm development by creating an account on GitHub.
@hlesta have you seen our
we have archived the
helm-chart-scaffolding and instead moved development to
The “Cloud Posse” Distribution of Kubernetes Applications - cloudposse/charts
You can use the monochart as-is for 99% of webapps
or fork it and customize to your needs
the idea is to provide a common interface for deploying the most common kinds of apps
Hello @Erik Osterman (Cloud Posse). I’ll check this repo, it seems worthy to first sight thanks
Hello there, anybody knows an helm skaffolding with good practices applied?
I’m getting started with helm and I need a little bit of help to achieve that.
I found this repo https://github.com/cloudposse/helm-chart-scaffolding
Moved to https://github.com/cloudposse/charts/tree/master/incubator/monochart - cloudposse/helm-chart-scaffolding
It seems great place to get started
Do you have any recommendations?
Has anyone come across an Istio Helm plugin? I was thinking this would be part of Helm 3 discussion but haven’t seen anything of the sort.
what would the helm plugin do?
In my mind it would allow me to use the Istio config like a template and it would supply Values to the config just like a Kubernetes manifest so I could treat this like an ingress resource.
How is Cloud Posse working with Istio any examples maybe I am thinking about this all wrong.
so, once you have istio installed, you have all the CRDs necessary to work with it
then in your helm charts, you add the resources
@zadkiel we opened this issue https://github.com/aslafy-z/helm-git/issues/9
The plugin fails when ref refers to an annotated tag, which is the usual case for GitHub release tags. For example: helm repo add istio git+https://github.com/istio/[email protected]/kubernetes/helm?re…
@Jeremy (Cloud Posse) share a bit of info on what is going on