network-mapper
CoreDNS
network-mapper | CoreDNS | |
---|---|---|
10 | 41 | |
570 | 11,811 | |
0.5% | 0.8% | |
8.7 | 9.3 | |
3 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
CoreDNS
-
Small DNS Server That Support Outgoing Address Binding?
CoreDNS supports this via the bind plugin.
- The Tailscale Universal Docker Mod
-
How to use Cloudflare 1.1.1.1 with Kubernetes DNS
I'd like to use Cloudflare's 1.1.1.1 and 1.0.0.1 nameservers in Kubernetes, alongside DNS over TLS. It looks like I can do it using core-dns. I need to setup the following somehow:
-
Dockerize Bind9 DNS with custom image
Shamless plug for CoreDNS. Much better DNS server than classic bind9. And of course there's already a nice container image for it.
-
Kubernetes traffic discovery
But another approach that could work in Kubernetes, because the DNS servers are within the cluster itself, would be to work directly with the DNS server pods. In most Kubernetes clusters, whether standalone or managed (GKE, AKS, EKS), the cluster DNS is either coredns or kube-dns. That was great to minimize how much configuration options we’d need to support. We realized we could edit the coredns or kube-dns configmap resources to enable their log option, which would make them log all the queries they handle. We’ll cover exactly how it’s done in more detail below.
-
Self hosted DNS server that responds to queries with data from web API?
CoreDNS has an ectd plugin, so your service could add entries to a database, which is used as record source. Not the same mechanism as you have described, but it will get the job done. Also this is what Kubetnetes does for incluster dns records.
-
Upgrade CoreDNS without downtime and without kubernetes
nevermind there's caddy builtin upgrade method https://github.com/coredns/coredns/issues/6034
-
Guide for using DNS with home lab servers?
Coredns can be spun up in a docker container, just starting to get into it myself
-
What would you rewrite in Golang?
CoreDNS is a pretty good DNS server.
-
Cool networking projects in golang
Core DNS (https://coredns.io).
What are some alternatives?
echopod - The minimal HTTP server that provides info about container/pod.
PowerDNS - PowerDNS Authoritative, PowerDNS Recursor, dnsdist
tic-tac-toe - 🎮 Tic Tac Toe implementation over network 🌐
blocky - Fast and lightweight DNS proxy as ad-blocker for local network with many features
intents-operator - Manage network policies, AWS, GCP & Azure IAM policies, Istio Authorization Policies, and Kafka ACLs in a Kubernetes cluster with ease.
Pi-hole - A black hole for Internet advertisements
grafana-operator - An operator for Grafana that installs and manages Grafana instances, Dashboards and Datasources through Kubernetes/OpenShift CRs
nsupdate.info - Dynamic DNS service
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
etcd - Distributed reliable key-value store for the most critical data of a distributed system
kubetunnel - Develop microservices locally while being connected to your Kubernetes environment
cni - Container Network Interface - networking for Linux containers