What's New in Crunchy PostgreSQL Operator 4.0
Crunchy Data is pleased to release PostgreSQL Operator 4.0.
Crunchy PostgreSQL Operator extends Kubernetes to give you the power to easily create, configure and manage PostgreSQL clusters at scale. When combined with the Crunchy PostgreSQL Container Suite, the Crunchy PostgreSQL Operator provides an open source software solution for PostgreSQL scaling, high-availability, disaster recovery, monitoring, and more. All of this capability comes with the repeatability and automation that comes from Operators on Kubernetes.
Crunchy PostgreSQL Operator is open source and developed in close collaboration with users to support enterprise deployments of cloud agnostic PostgreSQL-as-a-Service capability. This release comes after extensive feedback from our customers and the community to ensure the scalability and security that sysadmins, DBAs, and developers have come to rely on.
Key features added to the Crunchy PostgreSQL Operator 4.0. include:
Namespace Deployment Options
Support for deploying the Crunchy PostgreSQL Operator with additional namespace patterns, including the ability to deploy the operator its own namespace but manage PostgreSQL clusters in multiple namespace. The new namespace management features lets users create multi-tenant PostgreSQL environments that add further isolation and security to their deployments. The various deployment patterns are included within the Design documentation.
Further Enhancements to pgBackRest Integration
Crunchy PostgreSQL Operator 4.0. continues the integration of pgBackRest, building on features incorporated within version 3.5. For example, this latest release adds the ability to perform pgBackRest backups to Amazon S3. This allows users to create an automated, geographically distributed, and hybrid cloud disaster recovery strategy: : in addition to the benefits of backing up to a distributed object store, users can move their PostgreSQL data easily between data centers.
Integrated PostgreSQL Benchmarking
Crunchy PostgreSQL Operator 4.0. adds the ability to run pgBench, a simple program for running standard and customizable benchmark tests on PostgreSQL, from the Operator command-line interface. The operator CLI overview documentation provides guidance as to how to use this capability. This provides and simple and easy means for users to compare and investigate performance and scalability under different deployment scenarios.
Ansible Playbook Based Installation
Crunchy PostgreSQL Operator 4.0 provides Ansible playbooks to automate operator installation. The Crunchy PostgreSQL Operator Ansible Installers allow users to install PostgreSQL Operator on Kubernetes and OpenShift from a Linux, Mac or Windows (Ubuntu subsystem) host. In connection with the automated installation, the Ansible playbooks can generate TLS certificates required by the PostgreSQL Operator and configure PostgreSQL Operator settings from a single inventory file.
Operator Lifecycle Management (OLM)
Crunchy PostgreSQL Operator 4.0. supports Operator Lifecycle Management (OLM). The OLM project is a component of the Operator Framework, an open source toolkit to manage Operators, in an effective, automated, and scalable way. OLM concepts were included into Crunchy PostgreSQL Operator to assist in the deployment on Kubernetes using OLM integration.
Documentation Improvements
The latest release includes enhanced user documentation, providing additional information regarding architecture, installation and configuration options. Please take a look and let us know what you think.
How to Get Started
Please give the new release of the operator a try and let us know what you think about these new features.
If you are new to the Crunchy PostgreSQL Operator and interested in installing the Crunchy PostgreSQL Operator in your environment, please start here: Installation via Ansible. Instructions for Installation via Bash are also available.
Interested in a feature you dont see in this release? Please let us know. The project is open source and welcomes issues and pull requests.
We plan to provide a series of posts over the coming weeks to provide additional information about these new features and how they can support enterprise PostgreSQL-as-a-Service requirements.
