May you share configs for with disable ssl connection to databases?

[Dixon3]

I tried to deploy perforator in closed perimeter and there we have issue to have ssl on pg, click interfaces eanbled.

But i unable to manage correct params for perforator binaries it try to ssl first and fail.

[tangyatsu]

If I understand correctly, you're running ClickHouse and PostgreSQL databases without SSL support, and you want the Perforator deployment to communicate with these databases over plain HTTP. Unfortunately, that's currently impossible for ClickHouse—you need to have SSL enabled. One workaround is to generate a self-signed certificate and skip CA verification using the databases.clickhouse.insecure field. For PostgreSQL, you can disable SSL by setting databases.postgresql.sslmode to "disable."

[MikailBag]

(Reopening until we make a release)

[Dixon3]

Great, looks like what required.

PG also requred to have string like:
where sslmode should correspond to https://www.postgresql.org/docs/current/libpq-ssl.html Table 32.1. SSL Mode Descriptions

databases:
  postgresql:
    # Postgresql endpoints.
    endpoints:
     - host: "pg-patroni.postgresql"
       port: 5432
    # SSLmode for client connection.
    sslmode: "disable"
    # Data base name.
    db: "perforator"
    # User base name.
    user: "postgres"
    # Passwords for postgresql data base
    password: "paSSw0rd"
    # Name of existing Secret to use. Used when password is empty.
    # secretName: null
    # Key in Secret to get password from.
    #secretKey: null

[apolik]

I found an easy solution for Clickhouse. I deployed it using this helm chart https://artifacthub.io/packages/helm/bitnami/clickhouse

1. Generate a self-signed certificate for Clickhouse

values.yaml:

...
tls:
  enabled: true
  autoGenerated: 
    enabled: true

2. Set insecure flag and make sure you're connecting to a secure port (9440 in my case)

values.yaml:

...
clickhouse:
  replicas:
    - "<clickhouse-service>.<clickhouse-namespace>.svc.cluster.local:9440"
  insecure: true

[tangyatsu]

@apolik , Yeah, we have a separate perforator-dev chart that configures PostgreSQL, ClickHouse, and MinIO in a similar way to what you proposed. You can find it here:
https://github.com/yandex/perforator/blob/main/perforator/deploy/kubernetes/helm/perforator-dev/values.yaml

We've also have a tutorial on setting up a Perforator test deployment with these databases:
https://perforator.tech/docs/en/tutorials/kubernetes/helm-chart