worry, the operation succeeded except for the part where the new replication controller is renamed back to the old name. You can just do another rolling update using kubectl 1.4 or higher to change the name back: look for a replication controller that has the original name plus a random suffix.

Unfortunately, there is a much rarer second possible failure mode: the replication controller gets renamed to the old name, but there is a duplicated set of pods in the cluster. kubectl will not report...

  * You do not need to adjust this flag on Kubelet:  there was no authorization for the Kubelet APIs in 1.4.
* batch/v2alpha1.ScheduledJob has been renamed, use batch/v2alpha1.CronJob instead ([#36021](https://github.com/kubernetes/kubernetes/pull/36021), [@soltysh](https://github.com/soltysh))
* PetSet has been renamed to StatefulSet.
  If you have existing PetSets, **you must perform extra migration steps** both

     *
     * <i>Remember: <code>SmbFile</code>s are immutible and therefore
     * the path associated with this <code>SmbFile</code> object will not
     * change). To access the renamed file it is necessary to construct a
     * new {@code SmbFile}</i>.
     *
     * @param  dest  An <code>SmbFile</code> that represents the new pathname
     * @throws NullPointerException