Closed Richard87 closed 1 year ago
The pod is trying to execute set ulimit, but is not allowed to, is this a bug?
set ulimit
Should ulimit be called, and if so, should the pod be configured to have the capability?
Clone of this closed issue: https://github.com/zalando/spilo/issues/881
I added this to the helm chart, but it had no effect:
securityContext: capabilities: add: - CAP_SYS_RESOURCE
To fix it I had to manually edit the statefulset and delete the db-pod...
But, Will this be reset when the operator reconcile the statefulset in the future?
Your pod's configuration has nothing to do with Spilo. You maybe want to create this issue in the operator repo.
The pod is trying to execute
set ulimit
, but is not allowed to, is this a bug?Should ulimit be called, and if so, should the pod be configured to have the capability?
Clone of this closed issue: https://github.com/zalando/spilo/issues/881
I added this to the helm chart, but it had no effect:
To fix it I had to manually edit the statefulset and delete the db-pod...
But, Will this be reset when the operator reconcile the statefulset in the future?