Skip to content

MG-334: add user docs - #377

Draft
neha037 wants to merge 1 commit into
openshift:masterfrom
neha037:MG-334
Draft

MG-334: add user docs#377
neha037 wants to merge 1 commit into
openshift:masterfrom
neha037:MG-334

Conversation

@neha037

@neha037 neha037 commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Documentation
    • Added guidance for updating Support Log Gather documentation for general availability.
    • Clarified permissions, service account requirements, subscription channels, installation steps, and validation behavior.
    • Updated examples and parameter descriptions to reflect current configuration rules.
    • Documented restrictions for auditing, timeouts, storage, proxies, trusted certificates, credentials, and immutable settings.
    • Added troubleshooting guidance, invalid examples, deferred topics, and a documentation checklist.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 28, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 28, 2026

Copy link
Copy Markdown

@neha037: This pull request references MG-334 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 "5.0.0" version, but no target version was set.

Details

In 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.

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 28, 2026
@openshift-ci

openshift-ci Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@coderabbitai

coderabbitai Bot commented Jul 28, 2026

Copy link
Copy Markdown

Walkthrough

This documentation change request defines GA updates for Support Log Gather modules, including permission guidance, installation examples, CLI configuration procedures, corrected MustGather examples, parameter reference updates, validation notes, and writer checklists.

Changes

Support Log Gather documentation

Layer / File(s) Summary
GA overview and installation guidance
docs/MG-334-support-log-gather-docs-update.md
Removes Technology Preview references, updates service-account permission wording, and changes CLI subscription examples to use <GA_CHANNEL>.
CLI configuration and validation procedure
docs/MG-334-support-log-gather-docs-update.md
Revises prerequisites, MustGather examples, restriction callouts, proxy and storage notes, and validation guidance.
Examples, parameter reference, and writer validation
docs/MG-334-support-log-gather-docs-update.md
Corrects service-account and parameter examples, documents secret and storage details, and adds invalid-pattern, deferred-topic, and writer-checklist appendices.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title matches the main change: adding user documentation for MG-334.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed Only a docs markdown file changed; no Ginkgo test files or titles were added or edited, so the naming rule is unaffected.
Test Structure And Quality ✅ Passed Only a docs file changed; no Ginkgo test code was added or modified.
Microshift Test Compatibility ✅ Passed PR only adds a markdown docs change request; no _test.go or Ginkgo test code was changed, so MicroShift compatibility is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed Only a markdown docs change is present; no Ginkgo test files or SNO-unsafe test additions were introduced.
Topology-Aware Scheduling Compatibility ✅ Passed Only a docs markdown file changed; no manifests, controllers, or operator code were modified, so no scheduling assumptions were introduced.
Ote Binary Stdout Contract ✅ Passed Docs-only PR; no process-level code or stdout writes were changed, so the OTE binary stdout contract isn't affected.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed Docs-only change: the diff adds no test files or Ginkgo constructs, so IPv4/disconnected-network test compatibility is not applicable.
No-Weak-Crypto ✅ Passed Docs-only PR; changed file contains no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB or custom/constant-time crypto patterns.
Container-Privileges ✅ Passed PR only adds a docs file; diff contains no container/K8s manifest changes and no privileged/hostNetwork/hostIPC/SYS_ADMIN/allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs ✅ Passed Docs-only PR; no log statements or secret/token/API-key literals were added.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@openshift-ci

openshift-ci Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: neha037
Once this PR has been reviewed and has the lgtm label, please assign devppratik for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
docs/MG-334-support-log-gather-docs-update.md (1)

180-190: 🎯 Functional Correctness | 🔵 Trivial | ⚡ Quick win

Link the bundled RBAC manifests. The controller only checks that the service account exists; point users to the must-gather-admin ClusterRole/ClusterRoleBinding so the prerequisite is actionable.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/MG-334-support-log-gather-docs-update.md` around lines 180 - 190, Update
the service-account prerequisite near the MustGather CR requirements to link to
the bundled must-gather-admin ClusterRole and ClusterRoleBinding manifests,
instructing users to apply or configure them for the service account. Keep the
existing namespace and permissions guidance intact.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/MG-334-support-log-gather-docs-update.md`:
- Around line 304-305: Update the oc verification commands in this
documentation, including the must-gather lookup and the referenced command
ranges, to explicitly target the must-gather-operator namespace. Preserve the
existing resource names and output formats while ensuring every check queries
the namespace where the examples create resources.
- Around line 193-195: Remove the invalid proxyConfig field from the example
MustGather YAML and all later duplicated examples in this document. Keep proxy
configuration represented only through the operator environment variables
HTTP_PROXY, HTTPS_PROXY, and NO_PROXY.

