BK
BK
THANK YOU
> I think corporate proxy causes this issue. I rebuilt the docker image by setting proxy and it worked. Guess what? Now Kubernetes API requests are failing with TLS handshake...
same issue the official tap repo didn't work
I create a config.yaml to my homefolder ~/.medusa/config.yaml but it looks like read my conf however it works fine with environment.
Same issue too
Hello, I solve my issue. I used Helm chart version with 2 replicas for each pod. I scale down to 1 and the issue gone.
For people who have a problem , we have on our side changed all the pods to replicas=1 and that solved our problem.
Any update with this issue ? we have the error
same issue for me with pgpool:4.5.1-debian-12-r0 downgrade to 4.5.0-debian-12-r10 to fix
> Thank you very much for your feedback @BK-STAR77! > > The container logic has not received any change from 4.5.0 to 4.5.1 that could cause this behavior. Checking [pgpool...