CloudNativePG 1.25 enhances control of PostgreSQL synchronous replication with a new dataDurability option, allowing you to choose between prioritising data consistency or self-healing capabilities. This article explains the feature, contrasts it with previous approaches, and provides guidance on migrating to the new API format.
This recipe shows how to perform an online major PostgreSQL upgrade using the
new declarative approach to logical replication introduced in CloudNativePG
1.25. By leveraging the Publication and Subscription CRDs, users can set up
logical replication between PostgreSQL clusters with ease. I will walk you
through configuring a PostgreSQL 15 publisher, importing schemas into a
PostgreSQL 17 subscriber, and verifying data synchronisation, with the broader
goal of highlighting the benefits of a repeatable and testable upgrade process.
In this CNPG recipe, we explore three essential command-line tools that
simplify working with CloudNativePG in Kubernetes: view-secret, view-cert,
and stern. These tools enhance tasks such as inspecting secrets, verifying
certificates, and tailing logs across multiple pods, streamlining your
PostgreSQL management experience in a cloud-native environment. Whether you’re
troubleshooting or optimising workflows, these utilities will help you boost
productivity and gain better control over your Kubernetes-based PostgreSQL
deployments.
Welcome CNPG Playground, a local learning environment for exploring CloudNativePG and PostgreSQL in Kubernetes. Using Docker and Kind, it simulates real-world scenarios, enabling developers and DBAs to experiment with PostgreSQL replication across two clusters. Designed for hands-on learning, CNPG Playground provides an accessible entry point for testing configurations and features, with plans for future enhancements and community collaboration.
CloudNativePG 1.24 introduces a highly customisable approach to managing
PostgreSQL synchronous replication through the new .spec.postgresql.synchronous
stanza. In this article, I’ll guide you through configuring synchronous
replication within a single Kubernetes cluster and across multiple clusters.
I’ll explore quorum-based and priority-based replication methods, highlighting
their benefits and trade-offs. Additionally, I’ll explain how to adjust the
synchronous_commit setting to strike the right balance between data
durability and performance.
In this article, I’ll explore how Kubernetes and CloudNativePG can be leveraged to streamline the testing of PostgreSQL patches, especially during a Commitfest. By automating the creation of PostgreSQL container images from any public Git repository, developers and reviewers can quickly and efficiently test patches within a Kubernetes environment. This approach not only saves time but also enhances the reliability of patches before integration into the main codebase.
In this article, I’ll introduce you to the new service template feature in
CloudNativePG 1.24, which greatly simplifies the creation of services such as
LoadBalancer to expose PostgreSQL outside of your Kubernetes cluster -
particularly useful for streamlining Database-as-a-Service (DBaaS) deployments.
I’ll walk you through setting up this feature on your laptop using kind and
cloud-provider-kind, ensuring you can easily test and implement these
capabilities in your own environment.
In modern Kubernetes environments, isolating PostgreSQL workloads is crucial for ensuring stability, security, and performance. This article, building on the previous CNPG Recipe #10, explores advanced techniques for isolating PostgreSQL instances using Kubernetes with Kind. By applying taints, labels, and anti-affinity rules, you can ensure that PostgreSQL nodes are dedicated exclusively to database workloads, preventing overlap with other services and enhancing fault tolerance. Whether you’re simulating a production environment or managing a live deployment, these strategies will help you maintain a robust and isolated PostgreSQL cluster in Kubernetes.
This article provides a step-by-step guide to deploying PostgreSQL in
Kubernetes using the kind tool (Kubernetes IN Docker) on a local machine,
simulating a production-like environment. It explains how to create multi-node
clusters and use node labels, specifically proposing the
node-role.kubernetes.io/postgres label to designate PostgreSQL nodes. The
article also demonstrates how to schedule PostgreSQL instances on these
designated nodes, emphasizing the importance of workload isolation in
Kubernetes environments. Thanks to Kubernetes’ portability, these
recommendations apply to any cloud deployment—whether private, public,
self-managed, or fully managed.
As Kubernetes celebrates its tenth anniversary, the integration of PostgreSQL within this ecosystem is gaining momentum, offering challenges and opportunities, rather than threats, for database administrators (DBAs). This article explores the evolution of running PostgreSQL in Kubernetes, emphasising the importance of transitioning from traditional deployment methods to a cloud-native approach. It discusses the need for DBAs to expand their skills beyond the traditional scope, advocating for a “T-shaped” or even “comb-shaped” professional profile. By understanding key Kubernetes concepts and embracing the principles of “slowification”, simplification, and amplification, DBAs can effectively collaborate with developers and infrastructure teams. This approach enhances individual expertise and contributes to the broader adoption and optimisation of PostgreSQL in Kubernetes environments. The article highlights the critical role of community and shared knowledge in breaking down silos and fostering a collaborative culture, which is essential for the successful deployment and management of PostgreSQL in modern cloud-native infrastructures.