---

Nitpick comments:
In `@docs/MG-334-support-log-gather-docs-update.md`:
- Around line 180-190: Update the service-account prerequisite near the
MustGather CR requirements to link to the bundled must-gather-admin ClusterRole
and ClusterRoleBinding manifests, instructing users to apply or configure them
for the service account. Keep the existing namespace and permissions guidance
intact.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: be5d1b8e-f824-425e-9fe2-67a86bd8bf9e

📥 Commits

Reviewing files that changed from the base of the PR and between 501f600 and dc5e1e0.

📒 Files selected for processing (1)
  • docs/MG-334-support-log-gather-docs-update.md

Comment on lines +193 to +195
### Change: REPLACE — Example MustGather YAML (remove invalid `proxyConfig`)

**Current problem:** The example includes `proxyConfig`, which is **not** a field on `MustGather` / `MustGatherSpec`. Proxy settings come from the Operator pod environment (cluster proxy).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== Relevant files ==\n'
git ls-files | rg '(^|/)(docs/MG-334-support-log-gather-docs-update\.md|.*mustgather.*|.*MustGather.*|.*proxy.*|.*crd.*\.ya?ml)$' || true

printf '\n== Search for proxyConfig and MustGather ==\n'
rg -n --hidden -S 'proxyConfig|MustGatherSpec|kind: MustGather|mustgather' . || true

Repository: openshift/must-gather-operator

Length of output: 50386


🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== File size and outline for the docs file ==\n'
wc -l docs/MG-334-support-log-gather-docs-update.md
ast-grep outline docs/MG-334-support-log-gather-docs-update.md --view expanded || true

printf '\n== Show surrounding lines around the cited section ==\n'
sed -n '180,205p' docs/MG-334-support-log-gather-docs-update.md

Repository: openshift/must-gather-operator

Length of output: 1890


🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== Focused MustGather API files ==\n'
fd -a '.*' . | rg 'MustGather|mustgather|proxy' || true

printf '\n== Focused source search in likely API directories ==\n'
for d in api config pkg internal controllers docs; do
  [ -d "$d" ] || continue
  rg -n --hidden -S 'proxyConfig|type MustGather|MustGatherSpec|kind: MustGather' "$d" || true
done

Repository: openshift/must-gather-operator

Length of output: 10667


🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== MustGatherSpec definition ==\n'
sed -n '1,120p' api/v1alpha1/mustgather_types.go

printf '\n== Proxy-related code paths ==\n'
rg -n --hidden -S 'HTTP_PROXY|HTTPS_PROXY|NO_PROXY|proxy|Proxy' controllers/mustgather api/v1alpha1 README.md docs/MG-334-support-log-gather-docs-update.md | sed -n '1,220p'

Repository: openshift/must-gather-operator

Length of output: 26513


Remove proxyConfig from the examples. MustGatherSpec has no such field, and the operator already forwards HTTP_PROXY/HTTPS_PROXY/NO_PROXY from its environment to the upload container. Same issue appears in the later copies.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/MG-334-support-log-gather-docs-update.md` around lines 193 - 195, Remove
the invalid proxyConfig field from the example MustGather YAML and all later
duplicated examples in this document. Keep proxy configuration represented only
through the operator environment variables HTTP_PROXY, HTTPS_PROXY, and
NO_PROXY.

Source: MCP tools

Comment on lines +304 to +305
$ oc get mustgather example-mg -o yaml
----

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Scope verification commands to the CR namespace.

The examples create resources in must-gather-operator, but these commands use the current namespace and can report false “missing” results.

Proposed fix
-$ oc get mustgather
+$ oc get mustgather -n must-gather-operator

-$ oc get pods
+$ oc get pods -n must-gather-operator

-$ oc logs -f pod/<mustgather-pod-name> -c upload
+$ oc logs -n must-gather-operator -f pod/<mustgather-pod-name> -c upload

Also applies to: 370-377, 384-384

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/MG-334-support-log-gather-docs-update.md` around lines 304 - 305, Update
the oc verification commands in this documentation, including the must-gather
lookup and the referenced command ranges, to explicitly target the
must-gather-operator namespace. Preserve the existing resource names and output
formats while ensuring every check queries the namespace where the examples
create resources.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants