mirror of
				https://github.com/coredns/coredns.git
				synced 2025-10-31 02:03:20 -04:00 
			
		
		
		
	plugin/reload: enable (#1587)
Couldn't revert the original commit, just manually perform the needed tweaks.
This commit is contained in:
		| @@ -11,6 +11,7 @@ package dnsserver | |||||||
| // care what plugin above them are doing. | // care what plugin above them are doing. | ||||||
| var Directives = []string{ | var Directives = []string{ | ||||||
| 	"tls", | 	"tls", | ||||||
|  | 	"reload", | ||||||
| 	"nsid", | 	"nsid", | ||||||
| 	"root", | 	"root", | ||||||
| 	"bind", | 	"bind", | ||||||
|   | |||||||
| @@ -28,6 +28,7 @@ import ( | |||||||
| 	_ "github.com/coredns/coredns/plugin/nsid" | 	_ "github.com/coredns/coredns/plugin/nsid" | ||||||
| 	_ "github.com/coredns/coredns/plugin/pprof" | 	_ "github.com/coredns/coredns/plugin/pprof" | ||||||
| 	_ "github.com/coredns/coredns/plugin/proxy" | 	_ "github.com/coredns/coredns/plugin/proxy" | ||||||
|  | 	_ "github.com/coredns/coredns/plugin/reload" | ||||||
| 	_ "github.com/coredns/coredns/plugin/reverse" | 	_ "github.com/coredns/coredns/plugin/reverse" | ||||||
| 	_ "github.com/coredns/coredns/plugin/rewrite" | 	_ "github.com/coredns/coredns/plugin/rewrite" | ||||||
| 	_ "github.com/coredns/coredns/plugin/root" | 	_ "github.com/coredns/coredns/plugin/root" | ||||||
|   | |||||||
| @@ -20,7 +20,7 @@ | |||||||
| # log:log | # log:log | ||||||
|  |  | ||||||
| tls:tls | tls:tls | ||||||
| #reload:reload # enable by reverting #1511 | reload:reload | ||||||
| nsid:nsid | nsid:nsid | ||||||
| root:root | root:root | ||||||
| bind:bind | bind:bind | ||||||
|   | |||||||
| @@ -15,7 +15,7 @@ The reloads are graceful - you should not see any loss of service when the | |||||||
| reload happens. Even if the new Corefile has an error, CoreDNS will continue | reload happens. Even if the new Corefile has an error, CoreDNS will continue | ||||||
| to run the old config and an error message will be printed to the log. | to run the old config and an error message will be printed to the log. | ||||||
|  |  | ||||||
| In some environments (for example, Kubernetes), there may be many CoreDNS  | In some environments (for example, Kubernetes), there may be many CoreDNS | ||||||
| instances that started very near the same time and all share a common | instances that started very near the same time and all share a common | ||||||
| Corefile. To prevent these all from reloading at the same time, some | Corefile. To prevent these all from reloading at the same time, some | ||||||
| jitter is added to the reload check interval. This is jitter from the | jitter is added to the reload check interval. This is jitter from the | ||||||
| @@ -44,7 +44,7 @@ reload [INTERVAL] [JITTER] | |||||||
|  |  | ||||||
| Check with the default intervals: | Check with the default intervals: | ||||||
|  |  | ||||||
| ~~~ txt | ~~~ corefile | ||||||
| . { | . { | ||||||
|     reload |     reload | ||||||
|     erratic |     erratic | ||||||
| @@ -53,7 +53,7 @@ Check with the default intervals: | |||||||
|  |  | ||||||
| Check every 10 seconds (jitter is automatically set to 10 / 2 = 5 in this case): | Check every 10 seconds (jitter is automatically set to 10 / 2 = 5 in this case): | ||||||
|  |  | ||||||
| ~~~ txt | ~~~ corefile | ||||||
| . { | . { | ||||||
|     reload 10s |     reload 10s | ||||||
|     erratic |     erratic | ||||||
|   | |||||||
		Reference in New Issue
	
	Block a user