Please add desclaimer to docs for preventing master update failure & hang

[ka7harada]

Which topic are you reporting about?

Request 1
Please add "hint" section under the explanation section for master update section.
And a hint for heads up to let customer know if many unexpected namespaces are left,it will give negative impact to api server microservice in master node
automatic master update would trigger the situation of worker node unstableness.
See　Sev1 CS4196877

And also customer's required action is also described.
Possible required customer action is same as required action for kubectl get --raw /metrics
https://cloud.ibm.com/docs/openshift?topic=openshift-ts-etcd-capacity

Request 2
Please add the link to hint from template of Announcing a master patch update for Red Hat OpenShift on IBM Cloud clusters like source id 1732661015411

Request 3
To other page, it would be nice if you write about rough guideline to the reasonable # of objects for cluster ex object for amount of 3 digit for 1 app is expected, but that for 4 digit may give risk to your cluster

What do you think needs to be updated?

Sample
１
Red Hat OpenShift on IBM Cloud version information
＞Available Red Hat OpenShift versions
＞Notes
https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versions&locale=en#openshift_versions_available

<=== add below to hint section ====>

Hint:Please house keep your objects and clear objects that remained unexpectedly. it may give risk of Master Update failure.

２
Update types >Patch updates (x.x.4_1510) > Master patches:
Link https://cloud.ibm.com/docs/containers?topic=containers-cs_versions&locale=en

Master patches: Master patches are applied automatically over the course of several days, so a master patch version might show up as available before it is applied to your master. The update automation also skips clusters that are in an unhealthy state or have operations currently in progress. Occasionally, IBM might disable automatic updates for a specific master fix pack, as noted in the change log, such as a patch that is only needed if a master is updated from one minor version to another. In any of these cases, you can choose to safely use the ibmcloud ks cluster master update command yourself without waiting for the update automation to apply.

<=== add from here ====>

Hint:Please house keep your objects and clear objects that remained unexpectedly. it may give risk of Master Update failure.

Anything else?

No response

[rtheis]

Sorry, this is not ready for the docs folks to action.