DirectResponse contains configuration for defining direct response routes.
Last changed in Kgateway v2.2.0
APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
DirectResponseSpec describes the desired state of a DirectResponse.
Body defines the content to be returned in the HTTP response body. The maximum length of the body is restricted to prevent excessively large responses. If this field is omitted, no body is included in the response.
StatusCode defines the HTTP status code to return for this route.
DirectResponseStatus defines the observed state of a DirectResponse.
Source: gateway.kgateway.dev_directresponses.yaml
Changes to DirectResponse (gateway.kgateway.dev/v1alpha1) in each Kgateway version, compared to the version before it.
1 property is now required
The description of DirectResponse has changed
6 properties have changed the description
Released · View DirectResponse in v2.2.0
DirectResponse was already present in this version of Kgateway, the oldest one on kubespec.dev
Released · View DirectResponse in v2.0.0
No examples of DirectResponse yet. Contribute one on GitHub.