diff options
author | Steve Kuznetsov <skuznets@redhat.com> | 2017-06-09 07:02:35 -0700 |
---|---|---|
committer | Steve Kuznetsov <skuznets@redhat.com> | 2017-06-09 09:21:54 -0700 |
commit | 9ba4195cb4c70705c4cec2543617738b8e114148 (patch) | |
tree | 2c6db92ecb69acbbd3440819d8f2abe3bace8d78 /roles/openshift_hosted/meta | |
parent | 5c678402a08dd251b9d4496316212fef5b917560 (diff) | |
download | openshift-9ba4195cb4c70705c4cec2543617738b8e114148.tar.gz openshift-9ba4195cb4c70705c4cec2543617738b8e114148.tar.bz2 openshift-9ba4195cb4c70705c4cec2543617738b8e114148.tar.xz openshift-9ba4195cb4c70705c4cec2543617738b8e114148.zip |
Verify the rollout status of the hosted router and registry
When deploying the hosted router and registry components, we need to
ensure that they correctly roll out. The previous checks were weak in
that they either simply waited for a set amount of time and/or did one
replica check. They would fail if the router or registry took longer to
deploy or if there were un-ready or failing replicas. The `oc rollout`
command group contains the `status` endpoint for internalizing all of
the logic for determining when a rollout has succeeded or failed, so
simply using this client call will ensure that the router and registry
correctly deploy.
Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
Diffstat (limited to 'roles/openshift_hosted/meta')
0 files changed, 0 insertions, 0 deletions