mirror of
				https://github.com/coredns/coredns.git
				synced 2025-10-31 10:13:14 -04:00 
			
		
		
		
	plugins: set upstream unconditionally (#2956)
`upstream` is not needed as a setting; just set if unconditionally and remove all documentation and tests for it. At some point we want remove the hanlding for `upstream` as well and error out on seeing it. Signed-off-by: Miek Gieben <miek@miek.nl>
This commit is contained in:
		| @@ -87,5 +87,5 @@ There are many ways to work around this issue, some are listed here: | ||||
| although this can be different depending on your distribution. | ||||
| * Disable the local DNS cache on host nodes, and restore `/etc/resolv.conf` to the original. | ||||
| * A quick and dirty fix is to edit your Corefile, replacing `forward . /etc/resolv.conf` with | ||||
| the ip address of your upstream DNS, for example `forward . 8.8.8.8`.  But this only fixes the issue for CoreDNS, | ||||
| the IP address of your upstream DNS, for example `forward . 8.8.8.8`.  But this only fixes the issue for CoreDNS, | ||||
| kubelet will continue to forward the invalid `resolv.conf` to all `default` dnsPolicy Pods, leaving them unable to resolve DNS. | ||||
|   | ||||
		Reference in New Issue
	
	Block a user