HENAFF Brewal

Hi, I couldn't reproduce the problem outside of the helm version. When I tryed to recreate it with a docker environment everything work as expected. The permission check was :...

To add some information on the environment : It's a Kubernetes Cluster with 3 worker nodes. Permify helm as the default replicas number (so 3), so each worker as one...

Hello, I just notice there is a distributed configuration for the cache system. Could this be the cause of the problem ? I'll try to configure it on the cluster...

Hi @tolgaOzen My bad, I forgot to write that was the bitnami helm chart version The postgres version is 15.3 Image : docker.io/bitnami/postgresql:15.3.0-debian-11-r17 So far, since I've activated the distributed...

Hi, I'm adding information to the ticket. I'm working on a test environment, the permify is still the same with the same versions of chart helm. Last night everything was...

Hi @tolgaOzen Of course, here is the config : ```yaml # The logger section sets the logging level for the service. logger: level: debug # The database section specifies the...

We don't have any logs from Permify, they don't logs correctly  For postgres we use the bitnami posgresql chart in version 12.5.9 (corresponding to a postgres 15.3) The database...

@tolgaOzen This is also what I understood from reading the permify code. But the bug only seems to appear when garbage collection is enabled. I will update the chart of...

There was an error on the latest version of the chart helm, I have submitted a PR to fix the problem on the permify helm chart repo.

I've updated to version 0.3.7 of the chart helm. Now the logs work properly. I'll update you if I notice the bug again !