Search for a keyword in charts

Synopsis

Search reads through all of the repositories configured on the system, and looks for matches.

It will display the latest stable versions of the charts found. If you specify the –devel flag, the output will include pre-release versions. If you want to search using a version constraint, use –version.

Examples:

  1. # Search for stable release versions matching the keyword "nginx"
  2. helm search nginx
  3. # Search for release versions matching the keyword "nginx", including pre-release versions
  4. helm search nginx --devel
  5. # Search for the latest stable release for nginx-ingress with a major version of 1
  6. helm search nginx-ingress --version ^1.0.0

Repositories are managed with ‘helm repo’ commands.

To look for charts with a particular name (such as stable/mysql), try searching using vertical tabs (\v). Vertical tabs are used as the delimiter between search fields. For example:

  1. helm search --regexp '\vstable/mysql\v'

To search for charts using common keywords (such as “database” or “key-value store”), use

  1. helm search database

or

  1. helm search key-value store
  1. helm search [keyword] [flags]

Options

  1. --col-width uint Specifies the max column width of output (default 60)
  2. --devel use development versions (alpha, beta, and release candidate releases), too. Equivalent to version '>0.0.0-0'. If --version is set, this is ignored
  3. -h, --help help for search
  4. -o, --output string Prints the output in the specified format. Allowed values: table, json, yaml (default "table")
  5. -r, --regexp Use regular expressions for searching
  6. -v, --version string Search using semantic versioning constraints
  7. -l, --versions Show the long listing, with each version of each chart on its own line

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 30-Oct-2019