v2.0.9

What's Changed

• Improve load balancer service resolution - support shared external ip address by @omris94 in #238
• FIx bug where hostNetwork pods could be falsely detected as incoming traffic from outside of the cluster; Support resolution of LoadBalancer typed services using their node ports by @omris94 in #240
• Fix bug where discovered traffic from a pod wasn't filtered properly by its creation timestamp by @omris94 in #243

Full Changelog: v2.0.8...v2.0.9

v2.0.7

What's Changed

• Fix error reporting - use the enum graphql type instead of a free string by @omris94 in #232

Full Changelog: v2.0.6...v2.0.7

v2.0.6

What's Changed

• Ignore target hostNetwork pods in the DNS capture flow by @omris94 in #231

Full Changelog: v2.0.5...v2.0.6

v2.0.5

What's Changed

• Fix a bug where the source hostnames weren't enforced on TCP capture results for AWS; Add a configuration key to define the time a server-pod has to live for us to trust it's IP by @omris94 in #227
• Fix a bug where a TCP connection to a hostNetwork pod could rarely be resolved to the wrong service by @omris94 in #228
• Improve the way we resolve services DNS to identities by going directly from the targetRef of endpoints instead of going through IP addresses by @omris94 in #229

Full Changelog: v2.0.4...v2.0.5

v2.0.4

What's Changed

• Fix a bug where internet intents discovered with CNAME instead of the actual domain name by @NetanelBollag in #223
• Preparation for the release of ClientIntents v2 by @omris94 in #221 #226

Full Changelog: v2.0.3...v2.0.4

v2.0.3

What's Changed

• Support cross cluster visibility by @NetanelBollag in #220
• Report TCP sniffing count telemetry by @NetanelBollag in #218

Full Changelog: v2.0.2...v2.0.3

v2.0.2

What's Changed

• Fix bug where incorrect stack traces would be reported for sentinel errors by @orishoshan in #213
• Add stack traces to panics reported in telemetry error reporting by @orishoshan in #215
• Fix bug that would cause harmless errors to be logged when a Service was deleted by the time resolution happened by @orishoshan in #216
• Enable DNS resolution for DNS ClientIntents by default by @NetanelBollag in #217

Full Changelog: v2.0.1...v2.0.2

v2.0.1

What's Changed

• Fix cases where errors would not be reported to telemetry or would be reported with wrong stack by @orishoshan in #202
• Fix bug where external ingress traffic detection would fail if more than one pod was found with the IP in cluster when determining if traffic is external by @orishoshan in #214

Full Changelog: v2.0.0...v2.0.1

v2.0.0

What's Changed

• Updated cluster ID generation to match cluster ID used for PostgreSQL enforcement which, is supported in the new v2.0.0 versions of intents-operator & credentials-operator.
  by @evyatarmeged in #211

Full Changelog: v1.2.9...v2.0.0

v1.2.9

What's Changed

• Change TCP log to trace to reduce logging verbosity by default by @orishoshan in #209
• Fixed bug where external traffic reporting would fail if node pod CIDRs were not populated by @orishoshan in #210

Full Changelog: v1.2.8...v1.2.9