diff options
author | 2019-03-07 22:13:47 +0000 | |
---|---|---|
committer | 2019-03-07 22:13:47 +0000 | |
commit | c778b3a67ca43124a539acda21eca4934c8110f6 (patch) | |
tree | 6c012c1a6d7fe4fb5a2f7d9985c8b9b8f3d0f7ec /plugin.md | |
parent | db0b16b615c5397628f392de6dd131d4cbc148d9 (diff) | |
download | coredns-c778b3a67ca43124a539acda21eca4934c8110f6.tar.gz coredns-c778b3a67ca43124a539acda21eca4934c8110f6.tar.zst coredns-c778b3a67ca43124a539acda21eca4934c8110f6.zip |
plugin/health: remove ability to poll other plugins (#2547)
* plugin/health: remove ability to poll other plugins
This mechanism defeats the purpose any plugin (mostly) caching can still
be alive, we can probably forward queries still. Don't poll plugins,
just tell the world we're up and running.
It was only actually used in kubernetes; and there specifically would
mean any network hiccup would NACK the entire server health.
Fixes: #2534
Signed-off-by: Miek Gieben <miek@miek.nl>
* update docs based on feedback
Signed-off-by: Miek Gieben <miek@miek.nl>
Diffstat (limited to 'plugin.md')
-rw-r--r-- | plugin.md | 5 |
1 files changed, 1 insertions, 4 deletions
@@ -59,10 +59,7 @@ When exporting metrics the *Namespace* should be `plugin.Namespace` (="coredns") *Subsystem* should be the name of the plugin. The README.md for the plugin should then also contain a *Metrics* section detailing the metrics. -If the plugin supports dynamic health reporting it should also have *Health* section detailing on -some of its inner workings. - -If the plugins supports signalling readiness it should have a *Ready* section detailing how it +If the plugin supports signalling readiness it should have a *Ready* section detailing how it works. ## Documentation |