goreplay/k8s/rolebinding.yaml at master - goreplay - Gitea: Git with a cup of tea

github/goreplay

mirror of https://github.com/buger/goreplay.git synced 2024-04-21 12:32:02 +00:00

Files

T

Leonid BugaevandGitHub d440b3dc8f K8s native support (#1052 )

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

2022-02-12 21:01:03 +03:00

13 lines

243 B

YAML

Raw Permalink Blame History

 kind: ClusterRoleBinding
 apiVersion: rbac.authorization.k8s.io/v1
 metadata:
   name: goreplay-reader-binding
 subjects:
 - kind: ServiceAccount
   name: goreplay
   namespace: goreplay
 roleRef:
   kind: ClusterRole
   name: pod-reader
   apiGroup: ""