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

Introduce higher and lower bounds for the number of instances (#178)

Browse Source 
* Introduce higher and lower bounds for the number of instances

Reduce the number of instances to the min_instances if it is lower and
to the max_instances if it is higher. -1 for either of those means there
is no lower or upper bound.

In addition, terminate the operator when there is a nonsense in the
configuration (i.e. max_instances < min_instances).

Reviewed by Jan Mußler and Sergey Dudoladov.
This commit is contained in:
Oleksii Kliukin
2017-12-15 16:02:50 +01:00
committed by GitHub
parent 0e255f82c6
commit bf80f5225e
4 changed files with 46 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+6
View File
@@ -180,6 +180,12 @@ This ConfigMap is then added as a source of environment variables to the Postgre
:exclamation: Note that there are environment variables defined by the operator itself in order to pass parameters to the Spilo image. The values from the operator for those variables will take precedence over those defined in the `pod_environment_configmap`.
### Limiting the number of instances in clusters with `min_instances` and `max_instances`
As a preventive measure, one can restrict the minimum and the maximum number of instances permitted by each Postgres cluster managed by the operator.
If either `min_instances` or `max_instances` is set to a non-zero value, the operator may adjust the number of instances specified in the cluster manifest to match either the min or the max boundary.
For instance, of a cluster manifest has 1 instance and the min_instances is set to 3, the cluster will be created with 3 instances. By default, both parameters are set to -1.
# Setup development environment
The following steps guide you through the setup to work on the operator itself.