From 6f40c2778c55b52748dd46bb6ed1e2cb5d58a217 Mon Sep 17 00:00:00 2001 From: YASHMAHAKAL Date: Sat, 13 Dec 2025 18:19:55 +0530 Subject: [PATCH 1/6] Add API specification links to user guides Add links to relevant API specification sections in documentation guides to improve navigation between practical examples and detailed API documentation. This addresses issue 4347 by adding links to the following guides: - HTTP feature guides (CORS, timeouts, method matching, etc.) - gRPC and traffic splitting guides - TLS configuration guide - Getting started guide All links follow the established pattern used in existing guides and reference the correct v1 API types. Fixes 4347 Signed-off-by: YASHMAHAKAL --- site-src/guides/getting-started/simple-gateway.md | 8 ++++---- site-src/guides/grpc-routing.md | 2 +- site-src/guides/http-cors.md | 2 +- site-src/guides/http-header-modifier.md | 2 +- site-src/guides/http-method-matching.md | 2 +- site-src/guides/http-query-param-matching.md | 2 +- site-src/guides/http-request-mirroring.md | 4 ++-- site-src/guides/http-timeouts.md | 2 +- site-src/guides/tls.md | 6 +++--- site-src/guides/traffic-splitting.md | 2 +- 10 files changed, 16 insertions(+), 16 deletions(-) diff --git a/site-src/guides/getting-started/simple-gateway.md b/site-src/guides/getting-started/simple-gateway.md index 53445b901e..f3afb0aac4 100644 --- a/site-src/guides/getting-started/simple-gateway.md +++ b/site-src/guides/getting-started/simple-gateway.md @@ -8,8 +8,8 @@ This guide is a great place to start if you are new to Gateway API. It shows the {% include 'standard/simple-gateway/gateway.yaml' %} ``` -The Gateway represents the instantiation of a logical load balancer and the -GatewayClass defines the load balancer template when users create a Gateway. +The [Gateway](../../reference/spec.md#gateway.networking.k8s.io/v1.Gateway) represents the instantiation of a logical load balancer and the +[GatewayClass](../../reference/spec.md#gateway.networking.k8s.io/v1.GatewayClass) defines the load balancer template when users create a Gateway. The example Gateway is templated from a hypothetical `example` GatewayClass, which is meant to be a placeholder and substituted by users. Here is a list of available @@ -21,10 +21,10 @@ The Gateway listens for HTTP traffic on port 80. This particular GatewayClass automatically assigns an IP address which will be shown in the `Gateway.status` after it has been deployed. -Route resources specify the Gateways they want to attach to using `ParentRefs`. As long as +Route resources specify the Gateways they want to attach to using [`ParentRefs`](../../reference/spec.md#gateway.networking.k8s.io/v1.ParentReference). As long as the Gateway allows this attachment (by default Routes from the same namespace are trusted), this will allow the Route to receive traffic from the parent Gateway. -`BackendRefs` define the backends that traffic will be sent to. More complex +[`BackendRefs`](../../reference/spec.md#gateway.networking.k8s.io/v1.HTTPBackendRef) define the backends that traffic will be sent to. More complex bi-directional matching and permissions are possible and explained in other guides. The following HTTPRoute defines how traffic from the Gateway listener is routed diff --git a/site-src/guides/grpc-routing.md b/site-src/guides/grpc-routing.md index ba0fca2b94..9860305fa3 100644 --- a/site-src/guides/grpc-routing.md +++ b/site-src/guides/grpc-routing.md @@ -1,7 +1,7 @@ # gRPC routing The [GRPCRoute resource](../api-types/grpcroute.md) allows you to match on gRPC traffic and -direct it to Kubernetes backends. This guide shows how the GRPCRoute matches +direct it to Kubernetes backends. This guide shows how the [GRPCRoute](../reference/spec.md#gateway.networking.k8s.io/v1.GRPCRoute) matches traffic on host, header, and service, and method fields and forwards it to different Kubernetes Services. diff --git a/site-src/guides/http-cors.md b/site-src/guides/http-cors.md index 3ca7078310..29a7ebc44d 100644 --- a/site-src/guides/http-cors.md +++ b/site-src/guides/http-cors.md @@ -8,7 +8,7 @@ Cross-Origin Resource Sharing (CORS). CORS is a security feature that allows or denies web applications running at one domain to make requests for resources from a different domain. -The `CORS` filter in an `HTTPRouteRule` can be used to specify the CORS policy. +The [`CORS` filter](../reference/spec.md#gateway.networking.k8s.io/v1.HTTPCORSFilter) in an `HTTPRouteRule` can be used to specify the CORS policy. ## Allowing requests from a specific origin diff --git a/site-src/guides/http-header-modifier.md b/site-src/guides/http-header-modifier.md index 170da1832f..0d15db2d78 100644 --- a/site-src/guides/http-header-modifier.md +++ b/site-src/guides/http-header-modifier.md @@ -1,7 +1,7 @@ # HTTP Header Modifiers [HTTPRoute resources](../api-types/httproute.md) can modify the headers of HTTP requests and the HTTP responses from clients. -There are two types of [filters](../api-types/httproute.md#filters-optional) available to meet these requirements: `RequestHeaderModifier` and `ResponseHeaderModifier`. +There are two types of [filters](../api-types/httproute.md#filters-optional) available to meet these requirements: [`RequestHeaderModifier`](../reference/spec.md#gateway.networking.k8s.io/v1.HTTPHeaderFilter) and [`ResponseHeaderModifier`](../reference/spec.md#gateway.networking.k8s.io/v1.HTTPHeaderFilter). This guide shows how to use these features. diff --git a/site-src/guides/http-method-matching.md b/site-src/guides/http-method-matching.md index 17391c7ec4..4aa487d52a 100644 --- a/site-src/guides/http-method-matching.md +++ b/site-src/guides/http-method-matching.md @@ -4,7 +4,7 @@ This feature is part of extended support. For more information on release channels, refer to our [versioning guide](../concepts/versioning.md). The [HTTPRoute resource](../api-types/httproute.md) can be used to match -requests based on the HTTP method. This guide shows how to use this +requests based on the [HTTP method](../reference/spec.md#gateway.networking.k8s.io/v1.HTTPRouteMatch). This guide shows how to use this functionality. ## Matching requests based on the HTTP method diff --git a/site-src/guides/http-query-param-matching.md b/site-src/guides/http-query-param-matching.md index faa3cef6aa..515e671cb5 100644 --- a/site-src/guides/http-query-param-matching.md +++ b/site-src/guides/http-query-param-matching.md @@ -4,7 +4,7 @@ This feature is part of extended support. For more information on release channels, refer to our [versioning guide](../concepts/versioning.md). The [HTTPRoute resource](../api-types/httproute.md) can be used to match -requests based on query parameters. This guide shows how to use this +requests based on [query parameters](../reference/spec.md#gateway.networking.k8s.io/v1.HTTPQueryParamMatch). This guide shows how to use this functionality. ## Matching requests based on a single query parameter diff --git a/site-src/guides/http-request-mirroring.md b/site-src/guides/http-request-mirroring.md index ebc0e1bd21..6e8df6be00 100644 --- a/site-src/guides/http-request-mirroring.md +++ b/site-src/guides/http-request-mirroring.md @@ -3,8 +3,8 @@ ???+ info "Extended Support Feature: HTTPRouteRequestMirror" This feature is part of extended support. For more information on release channels, refer to our [versioning guide](../concepts/versioning.md). -The [HTTPRoute resource](../api-types/httproute.md) can be used to mirror -requests to multiple backends. This is useful for testing new services with +The [HTTPRoute resource](../api-types/httproute.md) can be used to [mirror +requests](../reference/spec.md#gateway.networking.k8s.io/v1.HTTPRequestMirrorFilter) to multiple backends. This is useful for testing new services with production traffic. Mirrored requests will only be sent to one single destination endpoint diff --git a/site-src/guides/http-timeouts.md b/site-src/guides/http-timeouts.md index 973bf66f3b..7368635ec1 100644 --- a/site-src/guides/http-timeouts.md +++ b/site-src/guides/http-timeouts.md @@ -4,7 +4,7 @@ This feature is part of extended support. For more information on release channels, refer to our [versioning guide](../concepts/versioning.md). The [HTTPRoute resource](../api-types/httproute.md) can be used to configure -timeouts for HTTP requests. This is useful for preventing long-running requests +[timeouts](../reference/spec.md#gateway.networking.k8s.io/v1.HTTPRouteTimeouts) for HTTP requests. This is useful for preventing long-running requests from consuming resources and for providing a better user experience. The `timeouts` field in an `HTTPRouteRule` can be used to specify a request diff --git a/site-src/guides/tls.md b/site-src/guides/tls.md index fc43c4835f..7786fd5cc1 100644 --- a/site-src/guides/tls.md +++ b/site-src/guides/tls.md @@ -54,11 +54,11 @@ The use of `Terminate` on `TLSRoute` is available on `Extended` [Support Level]. ## Downstream TLS -Downstream TLS settings are configured using listeners at the Gateway level. +Downstream TLS settings are configured using [listeners](../reference/spec.md#gateway.networking.k8s.io/v1.Listener) at the Gateway level. ### Listeners and TLS -Listeners expose the TLS setting on a per domain or subdomain basis. +Listeners expose the [TLS setting](../reference/spec.md#gateway.networking.k8s.io/v1.GatewayTLSConfig) on a per domain or subdomain basis. TLS settings of a listener are applied to all domains that satisfy the `hostname` criteria. @@ -116,7 +116,7 @@ would be invalid. ## Upstream TLS -Upstream TLS settings are configured using the `BackendTLSPolicy` attached to a +Upstream TLS settings are configured using the [`BackendTLSPolicy`](../reference/spec.md#gateway.networking.k8s.io/v1.BackendTLSPolicy) attached to a `Service` via a target reference. This resource can be used to describe the SNI the Gateway should use to connect to the diff --git a/site-src/guides/traffic-splitting.md b/site-src/guides/traffic-splitting.md index b2f9968268..c47134beeb 100644 --- a/site-src/guides/traffic-splitting.md +++ b/site-src/guides/traffic-splitting.md @@ -1,7 +1,7 @@ # HTTP traffic splitting The [HTTPRoute resource](../api-types/httproute.md) allows you to specify -weights to shift traffic between different backends. This is useful for +[weights](../reference/spec.md#gateway.networking.k8s.io/v1.HTTPBackendRef) to shift traffic between different backends. This is useful for splitting traffic during rollouts, canarying changes, or for emergencies. The HTTPRoute`spec.rules.backendRefs` accepts a list of backends that a route rule will send traffic to. The relative weights of these backends define From efd9d0cfe6783643f839d3e66312765fe8c746fc Mon Sep 17 00:00:00 2001 From: YASHMAHAKAL Date: Tue, 16 Dec 2025 01:59:10 +0530 Subject: [PATCH 2/6] testing-api-redirects Signed-off-by: YASHMAHAKAL --- site-src/guides/http-request-mirroring.md | 2 +- site-src/guides/http-routing.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/site-src/guides/http-request-mirroring.md b/site-src/guides/http-request-mirroring.md index 6e8df6be00..c20ced744d 100644 --- a/site-src/guides/http-request-mirroring.md +++ b/site-src/guides/http-request-mirroring.md @@ -4,7 +4,7 @@ This feature is part of extended support. For more information on release channels, refer to our [versioning guide](../concepts/versioning.md). The [HTTPRoute resource](../api-types/httproute.md) can be used to [mirror -requests](../reference/spec.md#gateway.networking.k8s.io/v1.HTTPRequestMirrorFilter) to multiple backends. This is useful for testing new services with +requests](../reference/spec/#gateway) to multiple backends. This is useful for testing new services with production traffic. Mirrored requests will only be sent to one single destination endpoint diff --git a/site-src/guides/http-routing.md b/site-src/guides/http-routing.md index 72112ec65d..69ac20c68d 100644 --- a/site-src/guides/http-routing.md +++ b/site-src/guides/http-routing.md @@ -57,6 +57,6 @@ missing or not `canary` then it'll be forwarded to `bar-svc`. {% include 'standard/http-routing/bar-httproute.yaml' %} ``` -[gateway]: ../reference/spec.md#gateway.networking.k8s.io/v1.Gateway +[gateway]: ../reference/spec/#gateway [spec]: ../reference/spec.md#gateway.networking.k8s.io/v1.HTTPRouteSpec [svc]:https://kubernetes.io/docs/concepts/services-networking/service/ From 283169c2603721c7add3e6adf1d94bb5839af74b Mon Sep 17 00:00:00 2001 From: YASHMAHAKAL Date: Tue, 16 Dec 2025 10:59:11 +0530 Subject: [PATCH 3/6] Fix broken API specification links by removing .md extension Signed-off-by: YASHMAHAKAL --- site-src/guides/getting-started/simple-gateway.md | 8 ++++---- site-src/guides/grpc-routing.md | 6 +++--- site-src/guides/http-cors.md | 2 +- site-src/guides/http-header-modifier.md | 2 +- site-src/guides/http-method-matching.md | 2 +- site-src/guides/http-query-param-matching.md | 2 +- site-src/guides/http-request-mirroring.md | 2 +- site-src/guides/http-routing.md | 4 ++-- site-src/guides/http-timeouts.md | 2 +- site-src/guides/tls.md | 6 +++--- site-src/guides/traffic-splitting.md | 4 ++-- 11 files changed, 20 insertions(+), 20 deletions(-) diff --git a/site-src/guides/getting-started/simple-gateway.md b/site-src/guides/getting-started/simple-gateway.md index f3afb0aac4..674aa01277 100644 --- a/site-src/guides/getting-started/simple-gateway.md +++ b/site-src/guides/getting-started/simple-gateway.md @@ -8,8 +8,8 @@ This guide is a great place to start if you are new to Gateway API. It shows the {% include 'standard/simple-gateway/gateway.yaml' %} ``` -The [Gateway](../../reference/spec.md#gateway.networking.k8s.io/v1.Gateway) represents the instantiation of a logical load balancer and the -[GatewayClass](../../reference/spec.md#gateway.networking.k8s.io/v1.GatewayClass) defines the load balancer template when users create a Gateway. +The [Gateway](../../reference/spec/#gateway.networking.k8s.io/v1.Gateway) represents the instantiation of a logical load balancer and the +[GatewayClass](../../reference/spec/#gateway.networking.k8s.io/v1.GatewayClass) defines the load balancer template when users create a Gateway. The example Gateway is templated from a hypothetical `example` GatewayClass, which is meant to be a placeholder and substituted by users. Here is a list of available @@ -21,10 +21,10 @@ The Gateway listens for HTTP traffic on port 80. This particular GatewayClass automatically assigns an IP address which will be shown in the `Gateway.status` after it has been deployed. -Route resources specify the Gateways they want to attach to using [`ParentRefs`](../../reference/spec.md#gateway.networking.k8s.io/v1.ParentReference). As long as +Route resources specify the Gateways they want to attach to using [`ParentRefs`](../../reference/spec/#gateway.networking.k8s.io/v1.ParentReference). As long as the Gateway allows this attachment (by default Routes from the same namespace are trusted), this will allow the Route to receive traffic from the parent Gateway. -[`BackendRefs`](../../reference/spec.md#gateway.networking.k8s.io/v1.HTTPBackendRef) define the backends that traffic will be sent to. More complex +[`BackendRefs`](../../reference/spec/#gateway.networking.k8s.io/v1.HTTPBackendRef) define the backends that traffic will be sent to. More complex bi-directional matching and permissions are possible and explained in other guides. The following HTTPRoute defines how traffic from the Gateway listener is routed diff --git a/site-src/guides/grpc-routing.md b/site-src/guides/grpc-routing.md index 9860305fa3..efe987e890 100644 --- a/site-src/guides/grpc-routing.md +++ b/site-src/guides/grpc-routing.md @@ -1,7 +1,7 @@ # gRPC routing The [GRPCRoute resource](../api-types/grpcroute.md) allows you to match on gRPC traffic and -direct it to Kubernetes backends. This guide shows how the [GRPCRoute](../reference/spec.md#gateway.networking.k8s.io/v1.GRPCRoute) matches +direct it to Kubernetes backends. This guide shows how the [GRPCRoute](../reference/spec/#gateway.networking.k8s.io/v1.GRPCRoute) matches traffic on host, header, and service, and method fields and forwards it to different Kubernetes Services. @@ -74,6 +74,6 @@ been considered. {% include 'standard/grpc-routing/reflection-grpcroute.yaml' %} ``` -[gateway]: ../reference/spec.md#gateway.networking.k8s.io/v1.Gateway -[spec]: ../reference/spec.md#gateway.networking.k8s.io%2fv1alpha2.GRPCRouteSpec +[gateway]: ../reference/spec/#gateway.networking.k8s.io/v1.Gateway +[spec]: ../reference/spec/#gateway.networking.k8s.io%2fv1alpha2.GRPCRouteSpec [svc]:https://kubernetes.io/docs/concepts/services-networking/service/ diff --git a/site-src/guides/http-cors.md b/site-src/guides/http-cors.md index 29a7ebc44d..0d12bf4b43 100644 --- a/site-src/guides/http-cors.md +++ b/site-src/guides/http-cors.md @@ -8,7 +8,7 @@ Cross-Origin Resource Sharing (CORS). CORS is a security feature that allows or denies web applications running at one domain to make requests for resources from a different domain. -The [`CORS` filter](../reference/spec.md#gateway.networking.k8s.io/v1.HTTPCORSFilter) in an `HTTPRouteRule` can be used to specify the CORS policy. +The [`CORS` filter](../reference/spec/#gateway.networking.k8s.io/v1.HTTPCORSFilter) in an `HTTPRouteRule` can be used to specify the CORS policy. ## Allowing requests from a specific origin diff --git a/site-src/guides/http-header-modifier.md b/site-src/guides/http-header-modifier.md index 0d15db2d78..b5e50a4e90 100644 --- a/site-src/guides/http-header-modifier.md +++ b/site-src/guides/http-header-modifier.md @@ -1,7 +1,7 @@ # HTTP Header Modifiers [HTTPRoute resources](../api-types/httproute.md) can modify the headers of HTTP requests and the HTTP responses from clients. -There are two types of [filters](../api-types/httproute.md#filters-optional) available to meet these requirements: [`RequestHeaderModifier`](../reference/spec.md#gateway.networking.k8s.io/v1.HTTPHeaderFilter) and [`ResponseHeaderModifier`](../reference/spec.md#gateway.networking.k8s.io/v1.HTTPHeaderFilter). +There are two types of [filters](../api-types/httproute.md#filters-optional) available to meet these requirements: [`RequestHeaderModifier`](../reference/spec/#gateway.networking.k8s.io/v1.HTTPHeaderFilter) and [`ResponseHeaderModifier`](../reference/spec/#gateway.networking.k8s.io/v1.HTTPHeaderFilter). This guide shows how to use these features. diff --git a/site-src/guides/http-method-matching.md b/site-src/guides/http-method-matching.md index 4aa487d52a..0cbd2bf4b6 100644 --- a/site-src/guides/http-method-matching.md +++ b/site-src/guides/http-method-matching.md @@ -4,7 +4,7 @@ This feature is part of extended support. For more information on release channels, refer to our [versioning guide](../concepts/versioning.md). The [HTTPRoute resource](../api-types/httproute.md) can be used to match -requests based on the [HTTP method](../reference/spec.md#gateway.networking.k8s.io/v1.HTTPRouteMatch). This guide shows how to use this +requests based on the [HTTP method](../reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteMatch). This guide shows how to use this functionality. ## Matching requests based on the HTTP method diff --git a/site-src/guides/http-query-param-matching.md b/site-src/guides/http-query-param-matching.md index 515e671cb5..a023a3e7b4 100644 --- a/site-src/guides/http-query-param-matching.md +++ b/site-src/guides/http-query-param-matching.md @@ -4,7 +4,7 @@ This feature is part of extended support. For more information on release channels, refer to our [versioning guide](../concepts/versioning.md). The [HTTPRoute resource](../api-types/httproute.md) can be used to match -requests based on [query parameters](../reference/spec.md#gateway.networking.k8s.io/v1.HTTPQueryParamMatch). This guide shows how to use this +requests based on [query parameters](../reference/spec/#gateway.networking.k8s.io/v1.HTTPQueryParamMatch). This guide shows how to use this functionality. ## Matching requests based on a single query parameter diff --git a/site-src/guides/http-request-mirroring.md b/site-src/guides/http-request-mirroring.md index c20ced744d..5616d38fb9 100644 --- a/site-src/guides/http-request-mirroring.md +++ b/site-src/guides/http-request-mirroring.md @@ -4,7 +4,7 @@ This feature is part of extended support. For more information on release channels, refer to our [versioning guide](../concepts/versioning.md). The [HTTPRoute resource](../api-types/httproute.md) can be used to [mirror -requests](../reference/spec/#gateway) to multiple backends. This is useful for testing new services with +requests](../reference/spec/#gateway.networking.k8s.io/v1.HTTPRequestMirrorFilter) to multiple backends. This is useful for testing new services with production traffic. Mirrored requests will only be sent to one single destination endpoint diff --git a/site-src/guides/http-routing.md b/site-src/guides/http-routing.md index 69ac20c68d..b7ef8d06ec 100644 --- a/site-src/guides/http-routing.md +++ b/site-src/guides/http-routing.md @@ -57,6 +57,6 @@ missing or not `canary` then it'll be forwarded to `bar-svc`. {% include 'standard/http-routing/bar-httproute.yaml' %} ``` -[gateway]: ../reference/spec/#gateway -[spec]: ../reference/spec.md#gateway.networking.k8s.io/v1.HTTPRouteSpec +[gateway]: ../reference/spec/#gateway.networking.k8s.io/v1.Gateway +[spec]: ../reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteSpec [svc]:https://kubernetes.io/docs/concepts/services-networking/service/ diff --git a/site-src/guides/http-timeouts.md b/site-src/guides/http-timeouts.md index 7368635ec1..44901096a4 100644 --- a/site-src/guides/http-timeouts.md +++ b/site-src/guides/http-timeouts.md @@ -4,7 +4,7 @@ This feature is part of extended support. For more information on release channels, refer to our [versioning guide](../concepts/versioning.md). The [HTTPRoute resource](../api-types/httproute.md) can be used to configure -[timeouts](../reference/spec.md#gateway.networking.k8s.io/v1.HTTPRouteTimeouts) for HTTP requests. This is useful for preventing long-running requests +[timeouts](../reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteTimeouts) for HTTP requests. This is useful for preventing long-running requests from consuming resources and for providing a better user experience. The `timeouts` field in an `HTTPRouteRule` can be used to specify a request diff --git a/site-src/guides/tls.md b/site-src/guides/tls.md index 7786fd5cc1..99e14eb1bf 100644 --- a/site-src/guides/tls.md +++ b/site-src/guides/tls.md @@ -54,11 +54,11 @@ The use of `Terminate` on `TLSRoute` is available on `Extended` [Support Level]. ## Downstream TLS -Downstream TLS settings are configured using [listeners](../reference/spec.md#gateway.networking.k8s.io/v1.Listener) at the Gateway level. +Downstream TLS settings are configured using [listeners](../reference/spec/#gateway.networking.k8s.io/v1.Listener) at the Gateway level. ### Listeners and TLS -Listeners expose the [TLS setting](../reference/spec.md#gateway.networking.k8s.io/v1.GatewayTLSConfig) on a per domain or subdomain basis. +Listeners expose the [TLS setting](../reference/spec/#gateway.networking.k8s.io/v1.GatewayTLSConfig) on a per domain or subdomain basis. TLS settings of a listener are applied to all domains that satisfy the `hostname` criteria. @@ -116,7 +116,7 @@ would be invalid. ## Upstream TLS -Upstream TLS settings are configured using the [`BackendTLSPolicy`](../reference/spec.md#gateway.networking.k8s.io/v1.BackendTLSPolicy) attached to a +Upstream TLS settings are configured using the [`BackendTLSPolicy`](../reference/spec/#gateway.networking.k8s.io/v1.BackendTLSPolicy) attached to a `Service` via a target reference. This resource can be used to describe the SNI the Gateway should use to connect to the diff --git a/site-src/guides/traffic-splitting.md b/site-src/guides/traffic-splitting.md index c47134beeb..33b6ea622d 100644 --- a/site-src/guides/traffic-splitting.md +++ b/site-src/guides/traffic-splitting.md @@ -1,7 +1,7 @@ # HTTP traffic splitting The [HTTPRoute resource](../api-types/httproute.md) allows you to specify -[weights](../reference/spec.md#gateway.networking.k8s.io/v1.HTTPBackendRef) to shift traffic between different backends. This is useful for +[weights](../reference/spec/#gateway.networking.k8s.io/v1.HTTPBackendRef) to shift traffic between different backends. This is useful for splitting traffic during rollouts, canarying changes, or for emergencies. The HTTPRoute`spec.rules.backendRefs` accepts a list of backends that a route rule will send traffic to. The relative weights of these backends define @@ -41,7 +41,7 @@ production user traffic for `foo.example.com`. The following HTTPRoute has no receive 100% of the traffic matched by each of their route rules. A canary route rule is used (matching the header `traffic=test`) to send synthetic test traffic before splitting any production user traffic to `foo-v2`. -[Routing precedence](../reference/spec.md#gateway.networking.k8s.io/v1.HTTPRouteRule) +[Routing precedence](../reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteRule) ensures that all traffic with the matching host and header (the most specific match) will be sent to `foo-v2`. From 5e504a1b042711df2817546b69b6de051aee4064 Mon Sep 17 00:00:00 2001 From: YASHMAHAKAL Date: Tue, 16 Dec 2025 11:31:13 +0530 Subject: [PATCH 4/6] Use lowercase anchor IDs for API spec links Signed-off-by: YASHMAHAKAL --- site-src/guides/getting-started/simple-gateway.md | 8 ++++---- site-src/guides/grpc-routing.md | 6 +++--- site-src/guides/http-cors.md | 2 +- site-src/guides/http-header-modifier.md | 2 +- site-src/guides/http-method-matching.md | 2 +- site-src/guides/http-query-param-matching.md | 2 +- site-src/guides/http-request-mirroring.md | 2 +- site-src/guides/http-routing.md | 4 ++-- site-src/guides/http-timeouts.md | 2 +- site-src/guides/tls.md | 6 +++--- site-src/guides/traffic-splitting.md | 4 ++-- 11 files changed, 20 insertions(+), 20 deletions(-) diff --git a/site-src/guides/getting-started/simple-gateway.md b/site-src/guides/getting-started/simple-gateway.md index 674aa01277..d18a83a6cc 100644 --- a/site-src/guides/getting-started/simple-gateway.md +++ b/site-src/guides/getting-started/simple-gateway.md @@ -8,8 +8,8 @@ This guide is a great place to start if you are new to Gateway API. It shows the {% include 'standard/simple-gateway/gateway.yaml' %} ``` -The [Gateway](../../reference/spec/#gateway.networking.k8s.io/v1.Gateway) represents the instantiation of a logical load balancer and the -[GatewayClass](../../reference/spec/#gateway.networking.k8s.io/v1.GatewayClass) defines the load balancer template when users create a Gateway. +The [Gateway](../../reference/spec/#gateway) represents the instantiation of a logical load balancer and the +[GatewayClass](../../reference/spec/#gatewayclass) defines the load balancer template when users create a Gateway. The example Gateway is templated from a hypothetical `example` GatewayClass, which is meant to be a placeholder and substituted by users. Here is a list of available @@ -21,10 +21,10 @@ The Gateway listens for HTTP traffic on port 80. This particular GatewayClass automatically assigns an IP address which will be shown in the `Gateway.status` after it has been deployed. -Route resources specify the Gateways they want to attach to using [`ParentRefs`](../../reference/spec/#gateway.networking.k8s.io/v1.ParentReference). As long as +Route resources specify the Gateways they want to attach to using [`ParentRefs`](../../reference/spec/#parentreference). As long as the Gateway allows this attachment (by default Routes from the same namespace are trusted), this will allow the Route to receive traffic from the parent Gateway. -[`BackendRefs`](../../reference/spec/#gateway.networking.k8s.io/v1.HTTPBackendRef) define the backends that traffic will be sent to. More complex +[`BackendRefs`](../../reference/spec/#httpbackendref) define the backends that traffic will be sent to. More complex bi-directional matching and permissions are possible and explained in other guides. The following HTTPRoute defines how traffic from the Gateway listener is routed diff --git a/site-src/guides/grpc-routing.md b/site-src/guides/grpc-routing.md index efe987e890..0a83d19864 100644 --- a/site-src/guides/grpc-routing.md +++ b/site-src/guides/grpc-routing.md @@ -1,7 +1,7 @@ # gRPC routing The [GRPCRoute resource](../api-types/grpcroute.md) allows you to match on gRPC traffic and -direct it to Kubernetes backends. This guide shows how the [GRPCRoute](../reference/spec/#gateway.networking.k8s.io/v1.GRPCRoute) matches +direct it to Kubernetes backends. This guide shows how the [GRPCRoute](../reference/spec/#grpcroute) matches traffic on host, header, and service, and method fields and forwards it to different Kubernetes Services. @@ -74,6 +74,6 @@ been considered. {% include 'standard/grpc-routing/reflection-grpcroute.yaml' %} ``` -[gateway]: ../reference/spec/#gateway.networking.k8s.io/v1.Gateway -[spec]: ../reference/spec/#gateway.networking.k8s.io%2fv1alpha2.GRPCRouteSpec +[gateway]: ../reference/spec/#gateway +[spec]: ../reference/spec/#grpcroutespec [svc]:https://kubernetes.io/docs/concepts/services-networking/service/ diff --git a/site-src/guides/http-cors.md b/site-src/guides/http-cors.md index 0d12bf4b43..e0e2ba4553 100644 --- a/site-src/guides/http-cors.md +++ b/site-src/guides/http-cors.md @@ -8,7 +8,7 @@ Cross-Origin Resource Sharing (CORS). CORS is a security feature that allows or denies web applications running at one domain to make requests for resources from a different domain. -The [`CORS` filter](../reference/spec/#gateway.networking.k8s.io/v1.HTTPCORSFilter) in an `HTTPRouteRule` can be used to specify the CORS policy. +The [`CORS` filter](../reference/spec/#httpcorsfilter) in an `HTTPRouteRule` can be used to specify the CORS policy. ## Allowing requests from a specific origin diff --git a/site-src/guides/http-header-modifier.md b/site-src/guides/http-header-modifier.md index b5e50a4e90..a686de2ce9 100644 --- a/site-src/guides/http-header-modifier.md +++ b/site-src/guides/http-header-modifier.md @@ -1,7 +1,7 @@ # HTTP Header Modifiers [HTTPRoute resources](../api-types/httproute.md) can modify the headers of HTTP requests and the HTTP responses from clients. -There are two types of [filters](../api-types/httproute.md#filters-optional) available to meet these requirements: [`RequestHeaderModifier`](../reference/spec/#gateway.networking.k8s.io/v1.HTTPHeaderFilter) and [`ResponseHeaderModifier`](../reference/spec/#gateway.networking.k8s.io/v1.HTTPHeaderFilter). +There are two types of [filters](../api-types/httproute.md#filters-optional) available to meet these requirements: [`RequestHeaderModifier`](../reference/spec/#httpheaderfilter) and [`ResponseHeaderModifier`](../reference/spec/#httpheaderfilter). This guide shows how to use these features. diff --git a/site-src/guides/http-method-matching.md b/site-src/guides/http-method-matching.md index 0cbd2bf4b6..dc083437a3 100644 --- a/site-src/guides/http-method-matching.md +++ b/site-src/guides/http-method-matching.md @@ -4,7 +4,7 @@ This feature is part of extended support. For more information on release channels, refer to our [versioning guide](../concepts/versioning.md). The [HTTPRoute resource](../api-types/httproute.md) can be used to match -requests based on the [HTTP method](../reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteMatch). This guide shows how to use this +requests based on the [HTTP method](../reference/spec/#httproutematch). This guide shows how to use this functionality. ## Matching requests based on the HTTP method diff --git a/site-src/guides/http-query-param-matching.md b/site-src/guides/http-query-param-matching.md index a023a3e7b4..4dff6a7be8 100644 --- a/site-src/guides/http-query-param-matching.md +++ b/site-src/guides/http-query-param-matching.md @@ -4,7 +4,7 @@ This feature is part of extended support. For more information on release channels, refer to our [versioning guide](../concepts/versioning.md). The [HTTPRoute resource](../api-types/httproute.md) can be used to match -requests based on [query parameters](../reference/spec/#gateway.networking.k8s.io/v1.HTTPQueryParamMatch). This guide shows how to use this +requests based on [query parameters](../reference/spec/#httpqueryparammatch). This guide shows how to use this functionality. ## Matching requests based on a single query parameter diff --git a/site-src/guides/http-request-mirroring.md b/site-src/guides/http-request-mirroring.md index 5616d38fb9..a431bb2b84 100644 --- a/site-src/guides/http-request-mirroring.md +++ b/site-src/guides/http-request-mirroring.md @@ -4,7 +4,7 @@ This feature is part of extended support. For more information on release channels, refer to our [versioning guide](../concepts/versioning.md). The [HTTPRoute resource](../api-types/httproute.md) can be used to [mirror -requests](../reference/spec/#gateway.networking.k8s.io/v1.HTTPRequestMirrorFilter) to multiple backends. This is useful for testing new services with +requests](../reference/spec/#httprequestmirrorfilter) to multiple backends. This is useful for testing new services with production traffic. Mirrored requests will only be sent to one single destination endpoint diff --git a/site-src/guides/http-routing.md b/site-src/guides/http-routing.md index b7ef8d06ec..293e944027 100644 --- a/site-src/guides/http-routing.md +++ b/site-src/guides/http-routing.md @@ -57,6 +57,6 @@ missing or not `canary` then it'll be forwarded to `bar-svc`. {% include 'standard/http-routing/bar-httproute.yaml' %} ``` -[gateway]: ../reference/spec/#gateway.networking.k8s.io/v1.Gateway -[spec]: ../reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteSpec +[gateway]: ../reference/spec/#gateway +[spec]: ../reference/spec/#httproutespec [svc]:https://kubernetes.io/docs/concepts/services-networking/service/ diff --git a/site-src/guides/http-timeouts.md b/site-src/guides/http-timeouts.md index 44901096a4..aeade269a1 100644 --- a/site-src/guides/http-timeouts.md +++ b/site-src/guides/http-timeouts.md @@ -4,7 +4,7 @@ This feature is part of extended support. For more information on release channels, refer to our [versioning guide](../concepts/versioning.md). The [HTTPRoute resource](../api-types/httproute.md) can be used to configure -[timeouts](../reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteTimeouts) for HTTP requests. This is useful for preventing long-running requests +[timeouts](../reference/spec/#httproutetimeouts) for HTTP requests. This is useful for preventing long-running requests from consuming resources and for providing a better user experience. The `timeouts` field in an `HTTPRouteRule` can be used to specify a request diff --git a/site-src/guides/tls.md b/site-src/guides/tls.md index 99e14eb1bf..8307f9c59e 100644 --- a/site-src/guides/tls.md +++ b/site-src/guides/tls.md @@ -54,11 +54,11 @@ The use of `Terminate` on `TLSRoute` is available on `Extended` [Support Level]. ## Downstream TLS -Downstream TLS settings are configured using [listeners](../reference/spec/#gateway.networking.k8s.io/v1.Listener) at the Gateway level. +Downstream TLS settings are configured using [listeners](../reference/spec/#listener) at the Gateway level. ### Listeners and TLS -Listeners expose the [TLS setting](../reference/spec/#gateway.networking.k8s.io/v1.GatewayTLSConfig) on a per domain or subdomain basis. +Listeners expose the [TLS setting](../reference/spec/#gatewaytlsconfig) on a per domain or subdomain basis. TLS settings of a listener are applied to all domains that satisfy the `hostname` criteria. @@ -116,7 +116,7 @@ would be invalid. ## Upstream TLS -Upstream TLS settings are configured using the [`BackendTLSPolicy`](../reference/spec/#gateway.networking.k8s.io/v1.BackendTLSPolicy) attached to a +Upstream TLS settings are configured using the [`BackendTLSPolicy`](../reference/spec/#backendtlspolicy) attached to a `Service` via a target reference. This resource can be used to describe the SNI the Gateway should use to connect to the diff --git a/site-src/guides/traffic-splitting.md b/site-src/guides/traffic-splitting.md index 33b6ea622d..0b4a962431 100644 --- a/site-src/guides/traffic-splitting.md +++ b/site-src/guides/traffic-splitting.md @@ -1,7 +1,7 @@ # HTTP traffic splitting The [HTTPRoute resource](../api-types/httproute.md) allows you to specify -[weights](../reference/spec/#gateway.networking.k8s.io/v1.HTTPBackendRef) to shift traffic between different backends. This is useful for +[weights](../reference/spec/#httpbackendref) to shift traffic between different backends. This is useful for splitting traffic during rollouts, canarying changes, or for emergencies. The HTTPRoute`spec.rules.backendRefs` accepts a list of backends that a route rule will send traffic to. The relative weights of these backends define @@ -41,7 +41,7 @@ production user traffic for `foo.example.com`. The following HTTPRoute has no receive 100% of the traffic matched by each of their route rules. A canary route rule is used (matching the header `traffic=test`) to send synthetic test traffic before splitting any production user traffic to `foo-v2`. -[Routing precedence](../reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteRule) +[Routing precedence](../reference/spec/#httprouterule) ensures that all traffic with the matching host and header (the most specific match) will be sent to `foo-v2`. From 02674ae5fe86e3cc3b674af9dba8a410569b742b Mon Sep 17 00:00:00 2001 From: YASHMAHAKAL Date: Tue, 16 Dec 2025 19:35:42 +0530 Subject: [PATCH 5/6] fixed broken links & 404 error Signed-off-by: YASHMAHAKAL --- site-src/guides/grpc-routing.md | 6 +++--- site-src/guides/http-cors.md | 2 +- site-src/guides/http-header-modifier.md | 2 +- site-src/guides/http-method-matching.md | 2 +- site-src/guides/http-query-param-matching.md | 2 +- site-src/guides/http-request-mirroring.md | 3 +-- site-src/guides/http-routing.md | 4 ++-- site-src/guides/http-timeouts.md | 2 +- site-src/guides/tls.md | 6 +++--- site-src/guides/traffic-splitting.md | 4 ++-- 10 files changed, 16 insertions(+), 17 deletions(-) diff --git a/site-src/guides/grpc-routing.md b/site-src/guides/grpc-routing.md index 0a83d19864..bf5874f469 100644 --- a/site-src/guides/grpc-routing.md +++ b/site-src/guides/grpc-routing.md @@ -1,7 +1,7 @@ # gRPC routing The [GRPCRoute resource](../api-types/grpcroute.md) allows you to match on gRPC traffic and -direct it to Kubernetes backends. This guide shows how the [GRPCRoute](../reference/spec/#grpcroute) matches +direct it to Kubernetes backends. This guide shows how the [GRPCRoute](../../reference/spec/#grpcroute) matches traffic on host, header, and service, and method fields and forwards it to different Kubernetes Services. @@ -74,6 +74,6 @@ been considered. {% include 'standard/grpc-routing/reflection-grpcroute.yaml' %} ``` -[gateway]: ../reference/spec/#gateway -[spec]: ../reference/spec/#grpcroutespec +[gateway]: ../../reference/spec/#gateway +[spec]: ../../reference/spec/#grpcroutespec [svc]:https://kubernetes.io/docs/concepts/services-networking/service/ diff --git a/site-src/guides/http-cors.md b/site-src/guides/http-cors.md index e0e2ba4553..c5da1ab264 100644 --- a/site-src/guides/http-cors.md +++ b/site-src/guides/http-cors.md @@ -8,7 +8,7 @@ Cross-Origin Resource Sharing (CORS). CORS is a security feature that allows or denies web applications running at one domain to make requests for resources from a different domain. -The [`CORS` filter](../reference/spec/#httpcorsfilter) in an `HTTPRouteRule` can be used to specify the CORS policy. +The [`CORS` filter](../../reference/spec/#httpcorsfilter) in an `HTTPRouteRule` can be used to specify the CORS policy. ## Allowing requests from a specific origin diff --git a/site-src/guides/http-header-modifier.md b/site-src/guides/http-header-modifier.md index a686de2ce9..7b66561a9e 100644 --- a/site-src/guides/http-header-modifier.md +++ b/site-src/guides/http-header-modifier.md @@ -1,7 +1,7 @@ # HTTP Header Modifiers [HTTPRoute resources](../api-types/httproute.md) can modify the headers of HTTP requests and the HTTP responses from clients. -There are two types of [filters](../api-types/httproute.md#filters-optional) available to meet these requirements: [`RequestHeaderModifier`](../reference/spec/#httpheaderfilter) and [`ResponseHeaderModifier`](../reference/spec/#httpheaderfilter). +There are two types of [filters](../api-types/httproute.md#filters-optional) available to meet these requirements: [`RequestHeaderModifier`](../../reference/spec/#httpheaderfilter) and [`ResponseHeaderModifier`](../../reference/spec/#httpheaderfilter). This guide shows how to use these features. diff --git a/site-src/guides/http-method-matching.md b/site-src/guides/http-method-matching.md index dc083437a3..6dd17b879e 100644 --- a/site-src/guides/http-method-matching.md +++ b/site-src/guides/http-method-matching.md @@ -4,7 +4,7 @@ This feature is part of extended support. For more information on release channels, refer to our [versioning guide](../concepts/versioning.md). The [HTTPRoute resource](../api-types/httproute.md) can be used to match -requests based on the [HTTP method](../reference/spec/#httproutematch). This guide shows how to use this +requests based on the [HTTP method](../../reference/spec/#httproutematch). This guide shows how to use this functionality. ## Matching requests based on the HTTP method diff --git a/site-src/guides/http-query-param-matching.md b/site-src/guides/http-query-param-matching.md index 4dff6a7be8..9d6c718e1d 100644 --- a/site-src/guides/http-query-param-matching.md +++ b/site-src/guides/http-query-param-matching.md @@ -4,7 +4,7 @@ This feature is part of extended support. For more information on release channels, refer to our [versioning guide](../concepts/versioning.md). The [HTTPRoute resource](../api-types/httproute.md) can be used to match -requests based on [query parameters](../reference/spec/#httpqueryparammatch). This guide shows how to use this +requests based on [query parameters](../../reference/spec/#httpqueryparammatch). This guide shows how to use this functionality. ## Matching requests based on a single query parameter diff --git a/site-src/guides/http-request-mirroring.md b/site-src/guides/http-request-mirroring.md index a431bb2b84..0779f1b8f4 100644 --- a/site-src/guides/http-request-mirroring.md +++ b/site-src/guides/http-request-mirroring.md @@ -3,8 +3,7 @@ ???+ info "Extended Support Feature: HTTPRouteRequestMirror" This feature is part of extended support. For more information on release channels, refer to our [versioning guide](../concepts/versioning.md). -The [HTTPRoute resource](../api-types/httproute.md) can be used to [mirror -requests](../reference/spec/#httprequestmirrorfilter) to multiple backends. This is useful for testing new services with +The [HTTPRoute resource](../api-types/httproute.md) can be used to [mirror requests](../../reference/spec/#httprequestmirrorfilter) to multiple backends. This is useful for testing new services with production traffic. Mirrored requests will only be sent to one single destination endpoint diff --git a/site-src/guides/http-routing.md b/site-src/guides/http-routing.md index 293e944027..0230800beb 100644 --- a/site-src/guides/http-routing.md +++ b/site-src/guides/http-routing.md @@ -57,6 +57,6 @@ missing or not `canary` then it'll be forwarded to `bar-svc`. {% include 'standard/http-routing/bar-httproute.yaml' %} ``` -[gateway]: ../reference/spec/#gateway -[spec]: ../reference/spec/#httproutespec +[gateway]: ../../reference/spec/#gateway +[spec]: ../../reference/spec/#httproutespec [svc]:https://kubernetes.io/docs/concepts/services-networking/service/ diff --git a/site-src/guides/http-timeouts.md b/site-src/guides/http-timeouts.md index aeade269a1..93bb96daf3 100644 --- a/site-src/guides/http-timeouts.md +++ b/site-src/guides/http-timeouts.md @@ -4,7 +4,7 @@ This feature is part of extended support. For more information on release channels, refer to our [versioning guide](../concepts/versioning.md). The [HTTPRoute resource](../api-types/httproute.md) can be used to configure -[timeouts](../reference/spec/#httproutetimeouts) for HTTP requests. This is useful for preventing long-running requests +[timeouts](../../reference/spec/#httproutetimeouts) for HTTP requests. This is useful for preventing long-running requests from consuming resources and for providing a better user experience. The `timeouts` field in an `HTTPRouteRule` can be used to specify a request diff --git a/site-src/guides/tls.md b/site-src/guides/tls.md index 8307f9c59e..8ab02a56f1 100644 --- a/site-src/guides/tls.md +++ b/site-src/guides/tls.md @@ -54,11 +54,11 @@ The use of `Terminate` on `TLSRoute` is available on `Extended` [Support Level]. ## Downstream TLS -Downstream TLS settings are configured using [listeners](../reference/spec/#listener) at the Gateway level. +Downstream TLS settings are configured using [listeners](../../reference/spec/#listener) at the Gateway level. ### Listeners and TLS -Listeners expose the [TLS setting](../reference/spec/#gatewaytlsconfig) on a per domain or subdomain basis. +Listeners expose the [TLS setting](../../reference/spec/#gatewaytlsconfig) on a per domain or subdomain basis. TLS settings of a listener are applied to all domains that satisfy the `hostname` criteria. @@ -116,7 +116,7 @@ would be invalid. ## Upstream TLS -Upstream TLS settings are configured using the [`BackendTLSPolicy`](../reference/spec/#backendtlspolicy) attached to a +Upstream TLS settings are configured using the [`BackendTLSPolicy`](../../reference/spec/#backendtlspolicy) attached to a `Service` via a target reference. This resource can be used to describe the SNI the Gateway should use to connect to the diff --git a/site-src/guides/traffic-splitting.md b/site-src/guides/traffic-splitting.md index 0b4a962431..9d4d1f6a1f 100644 --- a/site-src/guides/traffic-splitting.md +++ b/site-src/guides/traffic-splitting.md @@ -1,7 +1,7 @@ # HTTP traffic splitting The [HTTPRoute resource](../api-types/httproute.md) allows you to specify -[weights](../reference/spec/#httpbackendref) to shift traffic between different backends. This is useful for +[weights](../../reference/spec/#httpbackendref) to shift traffic between different backends. This is useful for splitting traffic during rollouts, canarying changes, or for emergencies. The HTTPRoute`spec.rules.backendRefs` accepts a list of backends that a route rule will send traffic to. The relative weights of these backends define @@ -41,7 +41,7 @@ production user traffic for `foo.example.com`. The following HTTPRoute has no receive 100% of the traffic matched by each of their route rules. A canary route rule is used (matching the header `traffic=test`) to send synthetic test traffic before splitting any production user traffic to `foo-v2`. -[Routing precedence](../reference/spec/#httprouterule) +[Routing precedence](../../reference/spec/#httprouterule) ensures that all traffic with the matching host and header (the most specific match) will be sent to `foo-v2`. From 2e54f40121d374c4d0d7c2f3447d6bd1609a5ded Mon Sep 17 00:00:00 2001 From: YASHMAHAKAL Date: Tue, 16 Dec 2025 19:57:04 +0530 Subject: [PATCH 6/6] fixed simple-gateway.md broken links Signed-off-by: YASHMAHAKAL --- site-src/guides/getting-started/simple-gateway.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/site-src/guides/getting-started/simple-gateway.md b/site-src/guides/getting-started/simple-gateway.md index d18a83a6cc..dcc46562b1 100644 --- a/site-src/guides/getting-started/simple-gateway.md +++ b/site-src/guides/getting-started/simple-gateway.md @@ -8,8 +8,8 @@ This guide is a great place to start if you are new to Gateway API. It shows the {% include 'standard/simple-gateway/gateway.yaml' %} ``` -The [Gateway](../../reference/spec/#gateway) represents the instantiation of a logical load balancer and the -[GatewayClass](../../reference/spec/#gatewayclass) defines the load balancer template when users create a Gateway. +The [Gateway](../../../reference/spec/#gateway) represents the instantiation of a logical load balancer and the +[GatewayClass](../../../reference/spec/#gatewayclass) defines the load balancer template when users create a Gateway. The example Gateway is templated from a hypothetical `example` GatewayClass, which is meant to be a placeholder and substituted by users. Here is a list of available @@ -21,10 +21,10 @@ The Gateway listens for HTTP traffic on port 80. This particular GatewayClass automatically assigns an IP address which will be shown in the `Gateway.status` after it has been deployed. -Route resources specify the Gateways they want to attach to using [`ParentRefs`](../../reference/spec/#parentreference). As long as +Route resources specify the Gateways they want to attach to using [`ParentRefs`](../../../reference/spec/#parentreference). As long as the Gateway allows this attachment (by default Routes from the same namespace are trusted), this will allow the Route to receive traffic from the parent Gateway. -[`BackendRefs`](../../reference/spec/#httpbackendref) define the backends that traffic will be sent to. More complex +[`BackendRefs`](../../../reference/spec/#httpbackendref) define the backends that traffic will be sent to. More complex bi-directional matching and permissions are possible and explained in other guides. The following HTTPRoute defines how traffic from the Gateway listener is routed