Set Set cpu/memory requests/limits for tekton-results-api init contai…

…ners Init containers are harder to figure out the required resources as they do not run long enough to have metrics collected. Both container worked with 5m/32Mi in a dev environment. Put the limits higher to make sure they works in production environment even though the nature of the work done by both should not differ from dev to production environment. PLNSRVCE-1476 Signed-off-by: Hugo Arès <[email protected]>
openshift-pipelines · Oct 20, 2023 · 47c14a4 · 47c14a4
1 parent f74b260
commit 47c14a4
Show file tree

Hide file tree

Showing 2 changed files with 14 additions and 0 deletions.
diff --git a/developer/openshift/gitops/argocd/pipeline-service/tekton-results/minio-create-bucket.yaml b/developer/openshift/gitops/argocd/pipeline-service/tekton-results/minio-create-bucket.yaml
@@ -58,6 +58,13 @@ spec:
               subPath: s3-cert.crt
             - name: tmp-mc-volume
               mountPath: /tmp
+          resources:
+            requests:
+              cpu: 5m
+              memory: 32Mi
+            limits:
+              cpu: 100m
+              memory: 128Mi
           securityContext:
             readOnlyRootFilesystem: true
             runAsNonRoot: true

diff --git a/operator/gitops/argocd/pipeline-service/tekton-results/api-migrator-config.yaml b/operator/gitops/argocd/pipeline-service/tekton-results/api-migrator-config.yaml
@@ -34,5 +34,12 @@ spec:
                 secretKeyRef:
                   name: tekton-results-database
                   key: db.name
+          resources:
+            requests:
+              cpu: 5m
+              memory: 32Mi
+            limits:
+              cpu: 100m
+              memory: 128Mi
           securityContext:
             readOnlyRootFilesystem: true