Bug 1737090

Summary:	Document behavior after updating cluster build configs
Product:	OpenShift Container Platform	Reporter:	Adam Kaplan <adam.kaplan>
Component:	Documentation	Assignee:	Vikram Goyal <vigoyal>
Status:	CLOSED EOL	QA Contact:	Xiaoli Tian <xtian>
Severity:	medium	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	unspecified
Version:	4.1.0	CC:	aos-bugs, jokerman
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-18 06:56:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Adam Kaplan 2019-08-02 15:01:09 UTC

Document URL:
https://docs.openshift.com/container-platform/4.1/builds/build-configuration.html

Section Number and Name: 

Describe the issue:
Updating the cluster build configuration takes time to be applied to the cluster. As a result, customers may expect certain behavior to occur right after the cluster build configuration has been applied.


Suggestions for improvement: 
Add a section to explain how customers can verify the cluster has been updated with the new configuration:

1. Watch the openshift-controller-manager ClusterOperator - this will report `Progressing=True` while the configuration is being applied.

Via oc:
```
$ oc get clusteroperator openshift-controller-manager -w
```
or in the web console.

2. Watch the controller-manager DameonSet - this will report `Updated=3` when the configuration has been applied to all openshift controller managers.

Via oc:
```
$ oc get ds controller-manager -n openshift-controller-manager -w
```
or in the web console.