@Marvin I have converted the crt.pem to crt and created the following secrete in the namespace prefect-server will be deployed. "kubectl create secret generic db-ssl-secret --from-file=root.crt=root.crt -n <namespace>" I have this in my value.yaml. server: extraVolumes: - name: db-ssl-secret secret: secretName: db-ssl-secret defaultMode: 384 extraVolumeMounts: - name: db-ssl-secret mountPath: "/home/prefect/.postgresql" readOnly: true postgresql: useSubChart: false auth: existingSecret: prefect-postgres-secret I get this error in the logs of the prefect-server pod. asyncpg.exceptions._base.ClientConfigurationError: root certificate file "/home/prefect/.postgresql/root.crt" does not exist or cannot be accessed HINT: Provide the certificate file directly or make sure "/home/prefect/.postgresql/root.crt" exists and is readable.

It seems there may be a misconfiguration with the Kubernetes volumes setup. Here's what you need to ensure: 1. Make sure that the

db-ssl-secret

Kubernetes secret has been created successfully in the desired namespace with the correct root certificate file (

root.crt

). 2. Confirm the

server.extraVolumeMounts

configuration in your

values.yaml

file for the Prefect Server chart mounts the

db-ssl-secret

to the correct path inside the container which is expected by

asyncpg

. However, I was unable to find a particular solution to the

ClientConfigurationError

regarding the root certificate file not existing or being inaccessible in the Prefect documentation or Prefect GitHub issues. Please double-check the permissions and the file path specified for the secret volume mount and ensure the path matches where

asyncpg

looks for the certificate. If the issue persists, consider reaching out to the Prefect community or opening a GitHub issue for more personalized assistance. Meanwhile, here are some general links to Prefect Documentation that touch on Kubernetes deployment which might be helpful: - Docker Guide for Prefect - Kubernetes Deployment Guide for Prefect Remember to configure your PostgreSQL connection URL appropriately with the relevant SSL parameters, as described in Prefect's documentation on configuring databases. Unfortunately, the GitHub query didn't find any relevant issues, but you may want to search through the Prefect GitHub issues yourself for any similar problems or report a new issue.

ssl.SSLError: [X509: NO_CERTIFICATE_OR_CRL_FOUND] no certificate or crl found (_ssl.c:4149)