Although EDB Postgres Distributed for Kubernetes (PGD4K) supports architectures spanning multiple Red Hat OpenShift clusters, this document focuses only on elevating the single point of failure of PostgreSQL databases with EDB PG4K to a Red Hat OpenShift cluster, typically equivalent to an entire region in the cloud or a data center in on-premises deployments. The recommendations included in this document serve as a building block for more complex architectures across different Red Hat OpenShift clusters. A separate document covers addressing multiple Red Hat OpenShift clusters.

CloudNativePG (CNPG), originally built by EDB and now a CNCF Sandbox project, represents a paradigm shift in how PostgreSQL is managed within Kubernetes environments. Unlike traditional approaches that treat containers as mere virtual machines, CNPG is an open-source operator designed specifically for the Kubernetes API, treating the database as a critical capability of the cloud-native ecosystem. By automating the full lifecycle—from high availability failover and point-in-time recovery to native Prometheus-based observability—CNPG eliminates the operational friction typically associated with running stateful workloads at scale.

Learn how EDB Postgres Advances Server reflects better engineering practice for three recurring enterprise problems: leaving Oracle without destabilizing rewrites, enforcing security where the data actually lives, and operating Postgres predictably at scale.

Learn how EDB Postgres (PostgreSQL as packaged and supported by EDB), combined with pgvector and EDB Postgres AI Factory AI Pipelines, provides an omni-data foundation in which relational records, JSON documents, and vector embeddings are stored and queried together.

Achieving optimal performance and scalability with EDB Postgres is not an isolated database administration task; it is a holistic engineering discipline that begins with the foundational layers of hardware and the operating system.

EDB Postgres leverages a combination of enterprise-grade tools and architectural designs to ensure high availability (HA), disaster recovery (DR), and comprehensive backup and recovery.

Securing business-critical data in a large-scale PostgreSQL environment demands a multifaceted approach that extends beyond basic user permissions.

EDB as a company embraces the DevOps principles, both as the developer of software that is used in critically important systems by millions of users around the world and as the provider of tools that enable users to practice DevOps in their environments when it comes to deploying and managing Postgres and related tools.

From sovereign infrastructure to agentic intelligence, these predictions from the pioneers of the sovereign AI movement offer a clear view of the opportunities, risks, and architectural decisions that will define competitiveness in 2026.

While replacing Oracle with Postgres can yield cost reductions of upward of 80%, agility, innovation, microservices, and the move to the cloud have recently emerged as the dominant drivers. Oracle is the #1 legacy database, and its extremely onerous license policies are driving the majority of migration demand. This white paper focuses on the most popular source and target for database migrations: moving from Oracle to Postgres.