github.com/Racer159/jackal@v0.32.7-0.20240401174413-0bd2339e4f2e/docs/2-the-jackal-cli/100-cli-commands/jackal_tools_helm_dependency.md (about) 1 # jackal tools helm dependency 2 <!-- Auto-generated by hack/gen-cli-docs.sh --> 3 4 manage a chart's dependencies 5 6 ## Synopsis 7 8 9 Manage the dependencies of a chart. 10 11 Helm charts store their dependencies in 'charts/'. For chart developers, it is 12 often easier to manage dependencies in 'Chart.yaml' which declares all 13 dependencies. 14 15 The dependency commands operate on that file, making it easy to synchronize 16 between the desired dependencies and the actual dependencies stored in the 17 'charts/' directory. 18 19 For example, this Chart.yaml declares two dependencies: 20 21 # Chart.yaml 22 dependencies: 23 - name: nginx 24 version: "1.2.3" 25 repository: "https://example.com/charts" 26 - name: memcached 27 version: "3.2.1" 28 repository: "https://another.example.com/charts" 29 30 31 The 'name' should be the name of a chart, where that name must match the name 32 in that chart's 'Chart.yaml' file. 33 34 The 'version' field should contain a semantic version or version range. 35 36 The 'repository' URL should point to a Chart Repository. Helm expects that by 37 appending '/index.yaml' to the URL, it should be able to retrieve the chart 38 repository's index. Note: 'repository' can be an alias. The alias must start 39 with 'alias:' or '@'. 40 41 Starting from 2.2.0, repository can be defined as the path to the directory of 42 the dependency charts stored locally. The path should start with a prefix of 43 "file://". For example, 44 45 # Chart.yaml 46 dependencies: 47 - name: nginx 48 version: "1.2.3" 49 repository: "file://../dependency_chart/nginx" 50 51 If the dependency chart is retrieved locally, it is not required to have the 52 repository added to helm by "helm add repo". Version matching is also supported 53 for this case. 54 55 56 ## Options 57 58 ``` 59 -h, --help help for dependency 60 ``` 61 62 ## Options inherited from parent commands 63 64 ``` 65 --burst-limit int client-side default throttling limit (default 100) 66 --debug enable verbose output 67 --kube-apiserver string the address and the port for the Kubernetes API server 68 --kube-as-group stringArray group to impersonate for the operation, this flag can be repeated to specify multiple groups. 69 --kube-as-user string username to impersonate for the operation 70 --kube-ca-file string the certificate authority file for the Kubernetes API server connection 71 --kube-context string name of the kubeconfig context to use 72 --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 73 --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 74 --kube-token string bearer token used for authentication 75 --kubeconfig string path to the kubeconfig file 76 -n, --namespace string namespace scope for this request 77 --qps float32 queries per second used when communicating with the Kubernetes API, not including bursting 78 --registry-config string path to the registry config file 79 --repository-cache string path to the file containing cached repository indexes 80 --repository-config string path to the file containing repository names and URLs 81 ``` 82 83 ## SEE ALSO 84 85 * [jackal tools helm](jackal_tools_helm.md) - Subset of the Helm CLI included with Jackal to help manage helm charts. 86 * [jackal tools helm dependency build](jackal_tools_helm_dependency_build.md) - rebuild the charts/ directory based on the Chart.lock file 87 * [jackal tools helm dependency list](jackal_tools_helm_dependency_list.md) - list the dependencies for the given chart 88 * [jackal tools helm dependency update](jackal_tools_helm_dependency_update.md) - update charts/ based on the contents of Chart.yaml