[WIP] MG-216: add "openshift/mustgather" toolset#159
[WIP] MG-216: add "openshift/mustgather" toolset#159swghosh wants to merge 1 commit intoopenshift:mainfrom
Conversation
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: swghosh The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
| // FindContainerDir locates the must-gather container directory | ||
| // (e.g., quay-io-okd-scos-content-sha256-...) | ||
| func FindContainerDir(basePath string) (string, error) { | ||
| entries, err := os.ReadDir(basePath) |
There was a problem hiding this comment.
there are a few considerations regarding where the must-gather can be stored:
- if the server is running locally in a dev setup, it can access the must-gather from the fs
- if it is running on the target cluster, we should probably make sure it can be read from a pv
- the last one is variable where the must-gather needs to be accessed remotely. This will involve further discussions on where the must-gather from customer cases are stored and how they can be accessed.
|
/cc @bentito Iirc you were also interested in the offline bits |
|
@swghosh: This pull request references MG-216 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
PR needs rebase. DetailsInstructions 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. |
Offline debugging analysis use cases require us to get data parsed from a must-gather archive rather than online cluster's kapiserver endpoint. Some tools are similar to the core toolset but there are more tools beyond resources_get especially journal logs, kubelet logs, etc.