Helm Search Hub

helm search hub

search for charts in the Artifact Hub or your own hub instance

Synopsis

Search for Helm charts in the Artifact Hub or your own hub instance.

Artifact Hub is a web-based application that enables finding, installing, and publishing packages and configurations for CNCF projects, including publicly available distributed charts Helm charts. It is a Cloud Native Computing Foundation sandbox project. You can browse the hub at https://artifacthub.io/

The [KEYWORD] argument accepts either a keyword string, or quoted string of rich query options. For rich query options documentation, see https://artifacthub.github.io/hub/api/?urls.primaryName=Monocular%20compatible%20search%20API#/Monocular/get_api_chartsvc_v1_charts_search

Previous versions of Helm used an instance of Monocular as the default ‘endpoint’, so for backwards compatibility Artifact Hub is compatible with the Monocular search API. Similarly, when setting the ‘endpoint’ flag, the specified endpoint must also be implement a Monocular compatible search API endpoint. Note that when specifying a Monocular instance as the ‘endpoint’, rich queries are not supported. For API details, see https://github.com/helm/monocular

  1. helm search hub [KEYWORD] [flags]

Options

  1. --endpoint string Hub instance to query for charts (default "https://hub.helm.sh")
  2. --fail-on-no-result search fails if no results are found
  3. -h, --help help for hub
  4. --list-repo-url print charts repository URL
  5. --max-col-width uint maximum column width for output table (default 50)
  6. -o, --output format prints the output in the specified format. Allowed values: table, json, yaml (default table)

Options inherited from parent commands

  1. --burst-limit int client-side default throttling limit (default 100)
  2. --debug enable verbose output
  3. --kube-apiserver string the address and the port for the Kubernetes API server
  4. --kube-as-group stringArray group to impersonate for the operation, this flag can be repeated to specify multiple groups.
  5. --kube-as-user string username to impersonate for the operation
  6. --kube-ca-file string the certificate authority file for the Kubernetes API server connection
  7. --kube-context string name of the kubeconfig context to use
  8. --kube-insecure-skip-tls-verify if true, the Kubernetes API server's certificate will not be checked for validity. This will make your HTTPS connections insecure
  9. --kube-tls-server-name string server name to use for Kubernetes API server certificate validation. If it is not provided, the hostname used to contact the server is used
  10. --kube-token string bearer token used for authentication
  11. --kubeconfig string path to the kubeconfig file
  12. -n, --namespace string namespace scope for this request
  13. --qps float32 queries per second used when communicating with the Kubernetes API, not including bursting
  14. --registry-config string path to the registry config file (default "~/.config/helm/registry/config.json")
  15. --repository-cache string path to the directory containing cached repository indexes (default "~/.cache/helm/repository")
  16. --repository-config string path to the file containing repository names and URLs (default "~/.config/helm/repositories.yaml")

SEE ALSO

Auto generated by spf13/cobra on 11-Sep-2024