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
we already tried the newest version of the operator 1.15, it has the exact same behaviour, it alwas uses 16gb ram, we can not get it to fit a size for a small db, we want that it uses max 2gb ram because its only a test database which definitely does not need 16gb ram x3
Report
cr:
we already tried the newest version of the operator 1.15, it has the exact same behaviour, it alwas uses 16gb ram, we can not get it to fit a size for a small db, we want that it uses max 2gb ram because its only a test database which definitely does not need 16gb ram x3
when we add
it just gets oomkilled because it wants to use again 16gb of memory.
More about the problem
expected behaviour: no oomkill
Steps to reproduce
Versions
Anything else?
No response
The text was updated successfully, but these errors were encountered: