Everything You Need to Know to Start Using Helm
94%
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 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 2 options:
- Using the environment variable
HELM_MAX_HISTORYwhich 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 [Cloud-Native Microservices With Kubernetes - 2nd Edition
A Comprehensive Guide to Building, Scaling, Deploying, Observing, and Managing Highly-Available Microservices in KubernetesEnroll now to unlock all content and receive all future updates for free.