Output of helm version:
version.BuildInfo{Version:»v3.5.3″, GitCommit:»041ce5a2c17a58be0fcd5f5e16fb3e7e95fea622″, GitTreeState:»dirty», GoVersion:»go1.15.8″}
Output of kubectl version:
Client Version: version.Info{Major:»1″, Minor:»20″, GitVersion:»v1.20.4″, GitCommit:»e87da0bd6e03ec3fea7933c4b5263d151aafd07c», GitTreeState:»clean», BuildDate:»2021-02-18T16:12:00Z», GoVersion:»go1.15.8″, Compiler:»gc», Platform:»linux/amd64″}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
AKS
When running the following command, I get the following error:
`helm upgrade twistlock /tmp/hc-exports-XXXXlNHbbK/export-twistlock/twistlock-defender/ —install —namespace ***** —set cluster=***** —set admission_cert=******* —set admission_key=******* —set client_cert=******* —set client_key=******* —set ca_cert=******* —set service_parameter=*******
Error: «helm upgrade» requires 2 arguments`
The two arguments are present. This same command works elsewhere. I’m not sure why this is failing here.
I am getting an error in my kubernetes cluster while upgrading my install of kamus
$ helm --debug upgrade --install soluto/kamus
[debug] Created tunnel using local port: '64252'
[debug] SERVER: "127.0.0.1:64252"
Error: This command needs 2 arguments: release name, chart path
Using helm version 2.13.1
This error is also known to be cause by not correctly using --set correctly or as intended.
As an example when upgrading my ingress-nginx/ingress-nginx installing as such:
--set "controller.service.annotations.service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path"=/healthz,"controller.service.annotations.service.beta.kubernetes.io/azure-dns-label-name"=$DNS_LABEL
This caused the same error as listed above.
When I removed the quotations it worked as intended.
--set controller.service.annotations.service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path=/healthz,controller.service.annotations.service.beta.kubernetes.io/azure-dns-label-name=$DNS_LABEL
The error in this case had nothing to do with not correctly setting a release name and or chart. More explanation of —set issues and solutions are below.
Содержание
- helm error «Error: This command needs 2 arguments: release name, chart path»
- 6 Answers 6
- helm error «Error: This command needs 2 arguments: release name, chart path»
- 6 Answers 6
- Error: This command needs 2 arguments: release name, chart path in helm upgrade command #5209
- Comments
- Output of helm version : «v2.12.2»
- Output of kubectl version : Client Version: version.Info Server Version: version.Info
- Incorrect error message «This command needs 2 arguments: release name, chart path» #6058
- Comments
- Ошибка обновления helm «Ошибка: этой команде требуется 2 аргумента: имя выпуска, путь к диаграмме»
helm error «Error: This command needs 2 arguments: release name, chart path»
I am getting an error in my kubernetes cluster while upgrading my install of kamus
Using helm version 2.13.1
This error is also known to be cause by not correctly using —set correctly or as intended.
As an example when upgrading my ingress-nginx/ingress-nginx installing as such:
This caused the same error as listed above.
When I removed the quotations it worked as intended.
The error in this case had nothing to do with not correctly setting a release name and or chart. More explanation of —set issues and solutions are below.
6 Answers 6
Helm upgrade command requires release name and chart path. In your case, you missed release name.
helm —debug upgrade —install kamus soluto/kamus should work.
I encountered this error when I do —set key value instead of —set key=value . The cause was as stupid as the error message.
Helm upgrade requires both a release name and the chart it references. From the documentation:
Usage: helm upgrade [RELEASE] [CHART] [flags]
According to the documentation for the —install flag, the command you referenced seems like it should work, but it may be due to differing Helm versions.
helm install soluto/kamus works for me.
I ran into this error (too) many times.
The first thing that should come to your mind is typos in the command.
- If you’re passing location of values.yaml with -f
you should make sure its in the relevant order related to flags that were passed.
Run helm help upgrade or helm help install to get more information about each commands.
Источник
helm error «Error: This command needs 2 arguments: release name, chart path»
I am getting an error in my kubernetes cluster while upgrading my install of kamus
Using helm version 2.13.1
This error is also known to be cause by not correctly using —set correctly or as intended.
As an example when upgrading my ingress-nginx/ingress-nginx installing as such:
This caused the same error as listed above.
When I removed the quotations it worked as intended.
The error in this case had nothing to do with not correctly setting a release name and or chart. More explanation of —set issues and solutions are below.
6 Answers 6
Helm upgrade command requires release name and chart path. In your case, you missed release name.
helm —debug upgrade —install kamus soluto/kamus should work.
I encountered this error when I do —set key value instead of —set key=value . The cause was as stupid as the error message.
Helm upgrade requires both a release name and the chart it references. From the documentation:
Usage: helm upgrade [RELEASE] [CHART] [flags]
According to the documentation for the —install flag, the command you referenced seems like it should work, but it may be due to differing Helm versions.
helm install soluto/kamus works for me.
I ran into this error (too) many times.
The first thing that should come to your mind is typos in the command.
- If you’re passing location of values.yaml with -f
you should make sure its in the relevant order related to flags that were passed.
Run helm help upgrade or helm help install to get more information about each commands.
Источник
Error: This command needs 2 arguments: release name, chart path in helm upgrade command #5209
Output of helm version : «v2.12.2»
Output of kubectl version : Client Version: version.Info Server Version: version.Info
Cloud Provider/Platform (AKS, GKE, Minikube etc.): AWS
Error: This command needs 2 arguments: release name, chart path
i am running kubernetes and trying to create a test environment and for this changing the command helm upgrade , am getting above error
The text was updated successfully, but these errors were encountered:
helm upgrade ./jenkins-helm/»’ + serviceName + »’ -f values-test.yaml »’ + serviceName + »’-test —install —namespace »’ + testClusterNamespace + »’ ./jenkins-helm/»’ + serviceName + »’ —set image.repository=»5339606688788.dkr.ecr.us-east-1.amazonaws.com/con/$SERVICE_NAME» —set image.tag=$BUILD_NUMBER-$COMMIT_ID —set tracing.enabled=true
usng above command i got that error
Hard to understand the upgrade command above.
If you have installed and when you want to upgrade , set whatever value you want to change and the rest of the values will remain the same from previous. Example where you set the service type: helm upgrade —set service.type=NodePort
If you could explain more what you are trying to do that might help.
we are deploying an application, and we need it to do for dev and test environments, and am doing it for test environment now. in this process, the command which i posted was the last one to deploy to eks cluster, but its getting failed with the error mentioned.
Источник
Incorrect error message «This command needs 2 arguments: release name, chart path» #6058
HELM version: 2.14.1
Cloud Provider: AZURE DEVOPS
I have two helm upgrade commands:
this one is failing with error message saying «This command needs 2 arguments: release name, chart path»
[command]C:hostedtoolcachewindowshelm2.14.1x64windows-amd64helm.exe upgrade —namespace ci —install —recreate-pods —reset-values —force —set image.repository=acmedevacr.azurecr.io/build/myacmeapp,image.tag=0.4.0-alpha0939.8,deploymentTag=0.4.0-alpha0939.8,appVersion= 0.4.0-alpha0939.8,configVersion=0.4.0-alpha0925 -f d:ar1a/_acmedevops/Deployment/helm/app-chart/dev-env-common.values.yaml -f d:ar1a/_acmedevops/Deployment/helm/app-chart/myacmeapp.ci.values.yaml —debug ci-myacmeapp d:ar1a_acmedevopsDeploymenthelmapp-chart
this one works
[command]C:hostedtoolcachewindowshelm2.11.0x64windows-amd64helm.exe upgrade —namespace es-qa-ci —install —recreate-pods —reset-values —force —set image.repository=acmedevacr.azurecr.io/build/acme.identity.server,image.tag=0.3.1.1,deploymentTag=0.3.1.1,appVersion=0.3.1,configVersion=0.4.0 —wait -f d:ar1a/_acmedevops/Deployment/helm/app-chart/dev-env-common.values.yaml -f d:ar1a/_acmedevops/Deployment/helm/app-chart/acme.identity.server.es-qa-ci.values.yaml —debug es-qa-ci-acme.identity.server d:ar1a_acmedevopsDeploymenthelmapp-chart
I don’t see any differences beetween parameters — probably this error message is related to something else!!
The text was updated successfully, but these errors were encountered:
Источник
Ошибка обновления helm «Ошибка: этой команде требуется 2 аргумента: имя выпуска, путь к диаграмме»
Я получаю сообщение об ошибке в своем кластере kubernetes при установке камус
Использование шлема версии 2.13.1
Для обновления Helm требуется как название выпуска, так и диаграмма, на которую он ссылается. Из документации:
Usage: helm upgrade [RELEASE] [CHART] [flags]
Согласно документация для флага —install , команда, на которую вы ссылаетесь, кажется, должна работать, но это может быть связано с разными версиями Helm.
helm install soluto/kamus работает для меня.
Для команды Обновление шлема требуется имя выпуска и путь к диаграмме. В вашем случае вы пропустили имя выпуска.
helm —debug upgrade —install kamus soluto/kamus должно работать.
Источник
I am getting an error in my kubernetes cluster while installing kamus
$ brew install kubernetes-helm
$ helm init
$HELM_HOME has been configured at /Users/user/.helm.
Warning: Tiller is already installed in the cluster.
(Use --client-only to suppress this message, or --upgrade to upgrade Tiller to the current version.)
Happy Helming!
$ helm repo add soluto https://charts.soluto.io
"soluto" has been added to your repositories
$ helm --debug upgrade --install soluto/kamus
[debug] Created tunnel using local port: '64252'
[debug] SERVER: "127.0.0.1:64252"
Error: This command needs 2 arguments: release name, chart path
Using helm version 2.13.1
Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
I tried using the idea at https://stackguides.com/questions/54190837/helm-install-in-kuberneres-error-this-command-needs-2-arguments-release-name but it didn’t help. Can you spot what I am doing wrong? Thank you.
5 Answers
Helm upgrade command requires release name and chart path. In your case, you missed release name.
helm upgrade [RELEASE] [CHART] [flags]
helm --debug upgrade --install kamus soluto/kamus should work.
Helm upgrade requires both a release name and the chart it references. From the documentation:
Usage:
helm upgrade [RELEASE] [CHART] [flags]
According to the documentation for the --install flag, the command you referenced seems like it should work, but it may be due to differing Helm versions.
helm install soluto/kamus works for me.
May be this detailed information will be helpful for someone new to this !
1. My helm files are here (I made changes in values.yaml to upgrade):
controlplane $ pwd
/root/existing2helm
controlplane $ ls
Chart.yaml charts templates values.yaml
2. Listing current releases
controlplane $ helm list
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
newdeploybyhelm default 2 2021-02-01 00:39:11.596751325 +0000 UTC deployed existing2helm-0.1.0 1.16.0
3. Finally executing the upgrade command
controlplane $ helm upgrade newdeploybyhelm /root/existing2helm
Release "newdeploybyhelm" has been upgraded. Happy Helming!
NAME: newdeploybyhelm
LAST DEPLOYED: Mon Feb 1 00:48:30 2021
NAMESPACE: default
STATUS: deployed
I ran into this error (too) many times.
The first thing that should come to your mind is typos in the command.
For example:
- If you’re passing location of
values.yamlwith-f <path-to-values.yaml>you should make sure its in the relevant order related to flags that were passed. - If you’re passing inline values with the
--setflag you should make sure that there are no whitespace in the variable assignment like in this case:--set someVar= $SomeValue.
Run helm help upgrade or helm help install to get more information about each commands.
I encountered this error when I do --set key value instead of --set key=value. The cause was as stupid as the error message.
ткая ошибка
Error: «helm upgrade» requires 2 arguments
Usage: helm upgrade [RELEASE] [CHART] [flags]
Делаю все по инструкции
helm upgrade -n qa nginx-ingress bitnami/nginx-ingress-controller —version 0.43.0
—set service.type=NodePort
—set kind=Deployment
—set config={use-forwarded-headers: «true»}
—set metrics.enabled=true
—set metrics.serviceMonitor.enabled=true
—set metrics.service.annotations={prometheus.io/scrape: «true», prometheus.io/port: «9090»}
—set metrics.prometheusRule.enabled=true —dry-run
что я делаю не так?
russian
software
kubernetes
4
ответов
всегда улыбает когда тулза тебе черным по белому пишет в каком формате и что ждет , а ты как неандерталец тыкаешься во все мануалы и чаты че ж оно не работает то уЪуъуъуъ!
Название релиза не указал
Lucky SB
Название релиза не указал
helm upgrade nginx-ingress bitnami/nginx-ingress-controller —namespace qa —version 0.43.0
Похожие вопросы
Я получаю сообщение об ошибке в своем кластере kubernetes при установке камус
$ brew install kubernetes-helm
$ helm init
$HELM_HOME has been configured at /Users/user/.helm.
Warning: Tiller is already installed in the cluster.
(Use --client-only to suppress this message, or --upgrade to upgrade Tiller to the current version.)
Happy Helming!
$ helm repo add soluto https://charts.soluto.io
"soluto" has been added to your repositories
$ helm --debug upgrade --install soluto/kamus
[debug] Created tunnel using local port: '64252'
[debug] SERVER: "127.0.0.1:64252"
Error: This command needs 2 arguments: release name, chart path
Использование шлема версии 2.13.1
Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Я пытался использовать эту идею на https://stackoverflow.com/questions/54190837/helm-install-in-kuberneres-error-this-command-needs-2-arguments-release-name, но это не помогло. Можете ли вы определить, что я делаю неправильно? Спасибо.
Перейти к ответу
Данный вопрос помечен как решенный
Ответы
5
Для обновления Helm требуется как название выпуска, так и диаграмма, на которую он ссылается. Из документации:
Usage:
helm upgrade [RELEASE] [CHART] [flags]
Согласно документация для флага —install, команда, на которую вы ссылаетесь, кажется, должна работать, но это может быть связано с разными версиями Helm.
Helm install soluto/kamus работает для меня.
Для команды Обновление шлема требуется имя выпуска и путь к диаграмме. В вашем случае вы пропустили имя выпуска.
helm upgrade [RELEASE] [CHART] [flags]
Helm —debug upgrade —install kamus soluto/kamus должно работать.
Может быть, эта подробная информация будет полезна для новичков!
1. Мои файлы хелма здесь (я внес изменения в values.yaml для обновления):
controlplane $ pwd
/root/existing2helm
controlplane $ ls
Chart.yaml charts templates values.yaml
2. Список текущих выпусков
controlplane $ helm list
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
newdeploybyhelm default 2 2021-02-01 00:39:11.596751325 +0000 UTC deployed existing2helm-0.1.0 1.16.0
3. Наконец, выполнение команды обновления
controlplane $ helm upgrade newdeploybyhelm /root/existing2helm
Release "newdeploybyhelm" has been upgraded. Happy Helming!
NAME: newdeploybyhelm
LAST DEPLOYED: Mon Feb 1 00:48:30 2021
NAMESPACE: default
STATUS: deployed
Я сталкивался с этой ошибкой (тоже) много раз.
Первое, что должно прийти вам в голову, это опечатки в команде.
Например:
- Если вы передаете местоположение
values.yamlс-f <path-to-values.yaml>, вы должны убедиться, что оно находится в соответствующем порядке, связанном с переданными флагами. - Если вы передаете встроенные значения с флагом
--set, вы должны убедиться, что в назначении переменной нет пробелов, как в этом случае:--set someVar= $SomeValue.
Запустите helm help upgrade или helm help install, чтобы получить больше информации о каждой команде.
Я столкнулся с этой ошибкой, когда делаю —set key value вместо —set key=value. Причина была такой же глупой, как и сообщение об ошибке.