helm/common
1
0
Fork 0
Code Issues Pull Requests 2 Actions Releases Activity

cs: fix
All checks were successful
continuous-integration/drone/push Build is passing
Details

Browse Source
This commit is contained in:
Konstantin Grachev
2023-03-02 23:44:38 +03:00
parent 1975611101
commit 6342d7be31
8 changed files with 98 additions and 94 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -19,7 +19,8 @@ dependencies:
repository: https://harbor.grachevko.ru/chartrepo/helm
```
Once you have defined dependencies, you should run the following command to download this chart into your `charts/` directory:
Once you have defined dependencies, you should run the following command to download this chart into your `charts/`
directory:
```shell
$ helm dep build
@ -61,13 +62,15 @@ helm.sh/chart: foo-1.2.3-beta.55_1234
### `common.fullname`
The `common.fullname` template generates a name suitable for the `name:` field in Kubernetes metadata. It is used like this:
The `common.fullname` template generates a name suitable for the `name:` field in Kubernetes metadata. It is used like
this:
```yaml
name: { { include "common.fullname" . } }
```
This prints the value of `{{ .Release.Name }}-{{ .Chart.Name }}` by default, but can be overridden with `.Values. fullnameOverride`:
This prints the value of `{{ .Release.Name }}-{{ .Chart.Name }}` by default, but can be overridden
with `.Values. fullnameOverride`:
```yaml
fullnameOverride: some-name
@ -142,7 +145,8 @@ metadata:
name: release-name-mychart
```
Most of the common templates that define a resource type (e.g. `common.configMap` or `common.cronJob`) use this to generate the metadata, which means they inherit the same `labels` and `name` fields.
Most of the common templates that define a resource type (e.g. `common.configMap` or `common.cronJob`) use this to
generate the metadata, which means they inherit the same `labels` and `name` fields.
### `common.name`