mirror of
https://github.com/zalando/postgres-operator.git
synced 2026-09-30 12:01:34 +02:00
Bump v1.10.0 (#2299)
* bump to v1.9.1 * update year in license and add links to more blog posts * bump go to 1.19 and update dependencies * go for 1.10.0 instead of 1.9.1 * fix unit test - removed obsolete ClusterName field * fix DNS template in UI helm chart deployment file
This commit is contained in:
@@ -89,6 +89,12 @@ Please, report any issues discovered to https://github.com/zalando/postgres-oper
|
||||
|
||||
## Posts
|
||||
|
||||
- Series of blog posts on how to use the Zalando Operator, configure backups and use etcd as DCS by [thedatabaseme](https://thedatabaseme.de/tag/zalando-operator/), Mar. 2022-23.
|
||||
|
||||
- "Zalando Postgres Operator in Production: the way of Helm" by Zangir Kapishov on [medium](https://medium.com/@zkapishov/zalando-postgres-operator-in-production-the-way-of-helm-ccfd639ccb2d), Jan. 2023.
|
||||
|
||||
- "Chaos testing of a Postgres cluster managed by the Zalando Postgres Operator" by Nikolay Sivko on [coroot](https://coroot.com/blog/chaos-testing-zalando-postgres-operator), Aug. 2022.
|
||||
|
||||
- "Getting started with the Zalando Operator for PostgreSQL" by Daniel Westermann on [dbi services blog](https://blog.dbi-services.com/getting-started-with-the-zalando-operator-for-postgresql/), Mar. 2021.
|
||||
|
||||
- "Our experience with Postgres Operator for Kubernetes by Zalando" by Nikolay Bogdanov on [Palark blog](https://blog.palark.com/our-experience-with-postgres-operator-for-kubernetes-by-zalando/), Feb. 2021.
|
||||
|
||||
@@ -491,6 +491,12 @@ configuration they are grouped under the `kubernetes` key.
|
||||
override [topology key](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#built-in-node-labels)
|
||||
for pod anti affinity. The default is `kubernetes.io/hostname`.
|
||||
|
||||
* **pod_antiaffinity_preferred_during_scheduling**
|
||||
when scaling the number of pods beyond the available number of topology
|
||||
keys the anti affinity has to be configured to preferred during scheduling.
|
||||
The default is `false` which means the pod anti affinity will use
|
||||
`requiredDuringSchedulingIgnoredDuringExecution`.
|
||||
|
||||
* **pod_management_policy**
|
||||
specify the [pod management policy](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#pod-management-policies)
|
||||
of stateful sets of PG clusters. The default is `ordered_ready`, the second
|
||||
@@ -768,7 +774,7 @@ grouped under the `logical_backup` key.
|
||||
runs `pg_dumpall` on a replica if possible and uploads compressed results to
|
||||
an S3 bucket under the key `/spilo/pg_cluster_name/cluster_k8s_uuid/logical_backups`.
|
||||
The default image is the same image built with the Zalando-internal CI
|
||||
pipeline. Default: "registry.opensource.zalan.do/acid/logical-backup:v1.9.0"
|
||||
pipeline. Default: "registry.opensource.zalan.do/acid/logical-backup:v1.10.0"
|
||||
|
||||
* **logical_backup_google_application_credentials**
|
||||
Specifies the path of the google cloud service account json file. Default is empty.
|
||||
|
||||
Reference in New Issue
Block a user