I'm trying to understand when and how --version option in helm upgrade works. In the docs it says:
--version string Specify the exact chart version to use. If this is not specified, the latest version is used
Lets say I have installed my app.
helm install my-app-rls my-app-1.0.0.tgz
Now, If I update my chart and create another package my-app-1.0.1.tgz I can upgrade by
helm upgrade my-app-rls my-app-1.0.1.tgz
Chart.yaml of my-app-1.0.1.tgz already contains a version. When does --version need to be used? What is the use case of it?
You use --version when pulling a chart from a chart repository. For example:
helm upgrade app chart_name \
--version 1.0.0 \
--repo https://chart.repo.example.com \
--install --values ./values.yml
This says to find and use version 1.0.0 found at the url defined by --repo
Related
I'm following the instructions to setup Dask on K8s Cluster. I'm on MacOS, have K8s running on Docker Desktop, kubectl version 1.22.5 and helm version 3.8.0. After adding the repository, downloading default configuration, installing helm chart using command
RELEASE=my-dask-gateway
NAMESPACE=dask-gateway
VERSION=0.9.0
helm upgrade --install \
--namespace $NAMESPACE \
--version $VERSION \
--values path/to/your/config.yaml \
$RELEASE \
dask/dask-gateway
generates following output/error
"dask" already exists with the same configuration, skipping
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "dmwm-bigdata" chart repository
...Successfully got an update from the "dask" chart repository
Update Complete. ⎈Happy Helming!⎈
Release "my-dask-gateway" does not exist. Installing it now.
Error: failed to install CRD crds/daskclusters.yaml: unable to recognize "": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
An older post suggests to either update the manifest or use older version of kubernetes. Does that mean dask is not compatible with recent versions of kubernetes?
Posting community wiki answer for better visibility:
This is fixed in the repo main. You could grab the CRDs from there, or wait for a release, which we are hoping to do soon. Otherwise, yes, you would need an older version of kubernetes for dask-gateway to work.
I want to upgrade helm version from 2 version to 3 version since I am facing "Could not find tiller" issue in while using "helm delete --purge " in JenkinsX.
So upgrade does not depend on tiller and makes my job easy. Please help me to resolve this.
jx step helm build
WARNING: No $CHART_REPOSITORY defined so using the default value of: http://jenkins-x-chartmuseum:8080
Adding missing Helm repo: storage.googleapis.com https://storage.googleapis.com/chartmuseum.jenkins-x.io
Successfully added Helm repository storage.googleapis.com.
Adding missing Helm repo: jenkins-x-chartmuseum http://jenkins-x-chartmuseum:8080
Successfully added Helm repository jenkins-x-chartmuseum.
WARNING: No $CHART_REPOSITORY defined so using the default value of: http://jenkins-x-chartmuseum:8080
Adding missing Helm repo: chartmuseum.jenkins-x.io http://chartmuseum.jenkins-x.io
Successfully added Helm repository chartmuseum.jenkins-x.io.
EXITCODE 0[Pipeline] sh
[preview] Running shell script
+ make delete
helm version
Client: &version.Version{SemVer:"v2.14.3", GitCommit:"0e7f3b6637f7af8fcfddb3d2941fcc7cbebb0085", GitTreeState:"clean"}
Error: could not find tiller
use the command choco upgrade kubernetes-helm
first install chococo/brew then use above for choco cmd or brew upgrade helm.
The latest Helm 3 won't need tiller pod.
After creating package in Helm , I am facing difficulty in setting customized chart name I tried below commands
> helm install --name example ./mychart --set service.type=NodePort
> helm install happy-panda stable/mariadb
Also, tried commands from helm man page
> helm install -help
> --name-template string specify template used to name the release
Before setting your custom release name you've to check your Helm version . Above commands mentioned in question didn't worked in below Helm version
root#docker-slave:/home/mec/src/vmmanager/docker/vmmanager_chart# helm version
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
For Helm 2 version.
helm install --name your_customized_name chart_name
Like , helm install --name vmchart vmmanager_chart
For Helm 3 version,
helm install [--namespace ] # Per-default you need
to provide a release name
For detailed description you can refer below link.
https://lzone.de/cheat-sheet/Helm
helm install myChart-0.0.1.tgz --output json results in Error: unknown flag: --output
I use helm version v2.14.3. According to the docs https://helm.sh/docs/helm/#helm-install this should work. Other flags seem to work fine. E.g. helm install myChart-0.0.1.tgz --namespace test-ns --set random.variable="debug" --name mychart
The documentation also states the schema helm install [CHART] [flags],
while its examples suggest the schema helm install [flags] [CHART] in my tests both seem to work but non accepts the output flag.
The output flag was added with commit a52d6de9e17fc4dda4928f0029362e9be075aa24 which is only present in the release-2.15 branch. The documentation is generated from master, so it already has the option, but your version does not yet.
Your current version doesn't support the --output flag, to use it upgrade your helm version to v2.15.0.
From: V2.15.0 Changelog
Introduced --output to helm repo list, helm search, and helm install
When I try to install a chart with helm:
helm install stable/nginx-ingress --name my-nginx
I get the error:
Error: unknown flag: --name
But I see the above command format in many documentations.
Version:
version.BuildInfo{Version:"v3.0.0-beta.3",
GitCommit:"5cb923eecbe80d1ad76399aee234717c11931d9a",
GitTreeState:"clean", GoVersion:"go1.12.9"}
Platform: Windows 10 64
What could be the reason?
In Helm v3, the release name is now mandatory as part of the commmand, see helm install --help:
Usage:
helm install [NAME] [CHART] [flags]
Your command should be:
helm install my-nginx stable/nginx-ingress
Furthermore, Helm will not auto-generate names for releases anymore. If you want the "old behavior", you can use the --generate-name flag. e.g:
helm install --generate-name stable/nginx-ingress
The v3 docs are available at https://v3.helm.sh/docs/, but as it is a beta version, the docs will not be accurate for a while. It's better to rely on the CLI --help, that is auto-generated by Go/Cobra.
The --name flag is no more in version 3.
It should be
helm install my-nginx stable/nginx-ingress
Syntax:
help install [name] [chart]
I don't think the helm3 does support "--name" argument. As per the helm3 doc, the command to install a package and expected output is given down below:
$ helm install happy-panda bitnami/wordpress
NAME: happy-panda
LAST DEPLOYED: Tue Jan 26 10:27:17 2021
NAMESPACE: default
STATUS: deployed
REVISION: 1
NOTES:
** Please be patient while the chart is being deployed **
Here "happy-panda" is the name of the release and "bitnami/wordpress" is the name of the chart. Also you can generate name for the release by using
--generate-name flag.
As others have mentioned, there is no --name flag in version 3 of Helm. Also, Helm v3 comes without stable repository setup by default. The best way to discover a chart by searching the Artifact Hub. Once you find the repo, which hosts the chart you are looking for, you need to add the repo as:
helm repo add nginx-stable https://helm.nginx.com/stable
And then you can install chart
helm install my-nginx nginx-stable/nginx-ingress
As name was made compulsory in helm3,
if we do helm repo --help,
help install [name] [chart]
If the chart was not present,
use helm repo add <name> <url>
then use helm install