CoreDNS has put on a silly hat and thrown it in the air, becoming the fourth project to achieve graduate status from the Cloud Native Computing Foundation.
This means the DNS server and cloud native service discovery project is no longer in “incubation”, and now ranks alongside the CNCF’s other big hitters, Kubernetes, Prometheus and Envoy.
More crucially, perhaps, the CNCF recommends it as the default DNS for Kubernetes deployments. It also gets the nod for use for native cloud integration in hybrid cloud environments with AWS via AWS Route 53, and, before too long, Google Cloud DNS.
CoreDNS achieved incubation status less than a year ago, and since then has delivered 12 releases, and 35 built-in and 15 external plug-ins, according to the CNCF.
The project hit v1.3.1 earlier this month, described as a “fairly small release” ahead of some promised “backwards incompatible changes” in the upcoming v1.4.
CoreDNS currently has 100 contributors and 16 maintainers, and according to the CNCF is used in production by the likes of Bose, Trainline, SoundCloud and Skyscanner.
The project was kicked off in 2016 by Miek Gieben, who was then a Site Reliability Engineer at Google, which is why it’s no surprise it was written in Go.
Gieben is still involved in the project, but not so much that he can’t find time to apply his talents to other more outlets. Check out some of his Lego creations here.