Paco Xu
``` [root@daocloud ~]# kubectl rollout history deployment/mysql deployment.apps/mysql REVISION CHANGE-CAUSE 2 3 custom message revision 3 5 custom message revision 5 6 custom message revision 6 [root@daocloud ~]# kubectl rollout...
I prefer that it is something expected. `kubectl.kubernetes.io/last-applied-configuration` should be added when the user execs `kubectl apply`. `kubectl rollout` may not change the label. /cc @eddiezane
[kubelet-gce-e2e-lock-contention](https://k8s-testgrid.appspot.com/sig-node-kubelet#kubelet-gce-e2e-lock-contention) is green now. [node-kubelet-containerd-performance-test](https://k8s-testgrid.appspot.com/sig-node-containerd#node-kubelet-containerd-performance-test) failed but not for cni not ready Not sure if it is related with https://github.com/kubernetes/test-infra/issues/25430
/remove-lifecycle stale
+1 Thanks for your ci failure fixes and cleanups. Hope you can make more contributions to Kuberentes community.
> This is only about how to remove member by a script. But how to provide the list of inactive members? The docs only say that we can check inactive...
+1 Thanks for your contributions.
/priority important-soon /triage accepted