Skip to content

Conversation

@paulohtb6
Copy link
Collaborator

@paulohtb6 paulohtb6 commented Jul 28, 2025

Description

Resolves https://redpandadata.atlassian.net/browse/
Review deadline: July 29th

Page previews

Checks

  • New feature
  • Content gap
  • Support Follow-up
  • Small fix (typos, links, copyedits, etc)

@paulohtb6 paulohtb6 requested a review from a team as a code owner July 28, 2025 19:46
@netlify
Copy link

netlify bot commented Jul 28, 2025

Deploy Preview for redpanda-docs-preview ready!

Name Link
🔨 Latest commit 5533f3d
🔍 Latest deploy log https://app.netlify.com/projects/redpanda-docs-preview/deploys/68893a643861310008c1c9fb
😎 Deploy Preview https://deploy-preview-1241--redpanda-docs-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 28, 2025

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

📝 Walkthrough

Walkthrough

This set of changes updates documentation for several rpk CLI commands. The default value for the --cloud-timeout-ms flag in the self-test start command has been increased from 5000 ms to 10000 ms. The formatting of the --namespace flag description in the debug bundle command was adjusted for clarity, without semantic changes. The debug remote-bundle download command now includes a new --upload-url flag for specifying an upload destination. The default namespace value was removed from the remote-bundle start command documentation. The decommission-status command output format was revised to consolidate partition identification and clarify failure reporting.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant rpk CLI
    participant Cloud Storage
    participant Upload Destination

    User->>rpk CLI: rpk debug remote-bundle download --upload-url=<url>
    rpk CLI->>Cloud Storage: Download debug bundle
    Cloud Storage-->>rpk CLI: Bundle data
    rpk CLI->>User: Save bundle locally
    alt --upload-url specified
        rpk CLI->>Upload Destination: Upload bundle to <url>
    end
    rpk CLI->>User: Notify completion
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Suggested reviewers

  • micheleRP
  • Feediver1
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch rpk-v25.1.9

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (5)
modules/reference/pages/rpk/rpk-debug/rpk-debug-remote-bundle-start.adoc (1)

44-45: Clarify wording and verify removed default

  1. “The namespace to use to collect the resources from” is a bit clunky. Consider “Namespace from which to collect resources.”
  2. The previous docs showed a default of redpanda. If the CLI no longer sets a default, this update is correct; otherwise the documentation now diverges from behaviour.

Please run rpk debug remote-bundle start --help | grep -- '--namespace' and confirm that the tool indeed has no default value.

modules/reference/pages/rpk/rpk-debug/rpk-debug-remote-bundle-download.adoc (1)

32-33: Flag added – add cross-reference to upload guidance

--upload-url is documented here, but users may also look at the earlier start command for upload instructions. Consider adding a short “See also rpk debug bundle --upload-url for details” note to help discoverability.

modules/reference/pages/rpk/rpk-redpanda/rpk-redpanda-admin-brokers-decommission-status.adoc (3)

8-10: Clarify the new unified PARTITION column in the introductory sentence

Now that the output collapses namespace, topic, and partition number into a single PARTITION column, consider mentioning this explicitly so readers immediately understand the new format.

Example diff:

-When a node is in the process of being decommissioned, this command reports the decommissioning progress as follows, where PARTITION-SIZE is in bytes.
+When a node is being decommissioned, the command shows progress as follows.  
+The `PARTITION` column combines namespace, topic, and partition number (for example `kafka/test/0`).  
+`PARTITION-SIZE` is in bytes.

38-42: Tighten wording & make decommission failure behaviour explicit

The current sentence is slightly long and uses “for some reason”. Rephrase for conciseness and to state that the command exits with failure.

-If a partition cannot be moved for some reason, the command reports the problematic partition in the 'REALLOCATION FAILURE DETAILS' or 'ALLOCATION FAILURES' section and decommission fails. Typical scenarios for failure include:
+If a partition cannot be moved, the command lists it under **REALLOCATION FAILURE DETAILS** (or **ALLOCATION FAILURES**) and the decommission operation fails. Typical failure scenarios include:

45-54: Sample failure block reflects updated heading

The new REALLOCATION FAILURE DETAILS section correctly mirrors the wording used above. Consider shortening the underline delimiter so its length matches the heading (purely cosmetic).

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 78effdd and 9b554b6.

📒 Files selected for processing (5)
  • modules/reference/pages/rpk/rpk-cluster/rpk-cluster-self-test-start.adoc (1 hunks)
  • modules/reference/pages/rpk/rpk-debug/rpk-debug-bundle.adoc (1 hunks)
  • modules/reference/pages/rpk/rpk-debug/rpk-debug-remote-bundle-download.adoc (1 hunks)
  • modules/reference/pages/rpk/rpk-debug/rpk-debug-remote-bundle-start.adoc (1 hunks)
  • modules/reference/pages/rpk/rpk-redpanda/rpk-redpanda-admin-brokers-decommission-status.adoc (2 hunks)
