
An Overview of Traffic Mirroring Options in Kubernetes
There are many ways to implement traffic mirroring in Kubernetes. This post helps you make an informed decision on what to choose.
Speedscale listens to late-stage Kubernetes environments via Istio or sidecar, and redacts PII. You can also use Postman collections to feed in data.
This traffic can be reviewed, filtered and distilled into snapshots that run as tests and mocks, with no scripting required.
Since Speedscale observes PII-redacted traffic, this data can be viewed in our Traffic Viewer to debug problems, do root-cause analysis and understand API behavior. PII and sensitive data redaction included.
Speedscale can automatically detect and mock your dependencies.
Service mocks are simulators that accept outbound requests from your app and mimic responses coming back from 3rd parties.
Speedscale mocks contain PII-redacted, sanitized traffic so you don’t need to worry about sensitive data being used.
"chaos": {
"chaosPercent":25,
"badStatusCodes": true,
"intermittentResponses": true,
"randomLatency": true,
"randomHighLatencyMs": 5000
}
Traffic replay pods are ran locally in your clusters by a Kubernetes operator for traffic replay.
Test results are logged and sent to Speedscale for analysis and reporting. Pods are cleaned up afterward to return the cluster to the original state.
There are many ways to implement traffic mirroring in Kubernetes. This post helps you make an informed decision on what to choose.
Kubernetes preview environments as a concept is growing steadily in popularity, but what are they, and how are they used?
There are many moving parts when implementing production traffic replication. This post attempts to give you an idea of what role traffic replay plays.