Increase memory limits for Flux notification controller
General MR
Summary
From dogfood the lower limits were causing consistent OOM crashes. Doubling the memory limits makes everything work.
I believe this change is required as a result of https://repo1.dso.mil/platform-one/big-bang/bigbang/-/merge_requests/1896 - with the increased actions from the notification controller it requires more memory (especially on a large cluster with all packages deployed).
Merge request reports
Activity
changed milestone to %1.41.0
added cherrypick flux statusreview labels
assigned to @micah.nagel
enabled an automatic merge when the pipeline for 462ede48 succeeds
mentioned in commit f8ceda59
picked the changes into the branch
release-1.41.x
with commit 628e1592mentioned in commit 628e1592
Please register or sign in to reply