Edmondo Porcu

12/11/2022, 2:23 PM
Hello, does anyone use Prefect Helm Chart? I think I have this problem but I am not sure I understood the solution

Jamie Zieziula

12/11/2022, 2:26 PM
Hi Edmondo! Can you see if you have an persistent volume / claims that predate your existing helm chart install?

Edmondo Porcu

12/11/2022, 2:33 PM
Hi @Jamie Zieziula 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   <none>        4200/TCP   16m
service/prefect-orion-postgresql      ClusterIP    <none>        5432/TCP   16m
service/prefect-orion-postgresql-hl   ClusterIP   None            <none>        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

Jamie Zieziula

12/11/2022, 3:09 PM
can you run: kubectl get pv -n your-namespace kubectl get pvc -n your-namespace

Edmondo Porcu

12/11/2022, 9:53 PM
there are none
this is a kubernetes get all
We fixed it like so:
helm upgrade --install prefect prefect/prefect-orion --namespace prefect --set postgresql.auth.password=password
:gratitude-thank-you: 1
🙌 1

Anna Geller

12/13/2022, 1:14 PM
nice work, thanks for the update on that, Edmondo!