From 5da5c49950c957b8d67312599bcaccaf60416aa6 Mon Sep 17 00:00:00 2001 From: Deirdre Storck Date: Thu, 28 Jun 2018 11:06:21 -0700 Subject: [PATCH] removed caveat for 1.5 rolling update (#9270) --- .../en/docs/tasks/manage-daemon/update-daemon-set.md | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/content/en/docs/tasks/manage-daemon/update-daemon-set.md b/content/en/docs/tasks/manage-daemon/update-daemon-set.md index c2f6f506bd..9650d05ed0 100644 --- a/content/en/docs/tasks/manage-daemon/update-daemon-set.md +++ b/content/en/docs/tasks/manage-daemon/update-daemon-set.md @@ -34,17 +34,6 @@ DaemonSet has two update strategy types: DaemonSet template, old DaemonSet pods will be killed, and new DaemonSet pods will be created automatically, in a controlled fashion. -## Caveat: Updating DaemonSet created from Kubernetes version 1.5 or before - -If you try a rolling update on a DaemonSet that was created from Kubernetes -version 1.5 or before, a rollout will be triggered when you *first* change the -DaemonSet update strategy to `RollingUpdate`, no matter if DaemonSet template is -modified or not. If the DaemonSet template is not changed, all existing DaemonSet -pods will be restarted (deleted and created). - -Therefore, make sure you want to trigger a rollout before you first switch the -strategy to `RollingUpdate`. - ## Performing a Rolling Update To enable the rolling update feature of a DaemonSet, you must set its