Logs flooded with TLS handshake error: EOF

[meljishi]

Describe the bug:

The intents operator is flooding our logs with TLS handshake error: EOF errors. We are starting to implement network policies on the cluster but they don't seem to be working. Currently not enforced, just analyzing traffic.

Logs from the intents operator Number of logs on our system

Expected behaviour:

Intents operator should just see the created clientIntents and just report them for the network mapper to show on the app dashboard

Steps to reproduce the bug:

We're just following the simples road we can. No mtls involved (supposedly), no enforcement or anything, so there should be no connection errors

Anything else we need to know?:

Not that I can think of

Environment details::

• Kubernetes version:
• 1.30
• Cloud-provider/provisioner:
• GKE
• intents-operator image version:
• otterize/intents-operator:v2.0.11
• Install method: e.g. helm/static manifests
• Helm