<p>If there an use case where kubectl apply should not be use to get a roll-update? </p>

<p>Despite the command original intent if we gave to kubectl apply a source file describing the resources of the cluster been updated over time, there any use case on which should not be use?</p>

<p>The update strategy is specified in <code>.spec.strategy</code> in case of a Deployment and  <code>.spec.updateStrategy.type</code> for DaemonSets and StatefulSets</p>

<p>For Deployments <code>.spec.strategy.type</code> can be “Recreate” or “RollingUpdate”. “RollingUpdate” is the default value.</p>

<p>For DaemonSets and StatefulSets, <code>.spec.updateStrategy.type</code> can be "OnDelete" or "RollingUpdate". "OnDelete" is the default value.</p>

<p><code>kubectl apply</code> will respect these strategies, so I see no reason why not using it.</p>

<p><code>kubectl rolling-update</code> is used only for ReplicationControllers which were replaced by Deployments</p>
