TrueCloudLab/coredns
16
0
Fork 2
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

Directive -> plugin (#3363)

Browse source 
Caught my eye, we name things directive still, esp when talking about
the prometheus *plugin*. Rename everything that needs to be plugin to
'plugin'. Also make sure Metrics is a H2 section (not H1).

Signed-off-by: Miek Gieben <miek@miek.nl>
This commit is contained in:
Miek Gieben 2019-10-08 10:20:48 +01:00 • committed by GitHub
parent ffe6225ff6
commit 65458b2de2
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
15 changed files with 20 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

4
plugin/kubernetes/README.md
View file

@ -24,7 +24,7 @@ This plugin can only be used once per Server Block.
kubernetes [ZONES...]
~~~
With only the directive specified, the *kubernetes* plugin will default to the zone specified in
With only the plugin specified, the *kubernetes* plugin will default to the zone specified in
the server's block. It will handle all queries in that zone and connect to Kubernetes in-cluster. It
will not provide PTR records for services or A records for pods. If **ZONES** is used it specifies
all the zones the plugin should be authoritative for.
@ -231,7 +231,7 @@ plugin is also enabled:
## Metrics
If monitoring is enabled (via the *prometheus* directive) then the following metrics are exported:
If monitoring is enabled (via the *prometheus* plugin) then the following metrics are exported:
* `coredns_kubernetes_dns_programming_duration_seconds{service_kind}` - Exports the
[DNS programming latency SLI](https://github.com/kubernetes/community/blob/master/sig-scalability/slos/dns_programming_latency.md).