Hide Forgot
Figuring out whether a deployment, dc, statefulset, or ds is "ok" or "not ok" or "being updated" is too hard from kubectl/oc get. I think we should add two columns immediately to the right of name, like pods, as "Ready" and "Status" that should rollup condition, readyReplicas, replicas, and unavaialbelReplicas info from status. We can then potentially drop some of the other count columns. This would massively improve the ability of an admin to do an "at a glance" of workloads. Right now it sucks.
Not a 3.11 blocker, moving to 4.0 bucket
Upstream issue tracking this: https://github.com/kubernetes/kubernetes/issues/68623
Upstream PR https://github.com/kubernetes/kubernetes/pull/70466
We got this with 1.13 rebase, moving to qa.
confirmed with latest OCP, the issue has fixed: oc version: Client Version: version.Info{Major:"4", Minor:"1+", GitVersion:"v4.1.0", GitCommit:"74c534b60", GitTreeState:"", BuildDate:"2019-04-21T21:13:18Z", GoVersion:"", Compiler:"", Platform:""} kubectl version [root@dhcp-140-138 ~]# kubectl version Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-25T15:53:57Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"} [root@dhcp-140-138 ~]# kubectl get sts NAME READY AGE hello-statefulset 2/2 72s [root@dhcp-140-138 ~]# kubectl get deploy NAME READY UP-TO-DATE AVAILABLE AGE busybox 0/1 1 0 101m [root@dhcp-140-138 ~]# oc get sts NAME READY AGE hello-statefulset 2/2 9m16s [root@dhcp-140-138 ~]# oc get deploy NAME READY UP-TO-DATE AVAILABLE AGE busybox 0/1 1 0 109m
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758