You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
janetkuo opened this issue
Mar 17, 2017
· 4 comments
Labels
kind/bugCategorizes issue or PR as related to a bug.sig/appsCategorizes an issue or PR as relevant to SIG Apps.sig/cliCategorizes an issue or PR as relevant to SIG CLI.
kubectl rollout commands (such as undo or history) should take deployment overlapping annotation into consideration; for example, when listing replica sets. It won't interfere with the other overlapped deployment, but may cause user confusions.
As of 1.6, the overlapping annotation is no longer used. However, in 1.6 client code we still had to support talking to 1.5 servers, and in that context it was suggested that perhaps we should take the annotation into account.
In 1.7+, we no longer need to support talking to a pre-1.6 server, and the client code already uses the full ControllerRef logic rather than 1.5-compatible logic (#43942) so it will not be confused by overlap.
kind/bugCategorizes issue or PR as related to a bug.sig/appsCategorizes an issue or PR as relevant to SIG Apps.sig/cliCategorizes an issue or PR as relevant to SIG CLI.
Forked from #43239
kubectl rollout
commands (such asundo
orhistory
) should take deployment overlapping annotation into consideration; for example, when listing replica sets. It won't interfere with the other overlapped deployment, but may cause user confusions.@Kargakis @kubernetes/sig-apps-bugs
The text was updated successfully, but these errors were encountered: