Skip to content

Release 3.2.0

Choose a tag to compare

View all tags
@jmccormick2001 jmccormick2001 released this 22 Aug 23:03
· 2991 commits to master since this release
3.2.0
a64b053
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

This release includes:

  • removal of CCP_IMAGE_PREFIX and CO_IMAGE_PREFIX and CO_IMAGE_TAG environment variables from the deployment.yaml file and Helm chart equvalent, instead these values will be pulled from the pgo.yaml configuraiton file mounted by both the apiserver and operator containers, see the upgrade notes for details
  • #162 - added the MatchLabels attribute to the storage configuration as an optional attribute in the pgo.yaml file, when specified, it will cause a label selector to be added to the PVC of form "name=mycluster"
  • #186 - added a --ccp-image-tag command line flag to the pgo scale command which allows you to specify a specific postgres image tag to be used for the scaled replicas which can now be different than the primary image
  • #188 - added the pgo reload command which will cause a pg_ctl reload command to be executed on a list of matching PG databases
  • added ExternalIP for Services into the 'pgo show cluster' API response to support LoadBalancer service types
  • #276 - added "--service-type" command flag for creating a cluster and for scaling it, this will let users override ClusterIP with LoadBalancer in this release. The service type can be globally set in the pgo.yaml file as well.
  • #274 - documented upgrade requirement for upgrading clusters from 2.6 to 3.2 releases, applies to already created clusters.
  • #284 - added 'pgo show user' command, this replaces the '--show-secrets' flag on the 'pgo show cluster' command, a new permission named SHOW_SECRETS_PERM was added. pgo roles need this permission in order to see user secrets with this change.
  • #283 - added API fields to support pgo-ui and also improve the pgo CLI output.
  • #290 - added pgo-version label to clusters to keep track of what pgo version was used to create a cluster
  • #288 - added ready status check into the pgo test command to avoid hanging at the command line when a pod is not ready
  • #271 - updated command documentation
  • #203 - validate pgouser roles at startup time, apiserver will not start with invalid roles after this change
  • #263 - add pgo.yaml global flag for autofail, when set, will apply auto failover checks on all created clusters
  • #201 - added scale down ability to pgo scale command, with this command you can selectively delete replicas
  • moved the MetricsFlag in the pgo.yaml to to the Cluster section instead of the Pgo section to be more consistent with the sections of the configuration file
  • #272 - added pgbadger command line flag and pgo.yaml flag, when set, will cause a crunchy-pgbadger container sidecar to be added to the database pods.
  • initial ALPHA pgbackrest integration, further work will be done to support pgbackrest in future versions of the Postgres Operator, this is a trial to get feedback, future releases will build upon this initial functionality, see the Design Docs and Command Docs for more details on how this integration works
  • deprecate the storage types 'existing' and 'emptydir', these are no longer very useful and will be removed in the upcoming release. This will leave 'create' and 'dynamic' as the supported storage types.
  • includes updated Postgres packages in the Operator containers that require Postgres
  • added changes into the collect.json template for metrics collection to support crunchy-containers 2.1.0 which introduced a new version of pgmonitor, grafana (metrics). This change requires you to upgrade to the crunchy-collect 2.1.0 container.
  • updated the configuration to use the crunchy container suite 2.1.0 release as the default images
Assets 3
Loading