DirectResponse

DirectResponse is a Gwin custom resource that instructs the load balancer to return a fixed HTTP response directly to the client, without forwarding the request to any backend service.

It is referenced from an HTTPRoute rule via an ExtensionRef filter. This makes it conceptually similar to RequestRedirect — both are terminal route actions that short-circuit normal backend routing.

Typical use cases: returning 404 Not Found for unknown paths, 503 Service Unavailable during maintenance, or any other static response.

• Cheatsheet
• DirectResponseSpec
  • DirectResponseBody

CheatsheetCheatsheet

apiVersion: gwin.yandex.cloud/v1
kind: DirectResponse
metadata:
  name: not-found-response
  namespace: example-ns
spec:
  responseCode: 404          # HTTP status code to return
  responseBody:
    text: "Path not found"   # optional plain-text body

Reference from an HTTPRoute rule via ExtensionRef filter:

apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: example-route
  namespace: example-ns
spec:
  parentRefs:
    - name: example-gateway
  rules:
    - matches:
        - path:
            type: PathPrefix
            value: /unknown
      filters:
        - type: ExtensionRef
          extensionRef:
            group: gwin.yandex.cloud
            kind: DirectResponse
            name: not-found-response  # must be in the same namespace as the HTTPRoute

DirectResponseSpecDirectResponseSpec

DirectResponseSpec defines the HTTP response to be returned to the client.

Appears in: DirectResponse

DirectResponseBodyDirectResponseBody

DirectResponseBody defines the plain-text content of the response body.

Appears in: DirectResponseSpec