Skip to content

Conversation

@micheleRP
Copy link
Contributor

@micheleRP micheleRP commented May 14, 2025

Description

This pull request adds read-only cluster config propeties in Redpanda Cloud. (2 are in the object storage properties reference)

Single sourcing of the SM content is done in redpanda-data/docs#1128

Cluster Configuration Documentation Enhancements:

  • Updated modules/manage/pages/cluster-maintenance/config-cluster.adoc to include information about read-only cluster properties, such as cluster_id, and clarified their behavior. Added a new section detailing how to view cluster property values using rpk and the Cloud API. [1] [2]

New Object Storage Properties:

  • Created a new file, modules/reference/pages/properties/object-storage-properties.adoc, to document object storage properties (e.g., cloud_storage_azure_storage_account and cloud_storage_azure_container). These properties are now referenced alongside cluster properties.

Navigation and Reference Updates:

  • Added a link to the newly created Object Storage Properties documentation in modules/ROOT/nav.adoc.
  • Expanded the list of included tags in modules/reference/pages/properties/cluster-properties.adoc to include additional cluster properties, such as cluster_id and object storage-related properties.

What's New Section:

  • Updated modules/get-started/pages/whats-new-cloud.adoc to highlight the ability to view read-only cluster configuration properties via rpk or the Cloud API.

Antora Playbook Update:

  • Modified local-antora-playbook.yml to adjust the branch configuration for the documentation repository, replacing the main branch with a specific feature branch.

Resolves https://redpandadata.atlassian.net/browse/DOC-190
Review deadline: Monday May 19

Page previews

What's New
View cluster property values
Cluster Configuration Properties reference
Object Storage Properties reference

Checks

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

@micheleRP micheleRP requested a review from a team as a code owner May 14, 2025 18:49
@netlify
Copy link

netlify bot commented May 14, 2025

Deploy Preview for rp-cloud ready!

Name Link
🔨 Latest commit 95813f1
🔍 Latest deploy log https://app.netlify.com/projects/rp-cloud/deploys/682df03d5fb80e00081f561b
😎 Deploy Preview https://deploy-preview-295--rp-cloud.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 May 14, 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

The changes reorganize and clarify documentation related to cluster configuration properties. In the cluster maintenance documentation, the description of cluster property behavior is separated from instructions on how to view them, and a new example command (rpk cluster config get) is added for viewing read-only cluster properties. Additionally, the list of included cluster configuration properties in the reference documentation is expanded by adding several new property tags, covering areas such as memory limits, authentication, cloud storage, and replication settings. No code logic or public API changes are involved; modifications are limited to documentation structure and content.

Assessment against linked issues

Objective Addressed Explanation
Document feature: Expose selected cluster configuration properties in cloud/console (DOC-190)

Possibly related PRs

  • DOC-1283 add rpk to config-cluster.adoc #278: Adds detailed instructions for setting cluster properties with rpk cluster config and expands related documentation; both PRs modify documentation on cluster configuration and involve rpk cluster config usage.

Suggested reviewers

  • alenkacz
  • asimms41
  • mattschumpert

🪧 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 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: 2

🔭 Outside diff range comments (2)
modules/manage/pages/cluster-maintenance/config-cluster.adoc (2)

30-34: ⚠️ Potential issue

Remove diff artifact markers: There are stray + and -- markers in the tabs section, likely leftover from a patch. Remove these so that the tabs render correctly:

[tabs]
======
`rpk`::
Use `rpk cluster config` to set cluster properties.
======

44-48: ⚠️ Potential issue

Remove leftover patch indicators: Similar diff markers (--, +) are present before the Cloud API heading. Eliminate these artifacts to ensure the section renders properly:

Cloud API::
Use the Cloud API to set cluster properties:
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 83827e4 and 9eac1b7.

📒 Files selected for processing (2)
  • modules/manage/pages/cluster-maintenance/config-cluster.adoc (1 hunks)
  • modules/reference/pages/properties/cluster-properties.adoc (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Redirect rules - rp-cloud
  • GitHub Check: Header rules - rp-cloud
  • GitHub Check: Pages changed - rp-cloud
🔇 Additional comments (1)
modules/manage/pages/cluster-maintenance/config-cluster.adoc (1)

4-7: Clear separation of description and feature list: The split into two paragraphs improves readability, and the xref links to Iceberg topics, data transforms, and audit logging appear correct.

Copy link
Contributor

@JakeSCahill JakeSCahill left a comment

Choose a reason for hiding this comment

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

LGTM 😄

Copy link

@alenkacz alenkacz left a comment

Choose a reason for hiding this comment

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

Left some comments. Thanks for the edits!


For a complete list of the cluster properties available in Redpanda Cloud, see xref:reference:properties/cluster-properties.adoc[Cluster Configuration Properties] and xref:reference:properties/object-storage-properties.adoc[Object Storage Properties].

NOTE: Some properties are read-only and cannot be changed. For example, `cluster_id` is a read-only property that is automatically set when the cluster is created.

Choose a reason for hiding this comment

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

we don't expose cluster_id so we should not mention that.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

"https://api.cloud.redpanda.com/v1/clusters/${RP_CLUSTER_ID}" \
-H 'accept: application/json'\
-H 'content-type: application/json' \
-d '{"cluster_configuration":{"computed_properties": {"data_transforms_enabled"}}}'

Choose a reason for hiding this comment

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

http get has no body 🤔 I don't think this is correct

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@alenkacz please review the updated draft!

@@ -0,0 +1,11 @@
= Object Storage Properties

Choose a reason for hiding this comment

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

I don't understand what is this page about 🤔 Can I see it live somewhere?

Copy link
Contributor Author

@micheleRP micheleRP May 20, 2025

Choose a reason for hiding this comment

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

@alenkacz in our self-managed docs, we have tiered storage cluster properties on a separate page. See https://docs.redpanda.com/current/reference/properties/. But we have an open doc issue to consolidate the cluster properties and the object storage properties, so when that happens, all these properties available in Cloud will be on one page.

@micheleRP micheleRP merged commit 4502204 into main May 21, 2025
5 checks passed
@micheleRP micheleRP deleted the DOC-190-Document-feature-Expose-selected-cluster-configuration-properties-in-cloud-console branch May 21, 2025 15:29
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.

5 participants