Hello,
we are currently facing issues where our agent pods (created when build order triggers its creation) get killed with reason being OOM.
This can be fixed by setting memory limit to 3072.
However, this setting only persists to next restart of Jenkins, then its back to its default value of 1024.
Furthermore, memory limit value is not even taken from helm values.yaml, which we are using to install the jenkins (it gets ignored)
Please advise
Originally reported by vcimburek, imported from: Kubernetes plugin doesnt save memory limits
- status: Open
- priority: Major
- component(s): kubernetes-plugin
- label(s): kubernetes, kubernetes-plugin, limit, memory
- resolution: Unresolved
- votes: 1
- watchers: 2
- imported: 2025-12-02
Raw content of original issue
Hello,
we are currently facing issues where our agent pods (created when build order triggers its creation) get killed with reason being OOM.
This can be fixed by setting memory limit to 3072.
However, this setting only persists to next restart of Jenkins, then its back to its default value of 1024.
Furthermore, memory limit value is not even taken from helm values.yaml, which we are using to install the jenkins (it gets ignored)
Please advise
- environment:
Jenkins 2.516.3, running on Kubernetes
Hello,
we are currently facing issues where our agent pods (created when build order triggers its creation) get killed with reason being OOM.
This can be fixed by setting memory limit to 3072.
However, this setting only persists to next restart of Jenkins, then its back to its default value of 1024.
Furthermore, memory limit value is not even taken from helm values.yaml, which we are using to install the jenkins (it gets ignored)
Please advise
Originally reported by vcimburek, imported from: Kubernetes plugin doesnt save memory limits
Raw content of original issue
Jenkins 2.516.3, running on Kubernetes