Description of problem: I'm using the operator, now I want to know when the applicaiton is ready. For this it would be good if the operator provides a ready condition (which then nicely ties into kubectl wait) What you expected to happen: $ kubcetl wait --for condition=Ready kubevirt mykubevirt Version-Release number of selected component (if applicable): 1.4 How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Upstream PRs are merged: Created condition: https://github.com/kubevirt/kubevirt/pull/1959 Ready Condition: https://github.com/kubevirt/kubevirt/pull/1966
Thanks for the heads up Federico
./kubectl version Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-16T16:23:09Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.4+838b4fa", GitCommit:"838b4fa", GitTreeState:"clean", BuildDate:"2019-05-19T23:51:04Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"} (env) [root@dell-r640-007 ~]# ./kubectl -n kubevirt-hyperconverged wait pod cdi-apiserver-85f677f69b-vj82z --for condition=Ready pod/cdi-apiserver-85f677f69b-vj82z condition met (env) [root@dell-r640-007 ~]# ./kubectl -n kubevirt-hyperconverged wait kv kubevirt-hyperconverged-cluster --for condition=Ready kubevirt.kubevirt.io/kubevirt-hyperconverged-cluster condition met (env) [root@dell-r640-007 ~]# ./kubectl -n kubevirt-hyperconverged wait pods --all --for condition=Ready pod/cdi-apiserver-85f677f69b-vj82z condition met pod/cdi-deployment-745bc658b7-bllw7 condition met pod/cdi-operator-65bc954fc5-lsltq condition met pod/cdi-uploadproxy-5874c465fd-4xwwr condition met pod/cluster-network-addons-operator-6f978988f7-l6jxl condition met pod/hco-operator-66595548c7-zgdhw condition met pod/kubevirt-node-labeller-5wd8v condition met pod/kubevirt-node-labeller-h9zmx condition met pod/kubevirt-ssp-operator-67c78554f6-5qsl9 condition met pod/kubevirt-web-ui-operator-59489c7d6d-wr685 condition met pod/node-maintenance-operator-6d5946f965-cdtmx condition met pod/virt-api-7f67877b6b-2n9hk condition met pod/virt-api-7f67877b6b-zwzbn condition met pod/virt-controller-6fdb5b66d4-j7jfb condition met pod/virt-controller-6fdb5b66d4-xpj85 condition met pod/virt-handler-ftc8h condition met pod/virt-handler-zsmvk condition met pod/virt-operator-668b7d58fc-d82jp condition met pod/virt-operator-668b7d58fc-qvndv condition met pod/virt-template-validator-57d8588dd-xfr5v condition met
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/RHEA-2019:1850