summaryrefslogtreecommitdiffstats
path: root/setup.cfg
diff options
context:
space:
mode:
authorSteve Kuznetsov <skuznets@redhat.com>2017-05-22 09:42:19 -0700
committerSteve Kuznetsov <skuznets@redhat.com>2017-05-22 10:07:59 -0700
commit108a42cbbdbfc8094d1d8bf8d0d8826adfdf760d (patch)
tree1d7a646d9237aaafeb35c6e1356e996fd3e0417c /setup.cfg
parent7426996929fe298f4da0b238e38d91fb929b5112 (diff)
downloadopenshift-108a42cbbdbfc8094d1d8bf8d0d8826adfdf760d.tar.gz
openshift-108a42cbbdbfc8094d1d8bf8d0d8826adfdf760d.tar.bz2
openshift-108a42cbbdbfc8094d1d8bf8d0d8826adfdf760d.tar.xz
openshift-108a42cbbdbfc8094d1d8bf8d0d8826adfdf760d.zip
Create logging deployments with non-zero replica counts
When we currently create the set of logging `DeploymentConfig`s, we create them with zero desired replicas. This causes the deployment to immediately succeed as there is no work to be done. This inhibits our ability to use nice CLI UX features like `oc rollout status` to monitor the logging stack deployments. Instead, we should can create the configs with the correct number of replicas in the first place and stop using `oc scale` to bring them up after the fact. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
Diffstat (limited to 'setup.cfg')
0 files changed, 0 insertions, 0 deletions