public_git/postgres-operator
1
0
Fork 0
mirror of https://github.com/zalando/postgres-operator.git synced 2026-09-30 19:02:57 +02:00
Code Issues Projects Releases Wiki Activity

Keep single values.yaml in operator chart while supporting ConfigMap & CRD (#1224)

Browse Source 
* Keep single values.yaml while supporting ConfigMap & CRD

Co-authored-by: Damiano Albani <damiano.albani@geodan.nl>
This commit is contained in:
Damiano Albani
2021-06-03 09:28:18 +02:00
committed by GitHub
co-authored by Damiano Albani
parent a37e78bd9a
commit b300fca364
6 changed files with 114 additions and 488 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/developer.md
+4 -5
View File
@@ -314,13 +314,12 @@ Please, reflect your changes in tests, for example in:
For the CRD-based configuration, please update the following files:
* the default [OperatorConfiguration](../manifests/postgresql-operator-default-configuration.yaml)
* the Helm chart's [values-crd file](../charts/postgres-operator/values.yaml)
* the CRD's [validation](../manifests/operatorconfiguration.crd.yaml)
* the CRD's validation in the [Helm chart](../charts/postgres-operator/crds/operatorconfigurations.yaml)
Reflect the changes in the ConfigMap configuration as well (note that numeric
and boolean parameters have to use double quotes here):
* [ConfigMap](../manifests/configmap.yaml) manifest
* the Helm chart's default [values file](../charts/postgres-operator/values.yaml)
Add new options also to the Helm chart's [values file](../charts/postgres-operator/values.yaml) file.
It follows the OperatorConfiguration CRD layout. Nested values will be flattened for the ConfigMap.
Last but no least, update the [ConfigMap](../manifests/configmap.yaml) manifest example as well.
### Updating documentation