# PMM Server 3.2.0 on Kubernetes: Auto-Logout/Unauthorized Error with Multiple Replicas **URL:** \ **Category:** Percona Monitoring and Management (PMM)\ **Tags:** pmm, kubernetes\ **Created:** [November 3, 2025, 12:03pm UTC](https://forums.percona.com/t/pmm-server-3-2-0-on-kubernetes-auto-logout-unauthorized-error-with-multiple-replicas/39677 "2025-11-03T12:03:58Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![pravata\_dash](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/pravata_dash/32/12098_2.png) [@pravata\_dash](https://forums.percona.com/u/pravata_dash)\ **Post date:** [November 3, 2025, 12:03pm UTC](https://forums.percona.com/t/pmm-server-3-2-0-on-kubernetes-auto-logout-unauthorized-error-with-multiple-replicas/39677/1 "2025-11-03T12:03:58Z")
## Hello Percona Community, I am setting up a PMM Server (version 3.2.0) deployment in my local Kubernetes environment (running on macOS) using the official Percona Helm chart. ### The Setup - **PMM Version:** 3.2.0 (using official Helm chart) - **Environment:** Local Kubernetes (on macOS, orbstack) - **Client:** Successfully pushing metrics from local MySQL instance. ### The Problem (Replication Issue) When I configure the StatefulSet with **`replicas: 1`** , everything works perfectly: the Pod starts, I can log into the PMM UI, and client metrics are displayed. However, when I increase the replica count to **`replicas: 3`** , all three Pods come up successfully. But upon attempting to log into the PMM UI (accessed via the service), its logging in I am able to access the UI, but after few seconds OR sometimes **instantaneously logged out** with an “Unauthorized” error popup. It appears to be an immediate session invalidation or redirect loop triggered post-login. ### The Core Question This behavior strongly suggests an issue with session management or state synchronization between the multiple Pods. 1. **What is the specific relationship between PMM Server’s login/session mechanism and the number of replicas that could cause this “Unauthorized” auto-logout error?** Does PMM require a specific shared storage or configuration for session handling in a multi-replica setup that is not handled automatically by the Helm chart’s default StatefulSet configuration? 2. How is PMM High Availability (HA) fundamentally designed to work in a Kubernetes environment? Is the goal of increasing replicas in the StatefulSet to simply avoid an **SPOF (Single Point of Failure)**, or is there a specific requirement for leader election/clustering that needs additional configuration? 3. Will a Pod failure be automatically handled if I increase the replica count, or does the PMM architecture require external components (like a specific database/store) to manage state across Pods for true HA? Any insights into how PMM manages state and sessions across multiple Kubernetes replicas would be greatly appreciated. Thank you! ![Screenshot 2025-11-03 at 5.38.14 PM](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/7/4/7430dc884b761a8278269ebab4ba67380e849d37.png) ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [November 3, 2025, 7:34pm UTC](https://forums.percona.com/t/pmm-server-3-2-0-on-kubernetes-auto-logout-unauthorized-error-with-multiple-replicas/39677/2 "2025-11-03T19:34:59Z")
Hey @pravata_dash, It says on our documentation: > Only one replica set is currently supported for PMM Server on Kubernetes. > **[Percona Monitoring and Management - Back up PMM Server Helm deployment](https://docs.percona.com/percona-monitoring-and-management/3/install-pmm/install-pmm-server/deployment-options/helm/backup_container_helm.html)** > > Create backups of your PMM Server Kubernetes deployment to protect your monitoring data and configuration. Cheers! ---
**Author:** ![pravata\_dash](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/pravata_dash/32/12098_2.png) [@pravata\_dash](https://forums.percona.com/u/pravata_dash)\ **Post date:** [November 4, 2025, 10:21am UTC](https://forums.percona.com/t/pmm-server-3-2-0-on-kubernetes-auto-logout-unauthorized-error-with-multiple-replicas/39677/3 "2025-11-04T10:21:32Z")
Thanks for confirming @matthewb . Any idea when the clustered solution will be released? > **[Percona Monitoring and Management - Install PMM in HA mode](https://docs.percona.com/percona-monitoring-and-management/3/install-pmm/HA.html#what-pmm-ha-cannot-solve)** > > When your database monitoring goes down, you lose visibility into critical performance issues just when you need it most. HA ensures your PMM monitoring stays online even when servers fail, networks disconnect, or hardware breaks. ![Screenshot 2025-11-04 at 3.48.32 PM](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/e/3/e3bdac2aeddc810f717c42714d8513b4e2d3b5bf.png) ---
**Author:** ![ademidoff](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ademidoff/32/14234_2.png) [@ademidoff](https://forums.percona.com/u/ademidoff)\ **Post date:** [November 4, 2025, 10:44am UTC](https://forums.percona.com/t/pmm-server-3-2-0-on-kubernetes-auto-logout-unauthorized-error-with-multiple-replicas/39677/4 "2025-11-04T10:44:38Z")
Hi, We are targeting end of Q4 2025. ---
**Author:** ![pravata\_dash](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/pravata_dash/32/12098_2.png) [@pravata\_dash](https://forums.percona.com/u/pravata_dash)\ **Post date:** [November 4, 2025, 6:24pm UTC](https://forums.percona.com/t/pmm-server-3-2-0-on-kubernetes-auto-logout-unauthorized-error-with-multiple-replicas/39677/5 "2025-11-04T18:24:56Z")
Thanks for the reply.