🧰 Additional context used
🧠 Learnings (4)
📓 Common learnings
Learnt from: Feediver1
PR: redpanda-data/docs#1153
File: antora.yml:3-5
Timestamp: 2025-07-14T19:28:43.296Z
Learning: In Redpanda docs, during beta releases, the version metadata may intentionally show inconsistencies where the header displays the beta version (e.g., 25.2 Beta) while internal attributes like full-version, latest-redpanda-tag, operator-beta-tag still reference the stable version (e.g., 25.1). This is resolved during the GA merge process when all version references are synchronized.
modules/reference/pages/rpk/rpk-debug/rpk-debug-remote-bundle-start.adoc (1)

Learnt from: kbatuigas
PR: #1113
File: modules/manage/partials/iceberg/use-iceberg-catalogs.adoc:100-107
Timestamp: 2025-05-07T01:06:00.937Z
Learning: In AsciiDoc documentation for Redpanda, the syntax + and -- around content blocks within a [tabs] section are valid AsciiDoc formatting elements for tabbed content. The + after a tab name (like rpk::) indicates that the following block belongs to that tab, and the -- markers enclose the content for that tab. These are not diff artifacts and should not be removed.

modules/reference/pages/rpk/rpk-debug/rpk-debug-bundle.adoc (1)

Learnt from: kbatuigas
PR: #1113
File: modules/manage/partials/iceberg/use-iceberg-catalogs.adoc:100-107
Timestamp: 2025-05-07T01:06:00.937Z
Learning: In AsciiDoc documentation for Redpanda, the syntax + and -- around content blocks within a [tabs] section are valid AsciiDoc formatting elements for tabbed content. The + after a tab name (like rpk::) indicates that the following block belongs to that tab, and the -- markers enclose the content for that tab. These are not diff artifacts and should not be removed.

modules/reference/pages/rpk/rpk-redpanda/rpk-redpanda-admin-brokers-decommission-status.adoc (2)

Learnt from: kbatuigas
PR: #1113
File: modules/manage/partials/iceberg/use-iceberg-catalogs.adoc:100-107
Timestamp: 2025-05-07T01:06:00.937Z
Learning: In AsciiDoc documentation for Redpanda, the syntax + and -- around content blocks within a [tabs] section are valid AsciiDoc formatting elements for tabbed content. The + after a tab name (like rpk::) indicates that the following block belongs to that tab, and the -- markers enclose the content for that tab. These are not diff artifacts and should not be removed.

Learnt from: Feediver1
PR: #1153
File: modules/reference/pages/properties/topic-properties.adoc:45-50
Timestamp: 2025-07-16T19:33:20.420Z
Learning: In the Redpanda documentation, topic property cross-references like <<max.compaction.lag.ms>> and <<min.compaction.lag.ms>> require corresponding property definition sections with anchors like [[maxcompactionlagms]] and [[mincompactionlagms]] to prevent broken links.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: Redirect rules - redpanda-docs-preview
  • GitHub Check: Header rules - redpanda-docs-preview
  • GitHub Check: Pages changed - redpanda-docs-preview
🔇 Additional comments (4)
modules/reference/pages/rpk/rpk-debug/rpk-debug-bundle.adoc (1)

121-123: LGTM – AsciiDoc multi-line cell is correct

The split description using + follows the Redpanda AsciiDoc tabular style. No further action needed.

modules/reference/pages/rpk/rpk-redpanda/rpk-redpanda-admin-brokers-decommission-status.adoc (2)

16-21: Column consolidation looks good

The switch to a single PARTITION column makes the sample output easier to scan and matches current rpk behaviour. No issues spotted.


31-35: Detailed view sample output aligns with CLI changes

The detailed view reflects the same column consolidation and adds the extra byte-tracking columns. Output order and spacing are accurate.

modules/reference/pages/rpk/rpk-cluster/rpk-cluster-self-test-start.adoc (1)

46-46: Confirm --cloud-timeout-ms flag implementation and default

I wasn’t able to locate any definition of --cloud-timeout-ms in the Go sources despite searching for common naming patterns. Please verify that in rpk v25.1.9:

  • The Cobra command (e.g. in cmd/rpk/cluster/self_test_start.go) registers a --cloud-timeout-ms flag.
  • Its default value is set to 10000 (10 s).

You can also run rpk cluster self-test start --help to confirm the displayed default matches the docs.

@paulohtb6 paulohtb6 mentioned this pull request Jul 28, 2025
4 tasks
@paulohtb6 paulohtb6 requested review from kbatuigas and r-vasquez July 28, 2025 20:07

|-n, --namespace |string |The Kubernetes namespace in which the Redpanda
cluster is running. Default: `redpanda` +
cluster is running. +
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@r-vasquez we captured on help text that this default value has been removed. Is this correct?

Copy link
Contributor

Choose a reason for hiding this comment

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

That's correct 👍

Copy link
Contributor

@kbatuigas kbatuigas left a comment

Choose a reason for hiding this comment

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

No blockers but made a couple of suggestions

Co-authored-by: Kat Batuigas <36839689+kbatuigas@users.noreply.github.com>
@paulohtb6 paulohtb6 merged commit b14bc58 into main Jul 29, 2025
6 of 7 checks passed
@paulohtb6 paulohtb6 deleted the rpk-v25.1.9 branch July 29, 2025 21:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants