From 3bfd5d4f18d882b387f3e5cd7cdd3c21bdfd86e8 Mon Sep 17 00:00:00 2001 From: Sergey Dudoladov <sergey.dudoladov@zalando.de> Date: Tue, 25 Sep 2018 13:09:52 +0200 Subject: [PATCH] Improve the wording of the docs --- docs/administrator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/administrator.md b/docs/administrator.md index 7fba5395..1e31177b 100644 --- a/docs/administrator.md +++ b/docs/administrator.md @@ -200,7 +200,7 @@ manifest, the operator configmap's settings `enable_master_load_balancer` and `enable_replica_load_balancer` apply. Note that the operator settings affect all Postgresql services running in all namespaces watched by the operator. -To limit the range of IP adresses that can reach a load balancer, specify the desired ranges in the `allowedSourceRanges` field (applies to both master and replica LBs). To prevent exposing LBs to the entire Internet, this field is set by default to `127.0.0.1/32`. If you want to return to this default by changing the existing manifest, please explicitly set the `allowedSourceRanges` field to the empty sequence `[]`; setting it to `null` or omitting entirely may lead to k8s removing this field from the manifest due to [its handling of null fields](https://kubernetes.io/docs/concepts/overview/object-management-kubectl/declarative-config/#how-apply-calculates-differences-and-merges-changes). Then the resultant manifest will not have the necessary change, and the operator will respectively do noting with the source ranges. +To limit the range of IP adresses that can reach a load balancer, specify desired ranges in the `allowedSourceRanges` field (applies to both master and replica LBs). To prevent exposing LBs to the entire Internet, this field is set at cluster creation time to `127.0.0.1/32` unless overwritten explicitly. If you want to revoke all IP ranges from an existing cluster, please set the `allowedSourceRanges` field to `127.0.0.1/32` or to the empty sequence `[]`. Setting the field to `null` or omitting entirely may lead to k8s removing this field from the manifest due to [the k8s handling of null fields](https://kubernetes.io/docs/concepts/overview/object-management-kubectl/declarative-config/#how-apply-calculates-differences-and-merges-changes). Then the resultant manifest will not have the necessary change, and the operator will respectively do noting with the existing source ranges. ## Running periodic 'autorepair' scans of Kubernetes objects -- GitLab