You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure where the right repo for this issue would be, so I am filing it here, as we encountered the problem while trying to get the operator to work.
Describe the bug
Postgres version 15 sends/requires SNI Headers which lower versions to not send. This leads to a host of different errors and renders the operator unusable for us.
Expected behavior
There should exist an up-to-date version of the quay.io pgbench image. The current latest image uses the postgres 11 package, which is EOL since last year. I would have liked to provide a fix directly to the repo where the image is built but was unable to find it...
Additional context
We are trying to benchmark/monitor/debug our postgres installation in an azure/aks cloud
The text was updated successfully, but these errors were encountered:
Ummm I can do that, but as stated I dont know where the image is coming from (I dont think it is in this repository). Can you give me some direction on where this https://quay.io/repository/cloud-bulldozer/pgbench image is getting built from? Then I can take a look.
I am not sure where the right repo for this issue would be, so I am filing it here, as we encountered the problem while trying to get the operator to work.
Describe the bug
Postgres version 15 sends/requires SNI Headers which lower versions to not send. This leads to a host of different errors and renders the operator unusable for us.
Expected behavior
There should exist an up-to-date version of the quay.io pgbench image. The current latest image uses the postgres 11 package, which is EOL since last year. I would have liked to provide a fix directly to the repo where the image is built but was unable to find it...
Additional context
We are trying to benchmark/monitor/debug our postgres installation in an azure/aks cloud
The text was updated successfully, but these errors were encountered: