otterize/network-mapper
Map Kubernetes traffic: in-cluster, to the Internet, and to AWS IAM and export as text, intents, or an image
30 Releases
Latest: 1y ago
v3.0.19Latest
📋 What's Changed
- Improve performance - prevent sending the same state to Otterize cloud more than once by @zohar7ch in https://github.com/otterize/network-mapper/pull/312
- Improve data accuracy in Otterize Cloud by periodically re-reporting data by @zohar7ch in https://github.com/otterize/network-mapper/pull/310
- Full Changelog: https://github.com/otterize/network-mapper/compare/v3.0.18...v3.0.19
v3.0.18
📋 What's Changed
- Support reporting webhook services to Otterize cloud, for supporting auto-allow traffic to webhook services in cloud shadow mode by @zohar7ch in https://github.com/otterize/network-mapper/pull/303
- Improve blocked traffic detection in Otterize Cloud by reporting container port names by @omris94 in https://github.com/otterize/network-mapper/pull/308
- Full Changelog: https://github.com/otterize/network-mapper/compare/v3.0.17...v3.0.18
v3.0.17
📋 What's Changed
- Fix bug where indexes were used before being initialized by the metadataReporter by @omris94 in https://github.com/otterize/network-mapper/pull/307
- Fixed bug where invalid Kafka servers configuration produced an empty error log by @omris94 in https://github.com/otterize/network-mapper/pull/306
- Full Changelog: https://github.com/otterize/network-mapper/compare/v3.0.16...v3.0.17
v3.0.16
📋 What's Changed
- Fixed a bug where the mapper cloud crash when using DNS based ClientIntents by @zohar7ch in https://github.com/otterize/network-mapper/pull/304
- Full Changelog: https://github.com/otterize/network-mapper/compare/v3.0.15...v3.0.16
v3.0.15
📋 What's Changed
- Added e2e test for kafka by @zohar7ch in https://github.com/otterize/network-mapper/pull/299
- Istio - changing metric collection from sidecar to include server source by @evyatarmeged in https://github.com/otterize/network-mapper/pull/301
- Full Changelog: https://github.com/otterize/network-mapper/compare/v3.0.14...v3.0.15
v3.0.14
📋 What's Changed
- Fixed a bug where Kafka server metadata was not reported properly to Otterize cloud @zohar7ch in https://github.com/otterize/network-mapper/pull/298
- Fixed a bug where Kafka intents were dropped @zohar7ch in https://github.com/otterize/network-mapper/pull/298
- Full Changelog: https://github.com/otterize/network-mapper/compare/v3.0.13...v3.0.14
v3.0.13
📋 What's Changed
- Improve efficiency of network policies reporter by filtering large annotations before sending them to the cloud by @omris94 in https://github.com/otterize/network-mapper/pull/293
- Report traffic originated from control plane by @zohar7ch in https://github.com/otterize/network-mapper/pull/291
- Enhance cloud app network insights and visibility by reporting the ip addresses of workloads by @omris94 in https://github.com/otterize/network-mapper/pull/294
- Fixed bug where discovered intents were dropped in the mapper when collecting and parsing data from the sniffer by @zohar7ch in https://github.com/otterize/network-mapper/pull/295
- Support reporting connection count for incoming Internet connections by @zohar7ch in https://github.com/otterize/network-mapper/pull/297
- Full Changelog: https://github.com/otterize/network-mapper/compare/v3.0.12...v3.0.13
v3.0.12
📋 What's Changed
- Report connections count between two workloads to Otterize cloud by @zohar7ch in https://github.com/otterize/network-mapper/pull/284
- Report connection count also for communication between workload in the cluster and outside of the cluster (Internet edge) by @zohar7ch in https://github.com/otterize/network-mapper/pull/290
- Report ciliumClusterWideNetworkPolicies to the cloud app for better real-time network insights by @omris94 in https://github.com/otterize/network-mapper/pull/292
- Full Changelog: https://github.com/otterize/network-mapper/compare/v3.0.11...v3.0.12
v3.0.11
📋 What's Changed
- Fix bug where reporting network policies from a namespace without any policies could cause an error by @omris94 in https://github.com/otterize/network-mapper/pull/289
- Full Changelog: https://github.com/otterize/network-mapper/compare/v3.0.10...v3.0.11
v3.0.10
📋 What's Changed
- Report network policies to the cloud for better insights on unused policies and blocked traffic by @omris94 in https://github.com/otterize/network-mapper/pull/285
- Full Changelog: https://github.com/otterize/network-mapper/compare/v3.0.9...v3.0.10
v3.0.9
📋 What's Changed
- Support the reporting of pod and namespace labels to the cloud to enable better network policy analysis by @omris94 in https://github.com/otterize/network-mapper/pull/283
- Reporting workloads that are marked with the Prometheus scraping annotation to support automatically create network policies to allow Prometheus scraping in Otterize cloud by @zohar7ch in https://github.com/otterize/network-mapper/pull/278
- Full Changelog: https://github.com/otterize/network-mapper/compare/v3.0.8...v3.0.9
v3.0.8
📋 What's Changed
- Fix issue with traffic originating from Kubernetes control plane not being detected correctly on GKE, by configuring control-plane-ipv4-cidr-subnet-mask by @amitlicht in https://github.com/otterize/network-mapper/pull/281
✨ New Contributors
- @zohar7ch made their first contribution in https://github.com/otterize/network-mapper/pull/282
- Full Changelog: https://github.com/otterize/network-mapper/compare/v3.0.6...v3.0.8
v3.0.7
📋 What's Changed
- Improve cloud clientIntents suggestions by informing the cloud when a workload is using the workloadName override annotation by @omris94 in https://github.com/otterize/network-mapper/pull/279
- Fix issue where invalid traffic reports were reported to Otterize Cloud by @orishavit in https://github.com/otterize/network-mapper/pull/280
- Full Changelog: https://github.com/otterize/network-mapper/compare/v3.0.5...v3.0.7
v3.0.6
📋 What's Changed
- Improve cloud clientIntents suggestions by informing the cloud when a workload is using the workloadName override annotation by @omris94 in https://github.com/otterize/network-mapper/pull/279
- Fix issue where invalid traffic reports were reported to Otterize Cloud by @orishavit in https://github.com/otterize/network-mapper/pull/280
- Full Changelog: https://github.com/otterize/network-mapper/compare/v3.0.5...v3.0.6
v3.0.5
📋 What's Changed
- Support for GCP IAM eBPF visibility by @orishoshan in https://github.com/otterize/network-mapper/pull/275
- Fix bug where the workload identity resolution algorithm could fail if an owner ref uses a wrong apiVersion or kind by @omris94 in https://github.com/otterize/network-mapper/pull/277
- Full Changelog: https://github.com/otterize/network-mapper/compare/v3.0.4...v3.0.5
v3.0.4
📋 What's Changed
- Add support for AWS role mapping by @otterobert in https://github.com/otterize/network-mapper/pull/273
- Fixed bug where HTTP_PROXY/HTTPS_PROXY were used for the Kubernetes HTTP client by @orishoshan in https://github.com/otterize/network-mapper/pull/274
- Full Changelog: https://github.com/otterize/network-mapper/compare/v3.0.3...v3.0.4
v3.0.3
📋 What's Changed
- Collect traffic levels data from node-agent and upload to cloud by @orishavit in https://github.com/otterize/network-mapper/pull/271
- Full Changelog: https://github.com/otterize/network-mapper/compare/v3.0.2...v3.0.3
v3.0.2
📋 What's Changed
- Fix bug where TCP SYN to a pod IP was not ignored on freshly started pods, potentially causing spammed discovered intents in cases of fast IP reuse by @omris94 in https://github.com/otterize/network-mapper/pull/272
- Full Changelog: https://github.com/otterize/network-mapper/compare/v3.0.1...v3.0.2
v3.0.1
📋 What's Changed
- Remove AWS visibility/IAMLive from network-mapper by @orishavit in https://github.com/otterize/network-mapper/pull/269
- Removes remaining references to deprecated proxy-based AWS visibility by @orishavit in https://github.com/otterize/network-mapper/pull/270
- Full Changelog: https://github.com/otterize/network-mapper/compare/v3.0.0...v3.0.1
v3.0.0
📋 What's Changed
- Support new API version for ClientIntents: v2beta1 by @omris94 in https://github.com/otterize/network-mapper/pull/267
- To learn more, [see the matching release in otterize/intents-operator](https://github.com/otterize/intents-operator/releases/tag/v3.0.0).
- Full Changelog: https://github.com/otterize/network-mapper/compare/v2.0.21...v3.0.0
v2.0.21
📋 What's Changed
- Added Linkerd sidecar reporting to discovered intents resolution data by @evyatarmeged in https://github.com/otterize/network-mapper/pull/266
- Full Changelog: https://github.com/otterize/network-mapper/compare/v2.0.20...v2.0.21
v2.0.20
📋 What's Changed
- Improve troubleshooting capabilities by sending the listening port of detected established connections from the sniffer to the mapper by @omris94 in https://github.com/otterize/network-mapper/pull/262
- Bump intents-operator version to include: Update terminology: Rename annotation `intents.otterize.com/service-name` to `intents.otterize.com/workload-name`, retaining support for backward compatibility by @omris94 in https://github.com/otterize/network-mapper/pull/265
- Support configurable health server port for sniffer to prevent possible errors on startup by @evyatarmeged in https://github.com/otterize/network-mapper/pull/264
- Full Changelog: https://github.com/otterize/network-mapper/compare/v2.0.19...v2.0.20
v2.0.19
📋 What's Changed
- Fixing panic caused by assignment happening before err check by @evyatarmeged in https://github.com/otterize/network-mapper/pull/263
- Full Changelog: https://github.com/otterize/network-mapper/compare/v2.0.18...v2.0.19
v2.0.18
📋 What's Changed
- Fix a bug where host networking traffic could be misclassified as control plane traffic on Minikube by @omris94 in https://github.com/otterize/network-mapper/pull/261
- Full Changelog: https://github.com/otterize/network-mapper/compare/v2.0.17...v2.0.18
v2.0.17
📋 What's Changed
- Report AWS operations with service identity by @orishavit in https://github.com/otterize/network-mapper/pull/258
- Full Changelog: https://github.com/otterize/network-mapper/compare/v2.0.16...v2.0.17
v2.0.16
📋 What's Changed
- Consolidate mapperclient packages by @orishavit in https://github.com/otterize/network-mapper/pull/257
- Adding support for wildcard prefix in DNS internet intents (*.example.com) by @evyatarmeged in https://github.com/otterize/network-mapper/pull/256
- Full Changelog: https://github.com/otterize/network-mapper/compare/v2.0.15...v2.0.16
v2.0.15
📋 What's Changed
- Enhance discovered intents by including details on identity resolution methods by @omris94 in https://github.com/otterize/network-mapper/pull/255
- Full Changelog: https://github.com/otterize/network-mapper/compare/v2.0.14...v2.0.15
v2.0.14
📋 What's Changed
- Update Otterize Cloud GraphQL schema to latest version by @orishavit in https://github.com/otterize/network-mapper/pull/251
- Report Azure discovered intents by @orishavit in https://github.com/otterize/network-mapper/pull/252
- Update GraphQL schema to latest version by @orishavit in https://github.com/otterize/network-mapper/pull/253
- Use ClientName[space] as service identity name instead of as pod name in Azure reporting by @orishavit in https://github.com/otterize/network-mapper/pull/254
- Full Changelog: https://github.com/otterize/network-mapper/compare/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 https://github.com/otterize/network-mapper/pull/249
- Full Changelog: https://github.com/otterize/network-mapper/compare/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 https://github.com/otterize/network-mapper/pull/248
- Full Changelog: https://github.com/otterize/network-mapper/compare/v2.0.11...v2.0.12
