kubefed
CoreDNS
kubefed | CoreDNS | |
---|---|---|
7 | 41 | |
2,476 | 11,811 | |
- | 0.8% | |
6.6 | 9.3 | |
about 1 year ago | 5 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.
kubefed
-
Scaling Kubernetes to multiple clusters and regions
The project is similar (in spirit) to kubefed.
-
Build a Federation of Multiple Kubernetes Clusters With Kubefed V2
What Is KubeFed? KubeFed (Kubernetes Cluster Federation) allows you to use a single Kubernetes cluster to coordinate multiple Kubernetes clusters. It can deploy multiple-cluster applications in different regions and design for disaster recovery. To learn more about KubeFed: https://github.com/kubernetes-sigs/kubefed
-
Evolution of code deployment tools at Mixpanel
There's active work on a standard called kubefed [0] that is being worked on.
> I want a scale-to-zero node-pool in every region, and one kube master api for the world.
Personally, I'd generalize this to: "I want to describe the reliability requirements and configuration for my software and have an automated system solve for where, how many, when, and how to route to it"
I want to have something where I can say "I need to have high availability, lowest latency, and X GB of RAM and Y cores" and have a system automatically schedule me wherever compute is cheapest while also intelligently routing traffic to my servers based on client origins.
[0] - https://github.com/kubernetes-sigs/kubefed
-
Building a Kubernetes-based Solution in a Hybrid Environment by Using KubeMQ
Two of the more common approaches to deploying Kubernetes in hybrid environments are from cloud-to-cloud and cloud to on-prem. Whether this is from using a single control plane like Rancher, Platform9, or Gardener to create multiple clusters that are managed from a single location, or utilizing Kubernetes federation to create a cluster that spans different regions, this model has become a key feature offered by Kubernetes that has helped drive adoption.
-
Infrastructure Engineering — Deployment Strategies
This is made possible by the very nature of Kubernetes being a standard portable platform across cloud providers, ability to manage infrastructure as code, ability to setup networking between them whenever needed with the help of multi-cluster service meshes and also due to the ability to orchestrate the deployments using Kubefed and Crossplane.
-
Architecting your Cloud Native Infrastructure
And the interesting thing about networking in cloud is that it need not be just be limited to the cloud provider within your region but can span across multiple providers across multiple regions as needed and this is where projects like Kubefed, Crossplane definitely does help.
-
Infrastructure Engineering - Diving Deep
Projects like Kubefed and Crossplane are especially useful here since they help you to manage and orchestrate clusters and the requests you send across different cloud providers even if its going to be across regions.
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?
crossplane - The Cloud Native Control Plane
PowerDNS - PowerDNS Authoritative, PowerDNS Recursor, dnsdist
karmada - Open, Multi-Cloud, Multi-Cluster Kubernetes Orchestration
blocky - Fast and lightweight DNS proxy as ad-blocker for local network with many features
virtual-kubelet - Virtual Kubelet is an open source Kubernetes kubelet implementation.
Pi-hole - A black hole for Internet advertisements
velero - Backup and migrate Kubernetes applications and their persistent volumes
nsupdate.info - Dynamic DNS service
rook - Storage Orchestration for Kubernetes
etcd - Distributed reliable key-value store for the most critical data of a distributed system
OpenFaaS - OpenFaaS - Serverless Functions Made Simple
cni - Container Network Interface - networking for Linux containers