public_git
/
postgres-operator
mirror of https://github.com/zalando/postgres-operator.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

describe forcing the rolling upgrade

This commit is contained in:
Sergey Dudoladov 2020-03-10 12:28:21 +01:00
parent dd10127e5d
commit 507c79357f
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/administrator.md
View File

@ -430,8 +430,8 @@ from numerous escape characters in the latter log entry, view it in CLI with
used internally in K8s.
The operator also support lazy updates of the Spilo image. That means the pod template of a
PG cluster's stateful set is updated immediately with the new image, but no rolling upgrade follows. This feature saves you
some downtime when you know pods are re-started after the update anyway, for instance due to the node rotation.
PG cluster's stateful set is updated immediately with the new image, but no rolling update follows. This feature saves you
a switchover - and hence downtime - when you know pods are re-started later anyway, for instance due to the node rotation. To force a rolling update, disable this mode by setting the `enable_lazy_image_upgrade` to `false` in the operator configuration and restart the operator pod. With the standard eager rolling updates the operator checks during Sync all pods run images specified in their respective statefulsets. The operator triggers a rolling upgrade fo PG clusters that violate this condition.
## Logical backups