Add Gateway API HTTPRoute support for proxy, ui, and bff services

[Copilot]

📄 What has changed

Adds opt-in Gateway API HTTPRoute support to proxy, ui, and bff services while maintaining backward compatibility with existing Ingress resources.

Implementation

• HTTPRoute templates added to boundaries/{proxy,ui,bff}/ops/*/templates/http-route.yaml

  • Proxy: /s path prefix → shortlink-link-proxy:3020
  • UI: /next path prefix → shortlink-link-ui:8080
  • BFF: /api path prefix → shortlink-link-bff:7070

• values.yaml configuration for each service:

  httpRoute:
    enabled: false  # Opt-in, disabled by default
    parentRefs:
      - name: external-gateway
        namespace: shortlink-common
    hostnames:
      - shortlink.best
    rules: [...]
  
  ingress:
    enabled: true  # Default remains unchanged
  

• Migration guide at boundaries/GATEWAY_API_MIGRATION.md covering:

  • Gateway prerequisites and setup
  • Service-specific examples
  • Advanced features (header/query routing, traffic splitting, filters)
  • Phased migration strategy
  • Troubleshooting

Usage

# Enable HTTPRoute for a service
helm upgrade proxy boundaries/proxy/ops/proxy \
  --set httpRoute.enabled=true \
  --set ingress.enabled=false

Both routing methods can coexist during migration. Services using Istio for gRPC (link, metadata) are excluded as they already use GRPCRoute.

### Before submitting, please be sure to check this list
- [x] your branch will not cause merge conflict with the main branch
- [x] unit tests are included
- [x] you are not committing extraneous files or sensitive data

Original prompt

Update ingress to http route where we can

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.