RHIDP-12611: Document the RHDH must-gather tool for diagnostics data collection#2151
Conversation
PR Build ResultsBuild passed -- 35/35 titles | 72s Content Quality AssessmentCQA Report
SummaryChecks: 19 total, 19 pass, 0 fail 19 checks: 19 pass, 0 fail Run Updated 2026-06-03 13:46:04 UTC |
6bb563d to
aee87bf
Compare
aee87bf to
31d09c4
Compare
31d09c4 to
bd9e729
Compare
bd9e729 to
e8384e6
Compare
e8384e6 to
d5dc1b5
Compare
c9f7cb6 to
3099922
Compare
3099922 to
19afd22
Compare
19afd22 to
8928639
Compare
themr0c
left a comment
There was a problem hiding this comment.
The 2 procedures are still mixing oc and helm => the objective of having one procedure for each is missed.
|
btw, is there a note somewhere that the must-gather is currently Tech Preview? I remember seeing it previously on your PR, but can no longer find it. |
|
New changes are detected. LGTM label has been removed. |
|
Yes, the Technology Preview banner has now been included in the first section after the abstract in the "Diagnostic data collection overview" concept module. @rm3l |
rh-tokeefe
left a comment
There was a problem hiding this comment.
@jmagak overall this LGTM. I made a few comments for you to consider, but I defer to your judgement. It looks like two comments by Armel Soro are not resolved. I'm not sure if there needs to be an action, if an action was taken but the comment not resolved, etc.
There was a problem hiding this comment.
@jmagak I just realized that a previous section about running the must-gather image in air-gapped/disconnected environments seems to be missing from this PR.
I had made a few comments like this one, but now it seems to be completely missing:
I think disconnected environments is an important topic to cover here. Upstream docs: https://github.com/redhat-developer/rhdh-must-gather/blob/release-1.10/docs/disconnected-environments.md
rh-tokeefe
left a comment
There was a problem hiding this comment.
@jmagak overall LGTM. I made a suggestion for the short description based on the gem output. The other item is more a question for my own benefit.
|
|
/cherry-pick release-1.10 |
|
@jmagak: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@jmagak: new pull request created: #2314 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |



IMPORTANT: Do Not Merge - To be merged by Docs Team Only
Version(s): 1.10, main
Issue: RHIDP-12611
Preview:
7.1. Collect diagnostic data for support cases
1. Diagnostic data collection overview
2. Run must-gather on OpenShift to collect diagnostic data
3. Run must-gather on Kubernetes to collect diagnostic data
4. Collect diagnostic data from air-gapped clusters by mirroring must-gather to your internal registry
5. Diagnostic data types and collection scope
6. Collect heap dumps to diagnose memory issues
7. Configuration options for diagnostic collection
8. Diagnostic data output structure and organization
9. Additional resources