-
Bug
-
Resolution: Done
-
Undefined
-
4.13, 4.12, 4.14, 4.15, 4.16, 4.17, 4.18, 4.19
-
None
-
Quality / Stability / Reliability
-
False
-
-
5
-
None
-
None
-
None
-
None
-
None
-
OSDOCS Sprint 276, OSDOCS Sprint 277
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
In https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/support/remote-health-monitoring-with-connected-clusters#insights-operator-new-pull-secret_opting-out-remote-health-reporting for the procedure to opt-out from remote health reporting we provided guided steps how to: 1. download pull-secret 2. edit the file 3. what to remove from the file 4. save the file and... just after such a nicely detailed guidance, we simply say "You can now update your cluster to use this modified pull secret." The last statement can mean a lot of different things. Why we don't provide simple example of command to run to get the whole procedure done without a need of jumping back and forth through 100s of documentation pages? I'd like to see reference to https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/support/remote-health-monitoring-with-connected-clusters#images-update-global-pull-secret_opting-out-remote-health-reporting or ideally command example from the above: ``` oc set data secret/pull-secret -n openshift-config --from-file=.dockerconfigjson=<pull_secret_location> ``` to close the loop. Otherwise we're leaving documentation user wondering: "Now what, do I need to upgrade the WHOLE cluster?" ;-) This has impact on overall customer experience with Red Hat Products, and documentation is very important part of it.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- links to
(5 links to)