helm version

Print the client/server version information

Synopsis

Show the client and server versions for Helm and tiller.

This will print a representation of the client and server versions of Helm and Tiller. The output will look something like this:

Client: &version.Version{SemVer:“v2.0.0”, GitCommit:“ff52399e51bb880526e9cd0ed8386f6433b74da1”, GitTreeState:“clean”} Server: &version.Version{SemVer:“v2.0.0”, GitCommit:“b0c113dfb9f612a9add796549da66c0d294508a3”, GitTreeState:“clean”}

  • SemVer is the semantic version of the release.
  • GitCommit is the SHA for the commit that this version was built from.
  • GitTreeState is “clean” if there are no local code changes when this binary was built, and “dirty” if the binary was built from locally modified code.

To print just the client version, use ‘–client’. To print just the server version, use ‘–server’.

  1. helm version [flags]

Options

  1.   -c, --client                Client version only
  2.   -h, --help                  help for version
  3.   -s, --server                Server version only
  4.       --short                 Print the version number
  5.       --template string       Template for version string format
  6.       --tls                   Enable TLS for request
  7.       --tls-ca-cert string    Path to TLS CA certificate file (default "$HELM_HOME/ca.pem")
  8.       --tls-cert string       Path to TLS certificate file (default "$HELM_HOME/cert.pem")
  9.       --tls-hostname string   The server name used to verify the hostname on the returned certificates from the server
  10.       --tls-key string        Path to TLS key file (default "$HELM_HOME/key.pem")
  11.       --tls-verify            Enable TLS for request and verify remote

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 of the kubeconfig file to be used
  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 16-May-2019