Deploy security-focused databases and reduce administrative overhead
EP4K is a fully tested and certified Postgres operator for Red Hat OpenShift, which makes the platform capable of running highly available Postgres clusters that are secure by default, replicated, and automatically backed up using object storage buckets or physical volume snapshots. Using standard Kubernetes practices, like using GitOps, policy frameworks, and Tekton pipelines, the operator can create, manage, and control Postgres clusters. This tightly integrates Postgres databases with the rest of the application stack, lowering the cognitive load of developer teams and brings DBAs, DevOps, and developer teams closer together.
Building on years of experience as the world’s largest Postgres contributor and professional services provider, a new Postgres cluster created through EP4K survives the destruction of a replica, with EP4K creating a new replica immediately after it detects the old replica is gone. If the current primary fails, the process of promoting a replica to the primary—critical for achieving low recovery time objectives (RTO)—is completed within seconds. EP4K allows the use of asynchronous or synchronous replication. For disaster recovery, archiving write-ahead log files to an object stored at least every 5 minutes—more often in the case of a busy database—a recovery point objective (RPO) of, at most, 5 minutes is achievable without additional configuration.
Through the addition of physical volume snapshots as a backup and restore target, even very large databases—up to terabytes in size—can be safely run on Red Hat OpenShift with instant backups reducing the time required to restore a database to a matter of minutes. Life cycle management is simplified by using the fully automated EP4K distribution, providing the option to perform inconspicuous rolling, and minor upgrades of database software. By hooking into the Red Hat OpenShift operator lifecycle manager (OLM), the operator itself will be kept up to date without human intervention.
One of the most important aspects of the EDB solution with Red Hat OpenShift is that it is the only database operator to take advantage of Red Hat OpenShift security features and run under the restricted security context constraint (SSC), the most secure security context constraint. Finally, EDB uses the universal base images provided by Red Hat to build container images for the database server, the connection pooler, and the operator. These images are continuously monitored and updated for security updates. This approach provides organizations with full support and security coverage from EDB and Red Hat.