You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/operator_parameters.md
+12-5Lines changed: 12 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -161,11 +161,12 @@ Those are top-level keys, containing both leaf keys and groups.
161
161
162
162
***set_memory_request_to_limit**
163
163
Set `memory_request` to `memory_limit` for all Postgres clusters (the default
164
-
value is also increased). This prevents certain cases of memory overcommitment
165
-
at the cost of overprovisioning memory and potential scheduling problems for
166
-
containers with high memory limits due to the lack of memory on Kubernetes
167
-
cluster nodes. This affects all containers created by the operator (Postgres,
168
-
connection pooler, logical backup, scalyr sidecar, and other sidecars except
164
+
value is also increased but configured `max_memory_request` can not be
165
+
bypassed). This prevents certain cases of memory overcommitment at the cost
166
+
of overprovisioning memory and potential scheduling problems for containers
167
+
with high memory limits due to the lack of memory on Kubernetes cluster
168
+
nodes. This affects all containers created by the operator (Postgres,
169
+
connection pooler, logical backup, scalyr sidecar, and other sidecars except
169
170
**sidecars** defined in the operator configuration); to set resources for the
170
171
operator's own container, change the [operator deployment manually](https://github.com/zalando/postgres-operator/blob/master/manifests/postgres-operator.yaml#L20).
171
172
The default is `false`.
@@ -514,6 +515,12 @@ CRD-based configuration.
514
515
memory limits for the Postgres containers, unless overridden by cluster-specific
515
516
settings. The default is `500Mi`.
516
517
518
+
***max_cpu_request**
519
+
optional upper boundary for CPU request
520
+
521
+
***max_memory_request**
522
+
optional upper boundary for memory request
523
+
517
524
***min_cpu_limit**
518
525
hard CPU minimum what we consider to be required to properly run Postgres
519
526
clusters with Patroni on Kubernetes. The default is `250m`.
0 commit comments