---
title: How To Reinitialize PostgreSQL (Swimlane)
slug: install-10x/how-to-reinitialize-postgresql-swimlane
docTags: 
createdAt: 2025-12-09T17:22:34.878Z
---

Problem: The PostgreSQL deployment is broken, causing application pods like swimlane-tasks and swimlane-api to crash.

Solution: Reintialize the PostgreSQL cluster.

1. The PostgreSQL cluster is in an unhealthy state, similar to the indication below:

:::BlockQuote{indent="1"}
$ kubectl exec -it postgresql-0 -- patronictl list
:::

![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/8154056337/original/JTQw_OzLabYsXwBUijkG3on9GPwhStPowA.png?1761246808)

2. Completely remove the broken Kubernetes postgresql custom resource definition. This step may take up to 10 minutes to fully complete depending on the cluster state:

:::BlockQuote{indent="1"}
$ kubectl get postgresql postgresql
NAME TEAM VERSION PODS VOLUME CPU-REQUEST MEMORY-REQUEST AGE STATUS
postgresql swimlane 14 1 8Gi 16m Running

$ kubectl delete postgresql postgresql 
postgresql.acid.zalan.do "postgresql" deleted

$ kubectl delete endpoints postgresql-config
$ kubectl delete svc postgresql-config
:::

3. Reapply the KOTS deployment by clicking on the "Redeploy" button in the Admin Console:

![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/8154056130/original/J7IB78YRsNjcXphodsc4OH1EfU47zOuxUw.png?1761246581)

4. Restart all Swimlane application pods:

:::BlockQuote
$ kubectl delete pod -l app.kubernetes.io/name=swimlane
pod "gotenberg-6df9b986b8-vv6sr" deleted
pod "swimlane-api-564ff576bd-qckxc" deleted
pod "swimlane-reports-584bb577bf-ps9hn" deleted
pod "swimlane-tasks-9fcd9bfc7-5jbsd" deleted
pod "swimlane-tools-0" deleted
pod "swimlane-web-786866b48d-lfcql" deleted
:::

5. Now the PostgreSQL cluster should be healthy:

![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/8154056415/original/EUp3JYn6u7Vgh7Z0pvMuDS3WIMCZrLiMew.png?1761246901)