---
title: "Issues with automatic kubernetes update"
description: "Resolved · affects API · Oct 1, 2025"
base_url: "https://status.openpanel.dev"
canonical: "https://status.openpanel.dev/events/report/723"
---

# Issues with automatic kubernetes update

[Status](/.md) › [Events](/events.md) › Issues with automatic kubernetes update

Oct 1, 2025 · 10 months ago · affects: API · 1 minute

## Updates

### + Resolved — Oct 1, 7:40 AM

Our api and website was down after a automatic node upgrade on one of our DB nodes. We noticed that we only had one read replica for our DB which caused pgbouncer to throw a connection error while the upgrade was running.

This caused a bunch of issues. 

Steps to improve:
- We'll introduce a much better readiness and liveness for our API, since our API tried to scale (and restart all existing pods) to solve the problem, this just made the issue worse.
- We have increase our instances of the DB from 2 -> 3 to always have 1 read-replica available.
- Have a better plan when automatic upgrades should be triggered

These two changes will improve similar issues in the future.
