From f0711ca74255382e8fd0acb93dfb56c00ef79ac4 Mon Sep 17 00:00:00 2001
From: Niko Pen <42466421+nikopen@users.noreply.github.com>
Date: Sat, 24 Nov 2018 17:07:28 +0100
Subject: [PATCH] bigger or equal kubeadm version (#11226)

---
 .../docs/tasks/administer-cluster/dns-debugging-resolution.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/tasks/administer-cluster/dns-debugging-resolution.md b/content/en/docs/tasks/administer-cluster/dns-debugging-resolution.md
index 1a9b7bf7e2..dd569aa774 100644
--- a/content/en/docs/tasks/administer-cluster/dns-debugging-resolution.md
+++ b/content/en/docs/tasks/administer-cluster/dns-debugging-resolution.md
@@ -252,7 +252,7 @@ Some Linux distributions (e.g. Ubuntu), use a local DNS resolver by default (sys
 Systemd-resolved moves and replaces `/etc/resolv.conf` with a stub file that can cause a fatal forwarding
 loop when resolving names in upstream servers. This can be fixed manually by using kubelet's `--resolv-conf` flag
 to point to the correct `resolv.conf` (With `systemd-resolved`, this is `/run/systemd/resolve/resolv.conf`).
-kubeadm 1.11 automatically detects `systemd-resolved`, and adjusts the kubelet flags accordingly.
+kubeadm (>= 1.11) automatically detects `systemd-resolved`, and adjusts the kubelet flags accordingly.
 
 Kubernetes installs do not configure the nodes' `resolv.conf` files to use the
 cluster DNS by default, because that process is inherently distribution-specific.