Skip to content

Commit 1d78480

Browse files
authored
Merge pull request #76 from Kuadrant/core-dns
add core dns support blog
2 parents 88a9fb3 + 2237486 commit 1d78480

File tree

1 file changed

+36
-0
lines changed

1 file changed

+36
-0
lines changed

src/blog/core-dns-support.md

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
title: Alpha support for DNSPolicy using CoreDNS
3+
date: 2025-04-15
4+
author: Craig Brookes
5+
---
6+
7+
Kuadrant now offers an Alpha or "Preview" level integration with [CoreDNS](https://coredns.io/) as one of our DNS providers for the [DNSPolicy API](https://docs.kuadrant.io/latest/kuadrant-operator/doc/reference/dnspolicy/). This will allow you to define how you want your DNS to work for your gateway API based gateways whether that is a single gateway or multiple gateways across multiple clusters. The aim with this early support and release is to get this feature into users hands and allow them to experiment, ideally submit feature requests and discover what is missing and any changes we may need to make to our current design.
8+
9+
10+
### Why does this matter?
11+
12+
Until now, the Kuadrant DNS operator has only ever integrated with cloud DNS providers (route53, GCP and Azure). With the addition of CoreDNS as an option, you can now delegate a zone from any edge recursive DNS resolver to a set of CoreDNS instances on your own infrastructure. This means that if you have your own edge DNS server you can keep all of your DNS internally managed but still get the features offered by Kuadrant's and DNSPolicy.
13+
14+
15+
## What can you do with the CoreDNS integration?
16+
17+
Kuadrant has developed its own plug-in for CoreDNS. This currently allows us to support GEO, Weighted and Geo + Weighted DNS responses based on our existing DNSRecord and DNSPolicy resources. The plug-in is required in order to source the DNS records and meta-data from our existing custom resources. So you can use all the features of DNSPolicy with a CoreDNS provider with the exception of health checks and wildcard hosts currently (these will be added in the near future).
18+
19+
20+
21+
## How does it work
22+
23+
To find out more about how it works under the hood, take a look the the [design doc](https://github.com/Kuadrant/architecture/blob/main/docs/design/core-dns-integration.md)
24+
25+
26+
## Getting Started
27+
28+
To get started, take a look at the guide we have prepared. [CoreDNS Guide](https://github.com/Kuadrant/kuadrant-operator/blob/main/doc/user-guides/dns/core-dns.md)
29+
30+
## Whats next
31+
32+
- Support for Wildcard hosts
33+
- Support for HealthChecks
34+
- Exploring what is possible with more advanced policies leveraging on cluster metrics, data and CEL based conditions.
35+
36+
You can track what we are doing for the next iteration of CoreDNS support [here](https://github.com/Kuadrant/dns-operator/issues/447)

0 commit comments

Comments
 (0)