When a Postgres Operator decision is not forever: approaches and experiences for migrating between Postgres Operators
April 21–22
The Postgres ecosystem on Kubernetes is thriving and this is particularly evident in the Postgres K8s Operators space. As the Postgres Operator ecosystem matures, real world experience has shown that, technical, licensing or operational constraints can make it necessary to migrate between PostgreSQL Kubernetes Operators, over the lifecycle of a database platform. In this talk we are going to: • Provide an overview of the Postgres Operator landscape, reviewing widely adopted options such as CloudNativePG, Percona PostgreSQL Operator, Crunchy Data PGO, Zalando Operator, and Bitnami Helm charts. We will compare their key architectural, technological, and licensing choices to help attendees make more informed operator selection decisions. • Examine the reasons why, even after a decision, you might be faced with an operator migration eventually, and the licensing, architectural and operational aspects, risks and opportunities, that you should take into account. • Discuss the different implementation approaches for migrating between Operators, such as replication, backup and volume-based patterns. • Finally, deep dive on a particular Operator migration case study between two popular Postgres K8s operators. By the end of this session, attendees will have a clearer understanding of the PostgreSQL Operator ecosystem, the risks and opportunities associated with an Operator technology switch, and finally, concrete, actionable strategies for planning and executing Postgres Kubernetes Operator technology migrations.