Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add note about version flag for helm upgrade #320

Merged
merged 1 commit into from
Nov 26, 2019
Merged

Add note about version flag for helm upgrade #320

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion deploy/docs/Upgrading_with_Helm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,8 @@ If desired, there are two ways to pass configuration data:

- If there exists `--set/--set-file/--set-string/--values/-f` , the `--reset-values` flag will be used by default.

- If you are using an [Alpha Release](./Alpha_Release_Guide.md) you will need to append `--version=X.X.X-alpha` to your `helm upgrade` command to avoid changing the version of the Helm chart installed. Use `helm ls` to find your current Helm chart version.

### Example to Upgrade without any arguments:

```bash
Expand All @@ -28,7 +30,7 @@ In the above command, since no arguments were specified, the `--reuse-values` fl
### Example to Upgrade using the `--version` flag:

```bash
helm upgrade collection sumologic/sumologic --reuse-values --version=<RELEASE-VERSION> -f config.yaml
helm upgrade collection sumologic/sumologic --reuse-values --version=<RELEASE-VERSION> -f values.yaml
```

### Example to upgrade using the `--set` flag:
Expand Down