You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Has anyone gotten kubeshark to work with bottlerocket?
I can't get the worker pods to startup; get a cgroup error in sniffer logs and the pod refuses connections on 30001, no other errors in the worker logs.
The tracer is even worse; ended up turning that off : error="field GoCryptoTlsAbi0Read: program go_crypto_tls_abi0_read: apply CO-RE relocations: can't read types: type id 11360: unknown kind: Unknown (19)"
Provide more information
EKS (1.28)
Bottlerocket OS 1.17.0 (aws-k8s-1.28)
6 nodes but only binding 1 via afifinity
AWS CNI with NetworkPolicy enabled (v1.16.2-eksbuild.1)
kubeshark (v52.1.30)
To Reproduce
Steps to reproduce the behaviour:
Run kubeshark tap
Get pods
See pods are not starting up.
Describe failing pod - :30001: connect: connection refused
Check logs - sniffer has 1 ERR; tracer has 1 FTL Expected behaviour
kubeshark-worker pod starts up successfully.
Logs
kubeshark-worker -- describe
Warning BackOff 2m39s (x2 over 2m40s) kubelet Back-off restarting failed container tracer in pod kubeshark-worker-daemon-set-6z7qh_default(158a19c6-503d-483d-81ca-9a5c722229df)
Warning Unhealthy 2m37s (x4 over 2m39s) kubelet Readiness probe failed: dial tcp 10.205.90.30:30001: connect: connection refused
Warning Unhealthy 2m37s (x3 over 2m39s) kubelet Liveness probe failed: dial tcp 10.205.90.30:30001: connect: connection refused
2024-02-08T01:18:13Z INF main.go:73 > Starting worker...
2024-02-08T01:18:13Z ERR main.go:87 > While setting the memory limit error="Unable to parse the cgroup file"
2024-02-08T01:18:13Z INF main.go:95 > Memory limit is set to limit=800000000
2024-02-08T01:18:13Z INF main.go:100 > Starting worker...
2024-02-08T01:18:13Z INF misc/data.go:24 > Set the data directory to: data-dir=/app/data/ip-10-205-90-30.ap-southeast-2.compute.internal
2024/02/08 01:18:14 [DEBUG] GET http://kubeshark-hub:80/resolver/history
2024/02/08 01:18:15 [DEBUG] GET http://kubeshark-hub:80/resolver/history
kubeshark-worker -- tracer
2024-02-08T01:17:55Z INF tracer/misc/data.go:17 > Set the data directory to: data-dir=data
2024-02-08T01:17:55Z INF tracer/main.go:47 > Starting tracer...
2024-02-08T01:17:55Z INF tracer/tracer.go:39 > Initializing tracer (chunksSize: 40960000) (logSize: 4096)
2024-02-08T01:17:55Z INF tracer/tracer.go:53 > Detected Linux kernel version: 6.1.61
2024-02-08T01:17:55Z FTL tracer/main.go:68 > Couldn't initialize the tracer: error="field GoCryptoTlsAbi0Read: program go_crypto_tls_abi0_read: apply CO-RE relocations: can't read types: type id 11360: unknown kind: Unknown (19)"
kubeshark-worker -- load-pf-ring
No pf_ring module found for the current kernel version 6.1.61
Falling back to AF_PACKET
No dump logs when running with kubeshark tap --set dump-logs=true
The text was updated successfully, but these errors were encountered:
Describe the bug
Has anyone gotten kubeshark to work with bottlerocket?
I can't get the worker pods to startup; get a cgroup error in sniffer logs and the pod refuses connections on 30001, no other errors in the worker logs.
The tracer is even worse; ended up turning that off :
error="field GoCryptoTlsAbi0Read: program go_crypto_tls_abi0_read: apply CO-RE relocations: can't read types: type id 11360: unknown kind: Unknown (19)"
Provide more information
EKS (1.28)
Bottlerocket OS 1.17.0 (aws-k8s-1.28)
6 nodes but only binding 1 via afifinity
AWS CNI with NetworkPolicy enabled (v1.16.2-eksbuild.1)
kubeshark (v52.1.30)
To Reproduce
Steps to reproduce the behaviour:
kubeshark tap
:30001: connect: connection refused
Expected behaviour
kubeshark-worker pod starts up successfully.
Logs
kubeshark-worker -- describe
kubeshark-worker -- get
kubeshark-worker -- sniffer
kubeshark-worker -- tracer
kubeshark-worker -- load-pf-ring
No dump logs when running with
kubeshark tap --set dump-logs=true
The text was updated successfully, but these errors were encountered: