Add Kubernetes Gateway API integration for NGWAF

[Copilot]

Implements Kubernetes Gateway API support for Fastly NGWAF following the existing k8s-rev-proxy pattern. Gateway API provides more expressive routing capabilities and better separation of concerns compared to traditional Ingress resources.

Changes

New directory: on-prem-ngwaf-integrations/k8s-gateway-api/

• deployment.yaml - Kubernetes manifests with Gateway API resources:

  • Gateway resource listening on port 8000 (envoy-gateway class)
  • HTTPRoute resource routing all traffic through sigsci-agent
  • Same NGINX backend and sigsci-agent reverse proxy setup as k8s-rev-proxy
  • Uses ClusterIP services with Gateway handling ingress

• Makefile - Build automation matching k8s-rev-proxy pattern:

  • make build - Deploy with NGWAF credentials
  • make demo - Port-forward Gateway for local testing
  • make get - View pods, services, gateways, httproutes

• README.md - Setup instructions including:

  • Gateway API CRDs installation (v1.0.0)
  • Envoy Gateway controller setup
  • Configuration options for different Gateway controllers

GitHub Actions workflow: .github/workflows/ngwaf-k8s-gateway-api.yaml

• Automated testing with kind cluster
• Installs Gateway API CRDs and Envoy Gateway
• Validates deployment and routing with curl
• Includes proper contents: read permissions

Traffic flow:

Client → Gateway:8000 → HTTPRoute → sigsci-revproxy-service:80 → sigsci-agent:8080 → nginx-backend-service:80

Main README updated with workflow badge.

Original prompt

On on-prem-ngwaf-integrations, Review the k8s-rev-proxy implementation.

You need to implement the k8s Gateway API https://gateway-api.sigs.k8s.io/guides/ using a similar workflow as what exists in k8s-rev-proxy. You also need to build a GitHub action that may test this integration.

---

💡 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.