Releases: otterize/network-mapper
Releases · otterize/network-mapper
v2.0.17
What's Changed
- Report AWS operations with service identity by @orishavit in #258
Full Changelog: v2.0.16...v2.0.17
v2.0.16
What's Changed
- Consolidate mapperclient packages by @orishavit in #257
- Adding support for wildcard prefix in DNS internet intents (*.example.com) by @evyatarmeged in #256
Full Changelog: v2.0.15...v2.0.16
v2.0.15
v2.0.14
What's Changed
- Update Otterize Cloud GraphQL schema to latest version by @orishavit in #251
- Report Azure discovered intents by @orishavit in #252
- Update GraphQL schema to latest version by @orishavit in #253
- Use ClientName[space] as service identity name instead of as pod name in Azure reporting by @orishavit in #254
Full Changelog: v2.0.13...v2.0.14
v2.0.13
What's Changed
- Handle case where the sniffer could fail to start if the metrics port was taken by another process on the same node, due to hostNetwork by @orishoshan in #249
Full Changelog: v2.0.12...v2.0.13
v2.0.12
What's Changed
- Fix bug where sniffer would not stop gracefully upon context cancellation by @orishoshan in #248
Full Changelog: v2.0.11...v2.0.12
v2.0.11
What's Changed
- Reduce the risk of misidentification of incoming traffic by verifying destination hostname when resolving incoming internet traffic; Use
/proc/<pid>/root/etc/hostname
for IP to hostname resolution as an alternative to/proc/<pid>/environ
by @omris94 in #244 - Fix a bug where detected TCP traffic from pods a short time before their deletion time could be labeled as incoming traffic from the internet by @omris94 in #245
Full Changelog: v2.0.10...v2.0.11
v2.0.10
What's Changed
- Fix rare issue concerning captures going stale on the AWS VPC CNI, as well as auto-resolve addresses with no currently seen DNS traffic in the cluster by @orishoshan in #242
Full Changelog: v2.0.9...v2.0.10
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 ofLoadBalancer
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