Difference between revisions of "Helm"
From Christoph's Personal Wiki
(→Miscellaneousg examples) |
|||
| Line 30: | Line 30: | ||
*<tt>version</tt> — print the client/server version information | *<tt>version</tt> — print the client/server version information | ||
| − | == | + | ==Miscellaneous examples== |
* Install a Helm Chart with: | * Install a Helm Chart with: | ||
| Line 41: | Line 41: | ||
$ helm delete --purge ${MY_CHART_NAME} | $ helm delete --purge ${MY_CHART_NAME} | ||
</pre> | </pre> | ||
| + | |||
| + | ==Deployment order== | ||
| + | |||
| + | Helm collects all of the resources in a given Chart and its dependencies, groups them by resource type, and then installs them in the following order (as shown [https://github.com/helm/helm/blob/release-2.10/pkg/tiller/kind_sorter.go#L29 here]): | ||
| + | |||
| + | # Namespace | ||
| + | # ResourceQuota | ||
| + | # LimitRange | ||
| + | # PodSecurityPolicy | ||
| + | # Secret | ||
| + | # ConfigMap | ||
| + | # StorageClass | ||
| + | # PersistentVolume | ||
| + | # PersistentVolumeClaim | ||
| + | # ServiceAccount | ||
| + | # CustomResourceDefinition | ||
| + | # ClusterRole | ||
| + | # ClusterRoleBinding | ||
| + | # Role | ||
| + | # RoleBinding | ||
| + | # Service | ||
| + | # DaemonSet | ||
| + | # Pod | ||
| + | # ReplicationController | ||
| + | # ReplicaSet | ||
| + | # Deployment | ||
| + | # StatefulSet | ||
| + | # Job | ||
| + | # CronJob | ||
| + | # Ingress | ||
| + | # APIService | ||
| + | |||
| + | During uninstallation of a release, the order is reversed (as shown [https://github.com/helm/helm/blob/release-2.10/pkg/tiller/kind_sorter.go#L61 here]). | ||
==External links== | ==External links== | ||
Revision as of 21:02, 27 February 2020
Helm is a package manager for Kubernetes.
Commands
- completion — generate autocompletions script for the specified shell (bash or zsh)
- create — create a new chart with the given name
- delete — given a release name, delete the release from Kubernetes
- dependency — manage a chart's dependencies
- fetch — download a chart from a repository and (optionally) unpack it in local directory
- get — download a named release
- help — help about any command
- history — fetch release history
- home — displays the location of HELM_HOME
- init — initialize Helm on both client and server
- inspect — inspect a chart
- install — install a chart archive
- lint — examines a chart for possible issues
- list — list releases
- package — package a chart directory into a chart archive
- plugin — add, list, or remove Helm plugins
- repo — add, list, remove, update, and index chart repositories
- reset — uninstalls Tiller from a cluster
- rollback — roll back a release to a previous revision
- search — search for a keyword in charts
- serve — start a local http web server
- status — displays the status of the named release
- template — locally render templates
- test — test a release
- upgrade — upgrade a release
- verify — verify that a chart at the given path has been signed and is valid
- version — print the client/server version information
Miscellaneous examples
- Install a Helm Chart with:
$ helm upgrade --install ${MY_CHART_NAME} -f values.yaml --namespace=default .
- Delete this Helm Chart (i.e., destroy what it created) with:
$ helm delete --purge ${MY_CHART_NAME}
Deployment order
Helm collects all of the resources in a given Chart and its dependencies, groups them by resource type, and then installs them in the following order (as shown here):
- Namespace
- ResourceQuota
- LimitRange
- PodSecurityPolicy
- Secret
- ConfigMap
- StorageClass
- PersistentVolume
- PersistentVolumeClaim
- ServiceAccount
- CustomResourceDefinition
- ClusterRole
- ClusterRoleBinding
- Role
- RoleBinding
- Service
- DaemonSet
- Pod
- ReplicationController
- ReplicaSet
- Deployment
- StatefulSet
- Job
- CronJob
- Ingress
- APIService
During uninstallation of a release, the order is reversed (as shown here).
