helm rollback

roll back a release to a previous revision

Synopsis

This command rolls back a release to a previous revision.

The first argument of the rollback command is the name of a release, and the second is a revision (version) number. To see revision numbers, run ‘helm history RELEASE’. If you’d like to rollback to the previous release use ‘helm rollback [RELEASE] 0’.

  1. helm rollback [flags] [RELEASE] [REVISION]

Options

  1.       --cleanup-on-fail       allow deletion of new resources created in this rollback when rollback failed
  2.       --description string    specify a description for the release
  3.       --dry-run               simulate a rollback
  4.       --force                 force resource update through delete/recreate if needed
  5.   -h, --help                  help for rollback
  6.       --no-hooks              prevent hooks from running during rollback
  7.       --recreate-pods         performs pods restart for the resource if applicable
  8.       --timeout int           time in seconds to wait for any individual Kubernetes operation (like Jobs for hooks) (default 300)
  9.       --tls                   enable TLS for request
  10.       --tls-ca-cert string    path to TLS CA certificate file (default "$HELM-HOME/ca.pem")
  11.       --tls-cert string       path to TLS certificate file (default "$HELM-HOME/cert.pem")
  12.       --tls-hostname string   the server name used to verify the hostname on the returned certificates from the server
  13.       --tls-key string        path to TLS key file (default "$HELM-HOME/key.pem")
  14.       --tls-verify            enable TLS for request and verify remote
  15.       --wait                  if set, will wait until all Pods, PVCs, Services, and minimum number of Pods of a Deployment are in a ready state before marking the release as successful. It will wait for as long as --timeout

Options inherited from parent commands

  1.       --debug                           enable verbose output
  2.       --home string                     location of your Helm config. Overrides $HELM-HOME (default "~/.helm")
  3.       --host string                     address of Tiller. Overrides $HELM-HOST
  4.       --kube-context string             name of the kubeconfig context to use
  5.       --kubeconfig string               absolute path to the kubeconfig file to use
  6.       --tiller-connection-timeout int   the duration (in seconds) Helm will wait to establish a connection to tiller (default 300)
  7.       --tiller-namespace string         namespace of Tiller (default "kube-system")

SEE ALSO

  • helm - The Helm package manager for Kubernetes.
Auto generated by spf13/cobra on 5-Feb-2019