network-mapper
grafana-operator
| network-mapper | grafana-operator | |
|---|---|---|
| 10 | 3 | |
| 570 | 785 | |
| 0.5% | 3.7% | |
| 8.7 | 9.5 | |
| 2 days ago | 4 days ago | |
| Go | Go | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
network-mapper
- Network Mapper – low privileges, no-eBPF network observability tool for K8s
-
Otterize launches open-source, declarative IAM permissions for workloads on AWS EKS clusters
Yep! When you deploy Otterize, you get a map of your cluster’s traffic, with zero-configuration, through the open-source network-mapper.
-
Kubernetes traffic discovery
After multiple iterations, research sessions and some trial & error, we could produce an exportable list of network connections in any Kubernetes cluster. You might recall that our larger goal was to get to a logical (functional) map of pod-to-pod traffic, and that will be covered in a future posting. After adding that capability, here’s an example output from our project, now called network-mapper, when pointed at one of the clusters in our “lab” environment:
- Show HN: Visualize Kubernetes Clusters
-
Visualizing Kubernetes traffic, the non-invasive way
It'll require some changes but you can go for it if that's something up your alley, as after all, it's all open source - https://github.com/otterize/network-mapper
- GitHub - otterize/network-mapper: Map Kubernetes in-cluster traffic and export as text, intents, or an image
-
Open-source Kubernetes traffic visualizer - Otterize network mapper
We received some great feedback from the community regarding our tool, and one of the most commonly requested features was visualization. So we embedded this functionality into the tool, and now you can easily map and visualize your cluster with a single CLI command.
-
Alternative to Network Policys
As you've mentioned, it is not possible to define deny rules using the native NetworkPolicy resource. Instead, you could use your CNI’s implementation for network policies. If you use Calico as your CNI you can use Calico's network policies to create deny rules. You can also take a look at Otterize OSS, an open-source solution my team and I are working on recently. It simplifies network policies by defining them from the client’s perspective in a ClientIntents resource. You can use the network mapper to auto-generate those ClientIntents from the traffic in your cluster, and then deploy them and let the intents-operator manage the network policies for you.
- Otterize network mapper - map Kubernetes in-cluster traffic with zero-config
grafana-operator
-
How to detect whether cluster is openshift?
Have a look at https://github.com/grafana-operator/grafana-operator/blob/master/controllers/autodetect/main.go :)
-
Cheapest monitoring solution for AWS?
If you run your instance on EKS with the grafana operator then you can install them like any other cuszom resource. (Not sure if you are using Fargate with ECS or EKS) https://github.com/grafana-operator/grafana-operator/blob/master/documentation/dashboards.md
- The ConfigMap is invalid: metadata.annotations: Too long: must have at most 262144 characters
What are some alternatives?
echopod - The minimal HTTP server that provides info about container/pod.
parca - Continuous profiling for analysis of CPU and memory usage, down to the line number and throughout time. Saving infrastructure cost, improving performance, and increasing reliability.
tic-tac-toe - 🎮 Tic Tac Toe implementation over network 🌐
opentelemetry-go-instrumentation - OpenTelemetry auto-instrumentation for Go applications
intents-operator - Manage network policies, AWS, GCP & Azure IAM policies, Istio Authorization Policies, and Kafka ACLs in a Kubernetes cluster with ease.
hyperconverged-cluster-operator - Operator pattern for managing multi-operator products
kubeshark - The API traffic analyzer for Kubernetes providing real-time K8s protocol-level visibility, capturing and monitoring all traffic and payloads going in, out and across containers, pods, nodes and clusters. Inspired by Wireshark, purposely built for Kubernetes
gatus - ⛑ Automated developer-oriented status page
kubetunnel - Develop microservices locally while being connected to your Kubernetes environment
argocd-operator - A Kubernetes operator for managing Argo CD clusters.
CoreDNS - CoreDNS is a DNS server that chains plugins
mongodb-operator - A golang based operator to create and manage MongoDB standalone setup and cluster setup