mirror of
https://github.com/bjw-s-labs/helm-charts.git
synced 2025-07-04 00:47:04 +02:00
feat(common): Release 2.0.0 (#189)
This commit is contained in:
parent
8a42d212af
commit
98677d85b2
56 changed files with 1192 additions and 1804 deletions
49
docs/common-library/howto/helm-templates.md
Normal file
49
docs/common-library/howto/helm-templates.md
Normal file
|
@ -0,0 +1,49 @@
|
|||
---
|
||||
hide:
|
||||
- toc
|
||||
---
|
||||
|
||||
# Helm templates
|
||||
|
||||
Some fields in the common library `values.yaml` allow the use of Helm templates for their values.
|
||||
This is often indicated by a remark similar to `Helm template enabled` in the field description.
|
||||
|
||||
This feature allows you to set the value of that key to the output of the given Helm template.
|
||||
|
||||
## Example
|
||||
|
||||
Given the following `values.yaml`
|
||||
|
||||
```yaml
|
||||
containers:
|
||||
subcleaner:
|
||||
name: subcleaner
|
||||
|
||||
image:
|
||||
repository: k8s.gcr.io/git-sync/git-sync
|
||||
tag: {{.Chart.AppVersion}}
|
||||
|
||||
args:
|
||||
- --repo=https://github.com/KBlixt/subcleaner.git
|
||||
- --branch=master
|
||||
- --depth=1
|
||||
- --root=/add-ons/subcleaner
|
||||
```
|
||||
|
||||
This would render as follows:
|
||||
|
||||
```yaml
|
||||
containers:
|
||||
subcleaner:
|
||||
name: subcleaner
|
||||
|
||||
image:
|
||||
repository: k8s.gcr.io/git-sync/git-sync
|
||||
tag: v3.6.2
|
||||
|
||||
args:
|
||||
- --repo=https://github.com/KBlixt/subcleaner.git
|
||||
- --branch=master
|
||||
- --depth=1
|
||||
- --root=/add-ons/subcleaner
|
||||
```
|
3
docs/common-library/howto/index.md
Normal file
3
docs/common-library/howto/index.md
Normal file
|
@ -0,0 +1,3 @@
|
|||
# How to...
|
||||
|
||||
Here you can find information on how to accomplish specific scenario's.
|
42
docs/common-library/howto/multiple-subpath.md
Normal file
42
docs/common-library/howto/multiple-subpath.md
Normal file
|
@ -0,0 +1,42 @@
|
|||
---
|
||||
hide:
|
||||
- toc
|
||||
---
|
||||
|
||||
# Multiple subPaths for 1 volume
|
||||
|
||||
It is possible to mount multiple subPaths from the same volume to a
|
||||
container. This can be achieved by specifying `subPath` with a list
|
||||
instead of a string.
|
||||
|
||||
## Example
|
||||
|
||||
```yaml
|
||||
persistence:
|
||||
config:
|
||||
type: configMap
|
||||
name: my-configMap
|
||||
advancedMounts:
|
||||
main: # (1)
|
||||
main: # (2)
|
||||
- path: /data/config.yaml
|
||||
readOnly: false
|
||||
subPath: config.yaml
|
||||
- path: /data/secondConfigFile.yaml
|
||||
readOnly: false
|
||||
subPath: secondConfigFile.yaml
|
||||
second-container: # (3)
|
||||
- path: /appdata/config
|
||||
readOnly: true
|
||||
second-controller: # (4)
|
||||
main: # (5)
|
||||
- path: /data/config.yaml
|
||||
readOnly: false
|
||||
subPath: config.yaml
|
||||
```
|
||||
|
||||
1. the controller with the "main" identifier
|
||||
2. the container with the "main" identifier
|
||||
3. the container with the "second-container" identifier
|
||||
4. the controller with the "second-controller" identifier
|
||||
5. the container with the "main" identifier
|
Loading…
Add table
Add a link
Reference in a new issue