After taking a closer look at the issue, it seems like you bumped into an old issue that’s impacting our PG operator.
This forum post has a more detailed explanation of the issue and a couple of workarounds that worked for some users. However, I think you may have limited success trying these workarounds with Everest.
We have escalated this issue to our cloud team which will do a deeper investigation and will try to work on a fix in one of the upcoming PG operator releases.
We’ll report back when an eventual fix is part of Everest.