Is it possible to install new packages with helm3 while helm2 is running in the cluster with tiller?
Any potential problems to packages installed with helm2?
I don't see a problem. Helm v2 talks to tiller, Helm v3 doesn't. Just basically keep:
Every package managed with Helm v2 using Helm v2
Every package managed with Helm v3 managed with Helm v3
Eventually, you will have to migrate everything to Helm v3. One thing is that if you install the latest Helm v3 the client executable will have the helm name. So you'd like to maybe rename the v2 client executable to helm2 and the v3 client executable to v3 to keep yourself from becoming confusing.
Related
I have a few services, for example one of them is Nexus - how do I got about updating it, while it was deployed using HELM chart? Should I just insert newer version into values.yaml or should i update to HELM chart which consists newer version of Nexus ?
I was thinking about either changing version for Nexus in values.yaml file that consists values for all HELM charts deployed or go with installing and deploying new HELM chart that consists newer version of Nexus
I have delved into the documentations of helm and still it is unclear what is the difference between the two. Here's what I understand so far
helm install -> install a helm chart
helm repo add -> add a repo from the internet
You can see Helm as a templating tool, which reads files from the templates directory, fills them with values from values.yaml, and deploys them into the Kubernetes cluster. These is all done by the helm install command. So, Helm install takes your chart and deploys it into the Kubernetes cluster.
One of the feature of Helm is helm package, which packages your chart into a single *.tgz file and then you can store it in the Helm registry. A lot of Helm charts are stored that way, you can look, e.g., into Artifact Hub. If you find a chart you'd like to install from the Helm registry, you can add that remote repo into your local Helm registry using helm repo add. Then, helm repo update downloads a Helm chart to your local registry. Downloading a repo just downloads the Helm chart into your local registry, but it does not deploy anything into the Kubernetes cluster. To do that, you need to use helm install.
I am trying to use the new Pulumi helm release (https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm/v3/release/) and now wondering what helm command is wrapped inside here? Is it using helm install underneath or helm upgrade --install?
Thanks
To start with, Helm release resource embeds Helm as a library in the provider.
As for your question, it depends on the state of the release. If it is a fresh install, it should behave similar to a helm install. If the resource is seen to be updating, it triggers the equivalent of helm upgrade.
when I recently tried to use Gitlab Auto DevOps to Kubernetes, my Gitlab GUI cannot see the Helm Tiller application.
Why?
One possible reason could be that you are using Helm 3. The Tiller doesn't exist on Helm 3.
The internal implementation of Helm 3 has changed considerably from Helm 2. The most apparent change is the removal of Tiller.
I have a private helm repo using apache, after migrating to helm3 I cannot install/search charts anymore.
Using helm v3
helm repo list
NAME URL
mas http://localhost:8080/charts/
helm search repo mas/devops-openshift
No results found
Using helm 2.*
helm search -r mas/devops-openshift
NAME CHART VERSION APP VERSION DESCRIPTION
mas/devops-openshift 7.0.0 Devops (OpenShift)
Same happens when using "helm install" command, it cannot find the charts.
I guess it could be something related to the helm repo index file. Maybe helmv3 is expecting a different structure? But same happen when generating index file from helmv3.
Thanks all for the answers but I've found the issue.
My repository were using development version of the charts so I had something like this 1.0.0-pre.dev (Semantic Versioning 2.0.0).
By default helm 3 does not look at non production charts.
You have to set the flag -devel. something like:
helm search repo mas/devops-openshift --devel
While migrating from helm 2 to helm 3 remove private repo and add it after migration, then run helm repo update to refresh repository file.
If the chart is available locally, run helm repo index <DIR> --url <your_repo_url> to create new index.yaml for this repository.
Running helm env will show you the directory where the repository.yamlis located so check if the file is generated correctly.