Files
chart/library/common/docs/container/envFrom.md
Stavros Kois 929e60d801 NAS-121003 / 23.10 / Adapt charts CI and improve/fix common (#1011)
* Adapt charts CI and improve/fix common

* add check on permissions contaienr

* add postgres template

* update comments

* Update create_app.sh

* add check

* update script

* auto gen item.yaml from Chart,yaml

* rename readme on dest

* duplicate readme from the same source

* correct comment

* reoder

* remove extra space

* keep both README and app-readme

* update regex, to also allow 2 letter names, which is also valid

* No need to check host network if there aren't any pod values

* use same pattern as the pod.name label (not prepending release-name

* update deps

* add chart dirs to ci

* Add a validation to check if there is any yaml errors after merging files

* update charts path on ci

* common/1.0.0/ -> common/

* update common-test dep path

* temp update create_app script

* make permissions container name configurable, incase we want to change order of execution

* update naming convention

* fix typo and a missed name change

* do not allow `--` in names
2023-03-16 17:36:19 +02:00

47 lines
2.4 KiB
Markdown

# Env From
Assume every key below has a prefix of `workload.[workload-name].podSpec.containers.[container-name]`.
| Key | Type | Required | Helm Template | Default | Description |
| :------------------------------------ | :-------: | :------: | :-----------: | :-----: | :------------------------------------------------------------------- |
| envFrom | `list` | ❌ | ❌ | `{}` | Define envFrom for the container |
| envFrom.secretRef | `dict` | ✅ | ❌ | `{}` | Define the secretRef |
| envFrom.secretRef.name | `string` | ✅ | ✅ | `""` | Define the secret name |
| envFrom.secretRef.expandObjectName | `boolean` | ❌ | ❌ | `true` | Whether to expand (adding the fullname as prefix) the secret name |
| envFrom.configMapRef | `dict` | ✅ | ❌ | `{}` | Define the configMapRef |
| envFrom.configMapRef.name | `string` | ✅ | ✅ | `""` | Define the configmap name |
| envFrom.configMapRef.expandObjectName | `boolean` | ❌ | ❌ | `true` | Whether to expand (adding the fullname as prefix) the configmap name |
> When the `expandObjectName` is `true`, it will also scan the contents of the secret/configmap
> for duplicate keys between other secrets/configmaps/env/envList/fixedEnv and will throw an error if it finds any.
> `expandObjectName` should only be set to `false` if you want to consume a secret/configmap created outside of this chart
---
Appears in:
- `.Values.workload.[workload-name].podSpec.containers.[container-name].envFrom`
---
Examples:
```yaml
workload:
workload-name:
enabled: true
primary: true
podSpec:
containers:
container-name:
enabled: true
primary: true
envFrom:
- secretRef:
# This will be expanded to `fullname-secret-name`
name: secret-name
- configMapRef:
name: configmap-name
expandObjectName: false
```