fix: increase quay-s3-credentials-setup job memory limit to 512Mi

The default 256Mi limit from the quay chart causes OOMKilled when the
job runs oc apply to create the quay-config-with-s3 secret. Add the
override to values-hub.yaml (commented quay-registry section) and to
the feature fragments (quay.yaml, registry/option-1-quay.yaml).

Author: minmzzhang

scripts/features/quay.yaml

@@ -25,3 +25,8 @@ clusterGroup:
       chartVersion: 0.1.*
       annotations:
         argocd.argoproj.io/sync-wave: "41"
+      overrides:
+      - name: job.image
+        value: "registry.redhat.io/openshift4/ose-cli:latest"
+      - name: job.resources.limits.memory
+        value: "512Mi"

scripts/features/registry/option-1-quay.yaml

@@ -41,6 +41,8 @@ clusterGroup:
       overrides:
         - name: job.image
           value: "registry.redhat.io/openshift4/ose-cli:latest"
+        - name: job.resources.limits.memory
+          value: "512Mi"
 
   merge_into_applications:
     supply-chain:

values-hub.yaml

@@ -401,6 +401,11 @@ clusterGroup:
     #   chartVersion: 0.1.*
     #   annotations:
     #     argocd.argoproj.io/sync-wave: "41"  # Deploy after NooBaa storage backend
+    #   overrides:
+    #   - name: job.image
+    #     value: "registry.redhat.io/openshift4/ose-cli:latest"
+    #   - name: job.resources.limits.memory
+    #     value: "512Mi"
     # RHTAS with SPIFFE Integration
     # COMMENTED OUT: Uncomment to enable RHTAS with SPIFFE and Email issuers
     # Depends on: Vault, SPIRE, Keycloak (for Email OIDC issuer if used)