Make blocked-metrics nginx resources configurable

[Copilot]

The blocked-metrics deployment has hardcoded resource limits (32Mi memory) causing OOMKilled crashes in production environments. Users currently work around this with Kustomize patches.

Changes

• values.yaml: Add blockedMetrics.resources section with existing hardcoded values as defaults
• blocked-metrics-deployment.yaml: Replace hardcoded resources with template reference to .Values.blockedMetrics.resources

Usage

Override in values.yaml to prevent OOM crashes:

blockedMetrics:
  resources:
    limits:
      memory: 128Mi

Defaults remain unchanged (32Mi limit) for backward compatibility.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• charts.min.io
  • Triggering command: /usr/local/bin/helm helm dependency build (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Hardcoded low memory limit (32Mi) for blocked-metrics nginx container causes OOM loop</issue_title>
<issue_description>### Description

In the blocked-metrics-deployment.yaml template (chart version 0.40.2), the nginx container has hardcoded resource limits:

        resources:
          requests:
            cpu: 10m
            memory: 16Mi
          limits:
            cpu: 50m
            memory: 32Mi

These values are not configurable via values.yaml.

Problem

In our environment, the nginx container consistently exceeds the 32Mi memory limit, causing it to crash with OOMKilled and enter a CrashLoopBackOff state.

Workaround

We are currently using a Kustomize patch to increase the limit to 128Mi, which stabilized the deployment.

Suggestion

Please expose the resource configuration for the blocked-metrics component in values.yaml, similar to other components like ingester or querier.

Example desired values.yaml structure:

blockedMetrics:
  resources:
    limits:
      memory: 128Mi
```</issue_description>

## Comments on the Issue (you are @copilot in this section)

<comments>
</comments>

• Fixes Hardcoded low memory limit (32Mi) for blocked-metrics nginx container causes OOM loop #183

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.