mirror of
https://github.com/buger/goreplay.git
synced 2024-04-21 12:32:02 +00:00
Now you are be able to capture traffic inside k8s like this: ``` gor --input-raw k8s://namespace/deployment/app:80 --output-http http://replay.com ``` Supported format for filtering required pods: ``` k8s://[namespace/]pod/[pod_name] - k8s://default/pod/nginx-7848d4b86f-5nxz8 k8s://[namespace/]deployment/[deployment_name] - k8s://default/deployment/nginx k8s://[namespace/]daemonset/[daemonset_name] - k8s://default/daemonset/nginx k8s://[namespace/]labelSelector/[selector] - k8s://default/labelSelector/app=nginx k8s://[namespace/]fieldSelector/[selector] - k8s://default/fieldSelector/metadata.name=nginx-7848d4b86f-5nxz8 ``` `namespace` is optional, omit to use all namespaces: `k8s://labelSelector/app=replay` GoReplay designed to be running running as a daemonset (e.g. on each physical k8s node). See the full guide in here: https://github.com/buger/goreplay/blob/ca8205a5c5d2a1facb00214c78e4120aae6d772d/k8s/README.md
15 lines
351 B
YAML
15 lines
351 B
YAML
apiVersion: apps/v1
|
||
kind: DaemonSet
|
||
metadata:
|
||
name: goreplay-daemon
|
||
spec:
|
||
template:
|
||
spec:
|
||
hostNetwork: true
|
||
serviceAccountName: goreplay
|
||
containers:
|
||
- name: goreplay
|
||
image: buger/goreplay:2.0.0-rc2
|
||
command:
|
||
- "--input-raw k8s://deployments/nginx:80"
|
||
- "--output-stdout" |