As an example, the cluster logging operator frequently updates the status of the ClusterLogging CRs. Every time this happens, the web console reports that the item has changed and suggests a reload.

If you are trying to make an edit to a CR where this is the case, the experience is maddening. You have to make your change fast enough that it happens before the CR updates under the covers.

kubectl/oc's edit behavior doesn't have this problem, as some reconciliation of the changes are done on the back end. However, the web interface will NOT let you save your changes because the displayed YAML no longer matches.