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
+14-6
Original file line number
Diff line number
Diff line change
@@ -12,12 +12,12 @@ configuration.
12
12
13
13
* CRD-based configuration. The configuration is stored in a custom YAML
14
14
manifest. The manifest is an instance of the custom resource definition (CRD) called
15
-
`OperatorConfiguration`. The operator registers this CRD
15
+
`OperatorConfiguration`. The operator registers this CRD
16
16
during the start and uses it for configuration if the [operator deployment manifest ](https://github.com/zalando-incubator/postgres-operator/blob/master/manifests/postgres-operator.yaml#L21) sets the `POSTGRES_OPERATOR_CONFIGURATION_OBJECT` env variable to a non-empty value. The variable should point to the
17
17
`postgresql-operator-configuration` object in the operator's namespace.
18
18
19
19
The CRD-based configuration is a regular YAML
20
-
document; non-scalar keys are simply represented in the usual YAML way.
20
+
document; non-scalar keys are simply represented in the usual YAML way.
21
21
There are no default values built-in in the operator, each parameter that is
22
22
not supplied in the configuration receives an empty value. In order to
23
23
create your own configuration just copy the [default
@@ -172,6 +172,14 @@ configuration they are grouped under the `kubernetes` key.
172
172
list of `name:value` pairs for additional labels assigned to the cluster
173
173
objects. The default is `application:spilo`.
174
174
175
+
***inherited_labels**
176
+
list of labels that can be inherited from the cluster manifest, and added to
177
+
each child objects (`StatefulSet`, `Pod`, `Service` and `Endpoints`) created by
178
+
the opertor.
179
+
Typical use case is to dynamically pass labels that are specific to a given
180
+
postgres cluster, in order to implement `NetworkPolicy`.
181
+
The default is empty.
182
+
175
183
***cluster_name_label**
176
184
name of the label assigned to Kubernetes objects created by the operator that
177
185
indicates which cluster a given object belongs to. The default is
@@ -198,13 +206,13 @@ configuration they are grouped under the `kubernetes` key.
198
206
All variables from that ConfigMap are injected to the pod's environment, on
199
207
conflicts they are overridden by the environment variables generated by the
that should be assigned to the Postgres pods. The priority class itself must be defined in advance.
206
214
Default is empty (use the default priority class).
207
-
215
+
208
216
209
217
## Kubernetes resource requests
210
218
@@ -350,7 +358,7 @@ Options to aid debugging of the operator itself. Grouped under the `debug` key.
350
358
boolean parameter that toggles the functionality of the operator that require
351
359
access to the postgres database, i.e. creating databases and users. The default
352
360
is `true`.
353
-
361
+
354
362
## Automatic creation of human users in the database
355
363
356
364
Options to automate creation of human users with the aid of the teams API
@@ -448,4 +456,4 @@ scalyr sidecar. In the CRD-based configuration they are grouped under the
448
456
Memory limit value for the Scalyr sidecar. The default is `1Gi`.
449
457
450
458
451
-
For the configmap operator configuration, the [default parameter values](https://github.com/zalando-incubator/postgres-operator/blob/master/pkg/util/config/config.go#L14) mentioned here are likely to be overwritten in your local operator installation via your local version of the operator configmap. In the case you use the operator CRD, all the CRD defaults are provided in the [operator's default configuration manifest](https://github.com/zalando-incubator/postgres-operator/blob/master/manifests/postgresql-operator-default-configuration.yaml)
459
+
For the configmap operator configuration, the [default parameter values](https://github.com/zalando-incubator/postgres-operator/blob/master/pkg/util/config/config.go#L14) mentioned here are likely to be overwritten in your local operator installation via your local version of the operator configmap. In the case you use the operator CRD, all the CRD defaults are provided in the [operator's default configuration manifest](https://github.com/zalando-incubator/postgres-operator/blob/master/manifests/postgresql-operator-default-configuration.yaml)
0 commit comments