Skip to content

Release 3.5.0

Choose a tag to compare

View all tags
@jmccormick2001 jmccormick2001 released this 14 Jan 22:10
· 2606 commits to master since this release
3.5.0
89fef9f

#490 - failover label refactor - this change lets the failover work faster by not requiring a bounce of the PG pods within a PG cluster, see the documentation for details on this change and the impact on existing operator deployments

#481 - make replacing a replica as part of a fail-over a configurable setting in pgo.yaml and on the command line when creating a cluster

#494 - create a storage configuration setting specifically for xlog volumes, the setting is names XlogStorage within the pgo.yaml file.

#495 - support for label matching in storage configurations, this for example will let you specify different
PV types to match on to support multiple zones when using NFS.

#499 - create an autofail 'toggle', pgo update cluster --autofail=true|false is a new command that sets the autofail flag on the pgcluster CRD to enable or disable autofailover logic on a set of clusters.

#500 - fixed bug in pgbackrest restore job to accept PITR target time option, users will pass in --backup-opts="--type=time" --pitr-target="2018-12-12 14:45:58 EST" into the pgo restore command if they want to restore to a given point in time.

#506 - fixed a bug where the Postgres Port was not being able to be overrode when set in pgo.yaml

#521 - added pgbackrest shared repository architecture - with this change, a PG cluster that has pgbackrest enabled will cause a pgbackrest repository to be created as a Deployment configured to act as the pgbackrest repository for the whole Postgres cluster, this change only will work with crunchy containers version 2.3.0 and
is not backward compatible with prior crunchy container versions, see the Documentation Design section for
more details on how this integration is implemented

#505 - added an option to specify in pgo.yaml a new setting, PreferredFailoverNode, which is a selector that determines which nodes to use as 'preferred' when a fail over happens.

Notes on this version:

  • server.crt and server.key are no longer included by default in the repo, instead these are generated when you run the install-rbac.sh script upon installation
  • pgo-backrest-repo is a new container which holds the pgbackrest shared repository used when you deploy a PG cluster with --pgbackrest, keys are generated for pgbackrest repositories when you run install-rbac.sh upon Operator installation
  • pgo-backrest-repo storage is configured via pgo.yaml setting BackrestStorage
  • with this Operator version, the crunchy-postgres container image version 2.3.0 is required for pgbackrest integration within the Operator, you will need to upgrade to this latest version of crunchy-postgres for existing and all new PG clusters created by the Operator.
  • documentation for the Operator was completely revised with this version
  • pgo API keys are now generated when you run the install-rbac.sh script, before this release the server.key and server.crt keys were pre-generated and included into the github repository, running this script is only required
    once or unless you want to re-generate the API keys
  • pgbackrest integration with this release requires sshd keys to be generated, these keys are generated when you run the install-rbac.sh script and only need to be run one time

Breaking changes were made this release, you will want to review these changes here:
https://crunchydata.github.io/postgres-operator/3.5.0/upgrade/

Assets 10
Loading