Document optional service and port properties for ingress paths

[Copilot]

The ingress-route.yaml template supports optional service and port overrides per path, but these properties were not documented in values.yaml.

Changes

• Added inline comments in values.yaml explaining optional path properties:
  • service: defaults to chart's fullname if omitted
  • port: defaults to service.port if omitted
• Included example configuration demonstrating custom service/port usage

Example

ingress:
  hosts:
    - host: api.example.com
      paths:
        - path: /          # Uses default service and port
        - path: /api
          service: custom-api-service
          port: 8080

This clarifies the template's existing functionality without changing behavior.

---

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

[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)