public_git/postgres-operator
1
0
Fork 0
mirror of https://github.com/zalando/postgres-operator.git synced 2026-10-07 04:12:56 +02:00
Code Issues Projects Releases Wiki Activity

add global toggle and enum field for schema

Browse Source
This commit is contained in:
Felix Kunde
2020-05-26 12:37:10 +02:00
parent 2484af436a
commit ae207da172
20 changed files with 132 additions and 59 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/reference/cluster_manifest.md
+4 -4
View File
@@ -82,10 +82,10 @@ These parameters are grouped directly under the `spec` key in the manifest.
`enable_replica_load_balancer` parameter) to define whether to enable the
load balancer pointing to the Postgres standby instances. Optional.
* **enablePublicLoadBalancer**
boolean flag to override the operator defaults (set by the
`enable_public_load_balancer` parameter) to define whether to use an internal
or public ELB. Optional.
* **loadBalancerSchema**
can be either `internal` or `public`. Overrides the configured default schema
but will not work for `public`, if this is forbidden with
`allow_public_load_balancers` set to false. Optional.
* **allowedSourceRanges**
when one or more load balancers are enabled for the cluster, this parameter
docs/reference/operator_parameters.md
+8 -4
View File
@@ -418,12 +418,16 @@ In the CRD-based configuration they are grouped under the `load_balancer` key.
cluster. Can be overridden by individual cluster settings. The default is
`false`.
* **enable_public_load_balancer**
when using load balancer services they can be internal or public which can be
toggled with this option. The default is `false`.
* **default_load_balancer_schema**
when using load balancer services they can be `internal` or `public` which can
be toggled with this option. Note, that public load balancers must be allowed
via configuration (see next option). The default is `internal`.
* **allow_public_load_balancers**
global toggle to allow usage of public load balancers. The default is `true`.
* **custom_service_annotations**
This key/value map provides a list of annotations that get attached to each
this key/value map provides a list of annotations that get attached to each
service of a cluster created by the operator. If the annotation key is also
provided by the cluster definition, the manifest value is used.
Optional.