Bug 1737090 - Document behavior after updating cluster build configs
Summary: Document behavior after updating cluster build configs
Keywords:
Status: CLOSED EOL
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Xiaoli Tian
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-02 15:01 UTC by Adam Kaplan
Modified: 2020-05-18 06:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-18 06:56:47 UTC
Target Upstream Version:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.