From 33340b5b1cde245e1bfd96374c3eb0f0348aaa1e Mon Sep 17 00:00:00 2001
From: Gabe Montero <gmontero@redhat.com>
Date: Thu, 18 Jan 2024 12:34:18 -0500
Subject: [PATCH] bump results watcher watcher container to 3Gi (#3093)

Over the course of about a week we have seen the results watcher on prd-rh01  have to OOM about once a day.  During the day, we have observed garbage collection, and seen mem usage go up and down some.  But as prd-rh01 is our most used cluster, it is the one that has bumped into the 2Gi limit too often.  The other 3 clusters, while still having activity, have not observed leak behavior.  We have engaged upstream with some profiling data from our personal clusters to see if there is some sort of edge case.  But the simpler step first step to bump prod, and then continue to monitor, and see if we have just hit a new limit with more onboarding.
---
 .../production/base/bump-results-watcher-mem.yaml            | 4 ++++
 .../pipeline-service/production/base/kustomization.yaml      | 5 +++++
 .../pipeline-service/production/stone-prd-m01/deploy.yaml    | 2 +-
 .../pipeline-service/production/stone-prd-rh01/deploy.yaml   | 2 +-
 4 files changed, 11 insertions(+), 2 deletions(-)
 create mode 100644 components/pipeline-service/production/base/bump-results-watcher-mem.yaml

diff --git a/components/pipeline-service/production/base/bump-results-watcher-mem.yaml b/components/pipeline-service/production/base/bump-results-watcher-mem.yaml
new file mode 100644
index 00000000000..0e80093b1dc
--- /dev/null
+++ b/components/pipeline-service/production/base/bump-results-watcher-mem.yaml
@@ -0,0 +1,4 @@
+---
+- op: replace
+  path: /spec/template/spec/containers/1/resources/limits/memory
+  value: "3Gi"
\ No newline at end of file
diff --git a/components/pipeline-service/production/base/kustomization.yaml b/components/pipeline-service/production/base/kustomization.yaml
index e8516f8d372..a326c1dc6cb 100644
--- a/components/pipeline-service/production/base/kustomization.yaml
+++ b/components/pipeline-service/production/base/kustomization.yaml
@@ -25,6 +25,11 @@ patches:
       kind: Deployment
       name: pipeline-metrics-exporter
       namespace: openshift-pipelines
+  - path: bump-results-watcher-mem.yaml
+    target:
+      kind: Deployment
+      namespace: tekton-results
+      name: tekton-results-watcher
   - path: update-tekton-config-pac.yaml
     target:
       kind: TektonConfig
diff --git a/components/pipeline-service/production/stone-prd-m01/deploy.yaml b/components/pipeline-service/production/stone-prd-m01/deploy.yaml
index e3502cdb3e6..491bfd3cb76 100644
--- a/components/pipeline-service/production/stone-prd-m01/deploy.yaml
+++ b/components/pipeline-service/production/stone-prd-m01/deploy.yaml
@@ -1514,7 +1514,7 @@ spec:
         resources:
           limits:
             cpu: 250m
-            memory: 2Gi
+            memory: 3Gi
           requests:
             cpu: 100m
             memory: 64Mi
diff --git a/components/pipeline-service/production/stone-prd-rh01/deploy.yaml b/components/pipeline-service/production/stone-prd-rh01/deploy.yaml
index 0c9e74a8728..d802f90c132 100644
--- a/components/pipeline-service/production/stone-prd-rh01/deploy.yaml
+++ b/components/pipeline-service/production/stone-prd-rh01/deploy.yaml
@@ -1514,7 +1514,7 @@ spec:
         resources:
           limits:
             cpu: 250m
-            memory: 2Gi
+            memory: 3Gi
           requests:
             cpu: 100m
             memory: 64Mi