Skip to content

Release 2.5

Choose a tag to compare

View all tags
@jmccormick2001 jmccormick2001 released this 14 Feb 16:50
· 3431 commits to master since this release
2.5
be602a2

This release includes the following updates from the previous release (2.4):

  • #108 - a confirmation for deletion commands allowing the user a final check before removing clusters or backups, users can override this with a --no-prompt command flag in the pgo client
  • #106 - removed pgo --namespace flag, this is not implemented and could cause errors now that the namespace is determined by the apiserver configuration in this current release
  • updated the bash completion file
  • #103 , the default PG_LOCALE is now set to en_US.UTF8 in the default configuration files when databases are initialized
  • #100 - added a TLS_NO_VERIFY env variable to pgo-apiserver, if set to true will relax the security check on client connections
  • added configuration parameter BasicAuth to pgo.yaml, when set to false, will cause pgo-apiserver to not perform any BasicAuth checks, defaults to true when not specified.
  • #89 - added Secrets to hold the PostgreSQL passwords that are used when creating new clusters
  • #90 - removed Info level messages that showed a password in the container logs
  • #92 - added global flag to include metrics collection to all newly created clusters
  • #54 - added audit log messages, if a global flag is set, calls to the apiserver will be logged specifically for auditing
  • #113 - fix for making all cluster secrets following the same naming convention <>-<>-secret
  • updated RHEL Dockerfiles to use RHEL 7.4
  • added PORT environment variable for pgo-apiserver allowing users to use a port other than 8443
  • added a Windows pgo client to the release files, along with expenv binaries for Mac, Windows, Linux to support quickstart
  • changed the postgres-operator service to be of type "NodePort" to better support cloud providers
  • #79 - added logic to support custom Postgres configurations
  • #87 - you can implement a form of DR using the new storage config mechanism
  • #94 - storage configurations were added to support n-number of storage configurations, these can be referenced on the command line when creating clusters and performing backups
  • added a Service Account to secure the operator deployment
  • added a quickstart script to support deployment to pks and GKE environments
  • fixed a bug where the backup status was not getting updated upon completion
  • added a check to see if a backup job exists prior to allowing the submission of a new backup job
  • revised the operator documentation
Assets 3
Loading