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

Fix plugin name in project README (#3683)

Browse source 
* Update README.md

Signed-off-by: Chris O'Haver <cohaver@infoblox.com>

* fix readme occurances

Signed-off-by: Chris O'Haver <cohaver@infoblox.com>
This commit is contained in:
Chris O'Haver 2020-03-26 10:24:56 -04:00 • committed by GitHub
parent 8584c6ce60
commit 5cd8472384
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -33,7 +33,7 @@ Currently CoreDNS is able to:
* Use etcd as a backend (replacing [SkyDNS](https://github.com/skynetservices/skydns)) (*etcd*).
* Use k8s (kubernetes) as a backend (*kubernetes*).
* Serve as a proxy to forward queries to some other (recursive) nameserver (*forward*).
* Provide metrics (by using Prometheus) (*metrics*).
* Provide metrics (by using Prometheus) (*prometheus*).
* Provide query (*log*) and error (*errors*) logging.
* Integrate with cloud providers (*route53*).
* Support the CH class: `version.bind` and friends (*chaos*).

2
plugin/cache/README.md vendored
View file

@ -77,7 +77,7 @@ If monitoring is enabled (via the *prometheus* plugin) then the following metric
* `coredns_cache_served_stale_total{server}` - Counter of requests served from stale cache entries.
Cache types are either "denial" or "success". `Server` is the server handling the request, see the
metrics plugin for documentation.
prometheus plugin for documentation.
## Examples

2
plugin/reload/README.md
View file

@ -86,7 +86,7 @@ is already listening on that port. The process reloads and performs the followin
4. fail loading the new Corefile, abort and keep using the old process
After the aborted attempt to reload we are left with the old processes running, but the listener is
closed in step 1; so the health endpoint is broken. The same can happen in the prometheus metrics plugin.
closed in step 1; so the health endpoint is broken. The same can happen in the prometheus plugin.
In general be careful with assigning new port and expecting reload to work fully.