You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running helm diff upgrade derp private/elasticsearch --allow-unreleased fails with
Error: chart "elasticsearch" matching not found in private index. (try 'helm repo update'). No chart version found for elasticsearch-
Usage:
diff upgrade [flags] [RELEASE] [CHART]
Examples:
helm diff upgrade my-release stable/postgresql --values values.yaml
Flags:
--allow-unreleased enables diffing of releases that are not yet deployed via Helm
-h, --help help for upgrade
--reset-values reset the values to the ones built into the chart and merge in any new values
--reuse-values reuse the last release's values and merge in any new values
--set stringArray set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
--suppress stringArray allows suppression of the values listed in the diff output
-q, --suppress-secrets suppress secrets in the output
-f, --values valueFiles specify values in a YAML file (can specify multiple) (default [])
--version string specify the exact chart version to use. If this is not specified, the latest version is used
Global Flags:
--no-color remove colors from the output
Error: plugin "diff" exited with error
The text was updated successfully, but these errors were encountered:
It looks like the root cause of the issue is only having pre-released versions and no released version. When helm-diff is searching it's searching only for released versions. The default behavior of helm search is to show pre-released versions.
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.
helm search private/elasticsearch
returns resultshelm diff upgrade derp private/elasticsearch --allow-unreleased
fails withThe text was updated successfully, but these errors were encountered: