Filter custom resource works in conjunction with the FilterPolicy custom resource to define how and when Ambassador Edge Stack will
modify or intercept incoming requests before sending them to your upstream Service.
Filters define what actions to take on a request,
FilterPolicies define the matching criteria for requests, such as the headers, hostname, and path, and supply references to
one or more
Filters to execute against those requests. Filters are largely used to add built-in authentication and security, but
Ambassador Edge Stack also supports developing custom filters to add your own processing and logic.
This doc is an overview of all the fields on the
Filter Custom Resource with descriptions of the purpose, type, and default values of those fields.
This page is specific to the
getambassador.io/v3alpha1 version of the
Filter resource. For the newer
please see the v1alpha1 Filter api reference.
Filtering is configured using
Filter custom resources. The body of the resource
spec depends on the filter type:
ambassador_id, only one of the following fields may be configured. For example you cannot create a
Filter with both
|||Ambassador id accepts a list of strings that allow you to restrict which instances of Ambassador Edge Stack can use/view this resource. If |
|JWTFilter||Provides configuration for the JWT Filter type|
|OAuth2Filter||Provides configuration for the OAuth2 Filter type|
|APIKeyFilter||Provides configuration for the APIKey Filter type|
|ExternalFilter||Provides configuration for the External Filter type|
|PluginFilter||Provides configuration for the Plugin Filter type|