Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Hello, does anyone use Prefect Helm Chart? <https://github.com/PrefectHQ/prefect-helm#the-database-deploys-correctly-but-other-services-fail-with-bad-password> I think I have this problem but I am not sure I understood the solution

Hi Edmondo! Can you see if you have an persistent volume / claims that predate your existing helm chart install?

Hi <@U02L949MUGM> this is what I see in the namespace

```NAME                                 READY   STATUS             RESTARTS        AGE
pod/prefect-orion-54d75b54dc-lsnxt   0/1     CrashLoopBackOff   7 (4m17s ago)   16m
pod/prefect-orion-postgresql-0       1/1     Running            0               16m

NAME                                  TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
service/prefect-orion                 ClusterIP   10.101.15.192   &lt;none&gt;        4200/TCP   16m
service/prefect-orion-postgresql      ClusterIP   10.101.8.197    &lt;none&gt;        5432/TCP   16m
service/prefect-orion-postgresql-hl   ClusterIP   None            &lt;none&gt;        5432/TCP   16m

NAME                            READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/prefect-orion   0/1     1            0           16m

NAME                                       DESIRED   CURRENT   READY   AGE
replicaset.apps/prefect-orion-54d75b54dc   1         1         0       16m

NAME                                        READY   AGE
statefulset.apps/prefect-orion-postgresql   1/1     16m```

can you run:
kubectl get pv -n your-namespace
kubectl get pvc -n your-namespace 

We fixed it like so:

```helm upgrade --install prefect prefect/prefect-orion --namespace prefect --set postgresql.auth.password=password```

nice work, thanks for the update on that, Edmondo!