Fix middleware reference conditions in Traefik IngressRoute

[Copilot]

The IngressRoute unconditionally referenced optional middlewares that are only created when specific configuration keys exist, causing deployment failures when those keys are missing.

Changes

• IngressRoute middleware references: Added hasKey guards for optional middlewares (ipAllowList, buffering, noindex) to match their creation conditions
• noindex middleware creation: Changed condition from .Values.ingress to .Values.ingress.enabled for consistency with other middlewares

Example

Before:

middlewares:
  - name: {{ include "laravel.fullname" $ }}-forwarded-headers
  {{- if $.Values.ingress.ipAllowList.enabled }}
  - name: {{ include "laravel.fullname" $ }}-ip-allowlist
  {{- end }}

After:

middlewares:
  - name: {{ include "laravel.fullname" $ }}-forwarded-headers
  {{- if and (hasKey $.Values.ingress "ipAllowList") $.Values.ingress.ipAllowList.enabled }}
  - name: {{ include "laravel.fullname" $ }}-ip-allowlist
  {{- end }}

Middleware references now align with their creation conditions, preventing references to non-existent resources.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

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.bitnami.com
  • Triggering command: /usr/local/bin/helm helm repo add bitnami REDACTED (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)

[akiyashkin-ronasit]

looks good