Understanding Helm Chart Installation and Management
Viewing Release History
To see all the revisions of a release, use the helm history command. The general syntax is:
helm history [RELEASE_NAME] [flags]
To apply this to our example:
helm history my-wordpress
The history table contains the following columns:
| COLUMN | DESCRIPTION |
|---|---|
| REVISION | The revision number of the release. |
| UPDATED | The date and time when the revision was created. |
| STATUS | The status of the release (e.g., deployed (the current successful revision), superseded (not deleted, not failed, but no longer the current), failed, etc.). |
| CHART | The name and version of the chart used for this revision. |
| APP VERSION | The version of the application deployed by this release. |
Since the beginning of this section, we have been using the bitnami/wordpress chart, and we have made multiple upgrades. However, by default, Helm only keeps the last 10 revisions of a release, even if more upgrades were made. If you want to keep more revisions, you have two options:
- Using the environment variable
HELM_MAX_HISTORY, which is set by default to10. You can change it to any value you want.
# Set the maximum number of revisions to keep
export HELM_MAX_HISTORY=[NUMBER_OF_REVISIONS]
# Install or upgrade the chart
helm upgrade -i [Helm in Practice
Designing, Deploying, and Operating Kubernetes Applications at ScaleEnroll now to unlock current content and receive all future updates for free. Your purchase supports the author and fuels the creation of more exciting content. Act fast, as the price will rise as the course nears completion!
Hurry! This limited time offer ends in:
To redeem this offer, copy the coupon code below and apply it at checkout: