## Summary Add support for Gateway API filters and timeouts on route resources to enable enhanced customizability for GitLab chart deployments. This includes support for canary deployments and header sanitization, which are common requirements in regulated environments. ## Background The GitLab chart currently supports Gateway API route resources but lacks the ability to configure filters and timeouts. These features are essential for: - **Canary deployments**: Gradually rolling out new versions with traffic splitting - **Header sanitization**: Removing or modifying headers for security and compliance in regulated environments - **Request/response customization**: Applying transformations and policies at the routing layer Related discussion: [#6305](https://gitlab.com/gitlab-org/charts/gitlab/-/work_items/6305) ## Acceptance Criteria - [ ] HTTPRoute resources support filter configuration via Helm values - [ ] HTTPRoute resources support timeout configuration via Helm values - [ ] Documentation is updated with examples for common filter use cases (header sanitization, canary deployments) - [ ] Configuration is available for all HTTPRoute resources (webservice, registry, KAS, minio, pages, openbao) - Status: Currently no route supports filter and only the registry route supports timeouts. - [ ] Filters can be customized per route or globally ## Related Issues - [#6305](https://gitlab.com/gitlab-org/charts/gitlab/-/work_items/6305) - Gateway API | Support existing Gateways