OCPBUGS-58324: podman-etcd Add OOM score adjustment for etcd containers #2060
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change introduces a new
oom
parameter to thepodman-etcd
OCF agent. This allows tuning the Out-Of-Memory (OOM) score adjustment for the etcd container.The
oom
parameter accepts integer values from -1000 to 1000, defaulting to -997 (system-node-critical equivalent).see https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#node-out-of-memory-behavior
Key changes:
OCF_RESKEY_oom
parameter to agent definition (content type="integer"
).--oom-score-adj
option intopodman_start()
.oom
inpodman_validate()
, ensuring values are within the [-1000:1000] range.