|
| 1 | +--- |
| 2 | +title: "KubeCon NA Atlanta 2025: a recap and CloudNativePG’s path to CNCF Incubation" |
| 3 | +date: 2025-11-26T07:24:27+01:00 |
| 4 | +description: "A recap of my three talks at KubeCon NA Atlanta 2025 detailing CloudNativePG (CNPG) advancements in PostgreSQL on Kubernetes, security integration with Keycloak, and the decision to apply for CNCF Incubation" |
| 5 | +tags: ["postgresql", "postgres", "kubernetes", "k8s", "cloudnativepg", "cnpg", "postgresql", "postgres", "dok", "data on kubernetes", "kubecon", "cncf", "incubation", "multigres"] |
| 6 | +cover: cover.jpg |
| 7 | +thumb: thumb.jpg |
| 8 | +draft: true |
| 9 | +--- |
| 10 | + |
| 11 | +_This blog post recaps my eventful participation in KubeCon + CloudNativeCon |
| 12 | +North America 2025 in Atlanta, highlighting the key decision by maintainers to |
| 13 | +formally apply for CNCF Incubation for the CloudNativePG operator. I had the |
| 14 | +pleasure of delivering three presentations: a CNPG Lightning Talk focused on |
| 15 | +community contribution; a deep-dive with Yoshiyuki Tabata on implementing |
| 16 | +modern PostgreSQL authorisation using Keycloak and OAuth for robust database |
| 17 | +security; and a session with Jeremy Schneider introducing the new quorum-based |
| 18 | +consistency feature in CNPG 1.28 for safer cluster reconfigurations. Links to |
| 19 | +the videos of all three talks are shared within the full article._ |
| 20 | + |
| 21 | +<!--more--> |
| 22 | + |
| 23 | +--- |
| 24 | + |
| 25 | +**KubeCon + CloudNativeCon North America** in Atlanta was a huge success, |
| 26 | +marking my 9th KubeCon since first attending in San Diego back in 2019 |
| 27 | +(a streak thankfully re-established after the COVID interruption). |
| 28 | +It was an honour for me to represent my company, [EDB](https://www.enterprisedb.com/), |
| 29 | +which fully supports our open-source contributions as the highest form of |
| 30 | +innovation in technology. |
| 31 | + |
| 32 | +The event was an unparalleled opportunity to connect with numerous |
| 33 | +practitioners, professionals, and community members dedicated to the CNCF |
| 34 | +ecosystem, as well as CloudNativePG community fellows. I had the pleasure of |
| 35 | +speaking three times across the conference agenda this year. |
| 36 | + |
| 37 | +My primary goal for this participation was to go beyond the usual networking |
| 38 | +and actively engage with relevant **CNCF TOC** and **TAG members** to gauge the |
| 39 | +maturity and placement of **CloudNativePG (CNPG)**. |
| 40 | +We wanted to understand if our community-driven operator was truly in the right |
| 41 | +spot to apply for [**CNCF Incubation**](https://www.cncf.io/project-metrics/). |
| 42 | + |
| 43 | +I am thrilled to share that all of us maintainers decided to take |
| 44 | +the leap right there in Atlanta, submitting our formal application! |
| 45 | + |
| 46 | +You can follow our journey and show your support here: |
| 47 | +[CloudNativePG Application for Incubation](https://github.com/cncf/toc/issues/1961). |
| 48 | + |
| 49 | +## Project Lightning Talk: CloudNativePG, Running PostgreSQL the Kubernetes Way |
| 50 | + |
| 51 | +My first engagement was the [Project Lightning Talk](https://kccncna2025.sched.com/event/27d5y/project-lightning-talk-cloudnativepg-running-postgres-the-kubernetes-way-gabriele-bartolini-maintainer) |
| 52 | +in the CNCF projects event. This 5-minute slot was a fantastic opportunity to |
| 53 | +speak rapidly about **CloudNativePG**. I was pleased to see many attendees in |
| 54 | +the audience who not only use **Postgres in Kubernetes** but were already |
| 55 | +familiar with **CNPG**. |
| 56 | + |
| 57 | +The main message I conveyed was simple: join our vendor-neutral community! |
| 58 | +Contributions are vital, and even a simple act can help immensely—for instance, |
| 59 | +adding your **organisation** to the [`ADOPTERS.md` file](https://github.com/cloudnative-pg/cloudnative-pg/blob/main/ADOPTERS.md) |
| 60 | +helps us cross the chasm and strengthen our incubation application. |
| 61 | + |
| 62 | + |
| 63 | + |
| 64 | +We are a rapidly growing project, and I emphasised the diversity of contribution opportunities: |
| 65 | + |
| 66 | +> CloudNativePG is over 15 projects! You can become a contributor and owner of |
| 67 | +> our Helm charts, our Grafana dashboards, our container images, or our |
| 68 | +> metrics. |
| 69 | +
|
| 70 | +*Watch the recording: [Project Lightning Talk CloudNativePG](https://www.youtube.com/watch%3Fv%3DpYwYwehQX3U)* |
| 71 | + |
| 72 | +----- |
| 73 | + |
| 74 | +## Modern PostgreSQL Authorisation with Keycloak: Cloud Native Identity Meets Database Security |
| 75 | + |
| 76 | +The [second presentation](https://kccncna2025.sched.com/event/27FXv/modern-postgresql-authorization-with-keycloak-cloud-native-identity-meets-database-security-yoshiyuki-tabata-hitachi-ltd-gabriele-bartolini-edb) |
| 77 | +was a joint talk with **Yoshiyuki Tabata** of Hitachi, focusing on a critical |
| 78 | +security modernisation topic. |
| 79 | + |
| 80 | +The session tackled the obsolescence and inherent security risks of relying on |
| 81 | +static credentials (usernames and passwords) for database access in dynamic, |
| 82 | +multi-tenant cloud-native environments. We showed how traditional database |
| 83 | +authentication methods no longer meet modern security and compliance demands. |
| 84 | + |
| 85 | +We walked the audience through the solution: integrating **PostgreSQL |
| 86 | +authorisation with Keycloak**, an Identity and Access Management (IAM) |
| 87 | +open-source solution. The core concept is **externalising authentication and |
| 88 | +authorisation logic** from the database to enable centralised identity control |
| 89 | +across services. We demonstrated how to securely map Keycloak roles and groups |
| 90 | +directly to PostgreSQL privileges and enforce fine-grained access policies, all |
| 91 | +managed seamlessly in Kubernetes environments using **CloudNativePG**. |
| 92 | +We also touched upon how the innovative native OAuth support in PostgreSQL 18 |
| 93 | +has the potential to fundamentally transform database authentication, not only |
| 94 | +in Kubernetes. For those interested in this cutting-edge approach, we also |
| 95 | +launched our experimental project, the **Postgres Keycloak OAuth Validator**, |
| 96 | +which you can find here: |
| 97 | +[cloudnative-pg/postgres-keycloak-oauth-validator](https://github.com/cloudnative-pg/postgres-keycloak-oauth-validator). |
| 98 | + |
| 99 | +*Watch the recording: [Modern PostgreSQL Authorisation With Keycloak](https://www.youtube.com/watch?v=TYgPemq06fg)* |
| 100 | + |
| 101 | +----- |
| 102 | + |
| 103 | +## Quorum-Based Consistency for Cluster Changes with CloudNativePG Operator |
| 104 | + |
| 105 | +My [final talk](https://kccncna2025.sched.com/event/27FfQ/quorum-based-consistency-for-cluster-changes-with-cloudnativepg-operator-jeremy-schneider-geico-tech-gabriele-bartolini-edb), |
| 106 | +delivered alongside **Jeremy Schneider** of GEICO Tech, focused on a major new |
| 107 | +feature introduced in **CloudNativePG 1.28**: **failover quorum** for cluster |
| 108 | +changes. |
| 109 | + |
| 110 | +This talk was originally submitted by Leonardo Cecchi, and I had the honour of |
| 111 | +stepping in for him last minute after he had to bow out for family reasons. We |
| 112 | +explored how the concept of **quorum consistency** can be applied to cluster |
| 113 | +reconfigurations in a single-writer database like PostgreSQL. |
| 114 | + |
| 115 | +We demonstrated how the **CNPG operator** uses this theory to maintain safety |
| 116 | +and avoid data loss during complex operations. Specifically, we detailed how |
| 117 | +this feature provides **quorum-based consistency** for critical stateful |
| 118 | +operator actions (like scaling and switchover). |
| 119 | + |
| 120 | +Achieving this requires very careful end-to-end coordination between the |
| 121 | +control plane and data plane algorithms—a necessity for achieving **Level V |
| 122 | +capabilities** for stateful operators on Kubernetes—ultimately providing |
| 123 | +reliable auto-healing under compounded failures or network partitions. We were |
| 124 | +pleased to share lessons and insights useful for maintainers of other |
| 125 | +Kubernetes operators for stateful workloads. |
| 126 | + |
| 127 | +*Watch the recording: [Quorum-Based Consistency for Cluster Changes with CloudNativePG Operator](https://www.youtube.com/watch?v=iQUOO3-JRK4)* |
| 128 | + |
| 129 | +----- |
| 130 | + |
| 131 | +## Conclusion |
| 132 | + |
| 133 | +**KubeCon NA Atlanta** was a pivotal event for the entire **CloudNativePG** |
| 134 | +community. The engagement and positive feedback were overwhelming, and the |
| 135 | +decision to officially apply for **CNCF Incubation** with CloudNativePG marked |
| 136 | +a true high point. |
| 137 | + |
| 138 | +Another memorable moment was participating in the [KubeJam](https://kubejam.com/) |
| 139 | +event organised by [Testkube](https://testkube.io). |
| 140 | + |
| 141 | + |
| 142 | + |
| 143 | +Now, we look forward to the next major event in Europe, and I can't wait to see |
| 144 | +you all at [KubeCon + CloudNativeCon Europe in Amsterdam](https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/), |
| 145 | +hopefully with CloudNativePG proudly holding Incubation status! |
| 146 | + |
| 147 | +--- |
| 148 | + |
| 149 | +Stay tuned for the upcoming recipes! For the latest updates, consider |
| 150 | +subscribing to my [LinkedIn](https://www.linkedin.com/in/gbartolini/) and |
| 151 | +[Twitter](https://twitter.com/_GBartolini_) channels. |
| 152 | + |
| 153 | +If you found this article informative, feel free to share it within your |
| 154 | +network on social media using the provided links below. Your support is |
| 155 | +immensely appreciated! |
| 156 | + |
| 157 | +<!-- |
| 158 | +_Cover Picture: [“TITLE“](URL)._ |
| 159 | +--> |
| 160 | + |
0 commit comments