Skip to content

C
Coredns
Switch branch/tag
This project is mirrored from https://github.com/coredns/coredns.git. The repository failed to update .
Repository mirroring has been paused due to too many failed attempts, and can be resumed by a project maintainer.
Last successful update .
  1. 21 Dec, 2021 1 commit
  3. 18 Dec, 2021 1 commit
  5. 14 Dec, 2021 1 commit
  7. 13 Dec, 2021 4 commits
  9. 10 Dec, 2021 5 commits
  11. 09 Dec, 2021 1 commit
  13. 07 Dec, 2021 1 commit
  15. 06 Dec, 2021 2 commits
  17. 01 Dec, 2021 1 commit
  19. 30 Nov, 2021 2 commits
  21. 25 Nov, 2021 1 commit
  23. 24 Nov, 2021 3 commits
  25. 23 Nov, 2021 4 commits
  27. 22 Nov, 2021 2 commits
  29. 20 Nov, 2021 3 commits
  31. 18 Nov, 2021 1 commit
  33. 16 Nov, 2021 1 commit
  35. 15 Nov, 2021 2 commits
  37. 14 Nov, 2021 1 commit
  39. 13 Nov, 2021 3 commits
    • Chris O'Haver's avatar
      Revert "Initial implementation of ForwardCRD plugin (#4512)" (#4981) · 3288b111
      Chris O'Haver authored 
      This reverts commit 2e6953c7.
      3288b111
    • Christian Ang's avatar
      Initial implementation of ForwardCRD plugin (#4512) · 2e6953c7
      Christian Ang authored 
      * Add forwardcrd plugin README.md
Co-authored-by: default avatarAidan Obley <aobley@vmware.com>
Signed-off-by: default avatarChristian Ang <angc@vmware.com>

* Create forwardcrd plugin

- Place forwardcrd before forward plugin in plugin list. This will avoid
forward from preventing the forwardcrd plugin from handling any queries
in the case of having a default upstream forwarder in a server block (as
is the case in the default kubernetes Corefile).
Co-authored-by: default avatarAidan Obley <aobley@vmware.com>
Signed-off-by: default avatarChristian Ang <angc@vmware.com>

* Add Forward CRD
Signed-off-by: default avatarChristian Ang <angc@vmware.com>

* Add NewWithConfig to forward plugin

- allows external packages to instanciate forward plugins
Co-authored-by: default avatarAidan Obley <aobley@vmware.com>
Signed-off-by: default avatarChristian Ang <angc@vmware.com>

* ForwardCRD plugin handles requests for Forward CRs

- add a Kubernetes controller that can read Forward CRs
- instances of the forward plugin are created based on Forward CRs from
the Kubernetes controller
- DNS requests are handled by calling matching Forward plugin instances
based on zone name
- Defaults to the kube-system namespace to align with Corefile RBAC
Signed-off-by: default avatarChristian Ang <angc@vmware.com>

Use klog v2 in forwardcrd plugin

* Refactor forward setup to use NewWithConfig
Co-authored-by: default avatarChristian Ang <angc@vmware.com>
Signed-off-by: default avatarEdwin Xie <exie@vmware.com>

* Use ParseInt instead of Atoi

- to ensure that the bitsize is 32 for later casting to uint32
Signed-off-by: default avatarChristian Ang <angc@vmware.com>

* Add @christianang to CODEOWNERS for forwardcrd
Signed-off-by: default avatarChristian Ang <angc@vmware.com>
Co-authored-by: default avatarEdwin Xie <exie@vmware.com>
      2e6953c7
    • Miek Gieben's avatar
      Metrics: expand coredns_dns_responses_total with plugin label (#4914) · 6953ab2b
      Miek Gieben authored 
      * Metrics: expand coredns_dns_responses_total with plugin label

This adds (somewhat hacky?) code to add a plugin label to the
coredns_dns_responses_total metric. It's completely obvlious to the
plugin as we just check who called the *recorder.WriteMsg method. We use
runtime.Caller( 1 2 3) to get multiple levels of callers, this should be
deep enough, but it depends on the dns.ResponseWriter wrapping that's
occuring.

README.md of metrics updates and test added in test/metrics_test.go to
check for the label being set.

I went through the plugin to see what metrics could be removed, but
actually didn't find any, the plugin push out metrics that make sense.

Due to the path fiddling to figure out the plugin name I doubt this
works (out-of-the-box) for external plugins, but I haven't tested that.
Signed-off-by: default avatarMiek Gieben <miek@miek.nl>

* better comment
Signed-off-by: default avatarMiek Gieben <miek@miek.nl>

* Metrics: expand coredns_dns_responses_total with plugin label

This adds (somewhat hacky?) code to add a plugin label to the
coredns_dns_responses_total metric. It's completely obvlious to the
plugin as we just check who called the *recorder.WriteMsg method. We use
runtime.Caller( 1 2 3) to get multiple levels of callers, this should be
deep enough, but it depends on the dns.ResponseWriter wrapping that's
occuring.

README.md of metrics updates and test added in test/metrics_test.go to
check for the label being set.

I went through the plugin to see what metrics could be removed, but
actually didn't find any, the plugin push out metrics that make sense.

Due to the path fiddling to figure out the plugin name I doubt this
works (out-of-the-box) for external plugins, but I haven't tested that.
Signed-off-by: default avatarMiek Gieben <miek@miek.nl>

* Update core/dnsserver/server.go
Co-authored-by: default avatardilyevsky <ilyevsky@gmail.com>

* Use [3]string
Signed-off-by: default avatarMiek Gieben <miek@miek.nl>

* imports
Signed-off-by: default avatarMiek Gieben <miek@miek.nl>

* remove dnstest changes
Signed-off-by: default avatarMiek Gieben <miek@miek.nl>

* revert
Signed-off-by: default avatarMiek Gieben <miek@miek.nl>

* Add some sleeps to make it less flaky
Signed-off-by: default avatarMiek Gieben <miek@miek.nl>

* Revert "Add some sleeps to make it less flaky"

This reverts commit b5c6655196e3ad570555f086832ceb1f48f6f2d5.

* Remove forward when not needed
Signed-off-by: default avatarMiek Gieben <miek@miek.nl>

* remove newline
Signed-off-by: default avatarMiek Gieben <miek@miek.nl>
Co-authored-by: default avatardilyevsky <ilyevsky@gmail.com>
      6953ab2b