Helm3 upgrade command error
See original GitHub issueI’ve intalled yugabyte db (https://docs.yugabyte.com/latest/deploy/kubernetes/single-zone/oss/helm-chart/) and now I’m trying to execute next command
microk8s helm upgrade --set replicas.tserver=5 yb-demo ./yugabyte
but I got an error Error: path “./yugabyte” not found
Issue Analytics
- State:
- Created 3 years ago
- Comments:8
Top Results From Across the Web
Helm3 upgrade command error · Issue #1846 - GitHub
I've intalled yugabyte db (https://docs.yugabyte.com/latest/deploy/kubernetes/single-zone/oss/helm-chart/) and now I'm trying to execute ...
Read more >How to fix Helm's "Upgrade Failed: has no deployed releases ...
When you are using the command helm upgrade --install , you may think that it will always work and rollback in case of...
Read more >How to fix “Helm Upgrade Error: has no deployed releases ...
The command above will update the STATUS filed of the deployment history data (stored in configMap) and set it to DEPLOYED .
Read more >How to Fix helm "has no deployed releases" Error - phoenixNAP
As of Helm 2.7.1, running the helm upgrade [release-name] [chart] command on a previously failed release produces the following error:
Read more >How to debug helm upgrade failed with message: spec - JFrog
In some cases, the error message will give the filed that's ... Check if the chart version is changed with the upgrade command...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think it’s not related to microk8s and it makes more sense to open an issue @ yugabyte: https://github.com/yugabyte/yugabyte-db/issues
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.