Thanks David. Then we may have to look more into the part where we do the curl request and also verify any bug with kernel causing this memory issue.
have you found a solution for that problem?
We have the same issue with https.
Our settings are close:
I think the RSS from the java process is not the problem.
But i don´t know why the node mem limit is reached.
2137989120 and growing
My workaround for this problem is change readinessprobe
- name: Authorization
value: Basic [base64 encoded user:pw]
This seem to be an issue caused by Centos kernel bug.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.