mirror of
https://github.com/kubernetes-sigs/external-dns.git
synced 2025-12-12 07:11:25 +01:00
0dbead2208
* docs(core-dns): update tutorial Signed-off-by: ivan katliarchuk <ivan.katliarchuk@gmail.com> * docs(core-dns): update tutorial Signed-off-by: ivan katliarchuk <ivan.katliarchuk@gmail.com> * docs(core-dns): update tutorial Signed-off-by: ivan katliarchuk <ivan.katliarchuk@gmail.com> * docs(core-dns): update tutorial Signed-off-by: ivan katliarchuk <ivan.katliarchuk@gmail.com> * docs(core-dns): update tutorial Signed-off-by: ivan katliarchuk <ivan.katliarchuk@gmail.com> * docs(core-dns): update tutorial Co-authored-by: Michel Loiseleur <97035654+mloiseleur@users.noreply.github.com> --------- Signed-off-by: ivan katliarchuk <ivan.katliarchuk@gmail.com> Co-authored-by: Michel Loiseleur <97035654+mloiseleur@users.noreply.github.com>
743 B
743 B
CoreDNS
Specific service annotation options
Groups
Groups can be used to group set of services together. The main use of this is to limit recursion, i.e. don't return all records, but only a subset. Let's say we have a configuration like this:
[[% include 'tutorials/coredns/coredns-groups.yaml' %]]
And we want domain.local to return (127.0.0.1 and 127.0.0.2) and subdom.domain.local to return (127.0.0.3 and 127.0.0.4). For this the two domains, need to be in different groups. What those groups are does not matter, as long as a and b belong to the same group which is different from the group c and d belong to. If a service is found without a group it is always included.