このページは、まだ日本語ではご利用いただけません。翻訳中です。
Fault Injection
New to Kuma? You need this policy, check
MeshFaultInjection
instead.
Fault Injection is an inbound policy. Dataplanes whose configuration is modified are in the
destinations
matcher.
FaultInjection
policy helps you to test your microservices against resiliency. Kong Mesh provides 3 different types of failures that could be imitated in your environment.
These faults are Delay, Abort and ResponseBandwidth limit.
Usage
Sources & Destinations
FaultInjection
is a policy, which is applied to the connection between dataplanes. As most of the policies, FaultInjection
supports the powerful mechanism of matching, which allows you to precisely match source and destination dataplanes.
FaultInjection
policy is available only for L7 HTTP traffic, thereforekuma.io/protocol
is a mandatory tag for the destination selector and must be of valuehttp
,http2
orgrpc
.
HTTP Faults
At least one of the following Faults should be specified.
Abort
Abort defines a configuration of not delivering requests to destination service and replacing the responses from destination dataplane by predefined status code.
-
httpStatus
- HTTP status code which will be returned to source side -
percentage
- percentage of requests on which abort will be injected, has to be in [0.0 - 100.0] range
Delay
Delay defines configuration of delaying a response from a destination.
-
value
- the duration during which the response will be delayed -
percentage
- percentage of requests on which delay will be injected, has to be in [0.0 - 100.0] range
ResponseBandwidth limit
ResponseBandwidth defines a configuration to limit the speed of responding to the requests.
-
limit
- represented by value measure in gbps, mbps, kbps or bps, e.g. 10kbps -
percentage
- percentage of requests on which response bandwidth limit will be injected, has to be in [0.0 - 100.0] range
Matching
FaultInjection
is an Inbound Connection Policy.
You can use all the tags in both sources
and destinations
sections.