Hi @nitindhiman314e
Usually you shouldn't see any packet loss as long as the Worker enjoys sufficient resources. In these situations you can either increase resources or use backend filters to reduce the amount of traffic that will be processed.

Hi @nitindhiman314e Usually you shouldn't see any packet loss as long as the Worker enjoys sufficient resources. In these situations you can either increase resources or use backend filters to reduce the amount of traffic that will be processed.

Hi @alongir,

Thank you for your reply. I currently have 4 nodes, and the corresponding 4 Kubeshark workers are running. Out of these, 2 workers have been running for the last 35 hours without any dropped packets. However, the other 2 are restarting intermittently and showing a high packet loss count. Below are the daemon worker resource limits we are using:

resources:
  limits:
    memory: 5Gi
  requests:
    cpu: '1'
    memory: 50Mi

I have also attached the current usage of the Kubeshark workers. Could you please suggest any tuning recommendations?
Regarding the worker restarts, we encountered the following error:

Back-off restarting failed container sniffer in pod kubeshark-worker-daemon-set-8tk5l_kubeshark (ee32d21b-85be-49e6-8120-7fab7e986ad2)

Thanks!