Skip to content

Add metadata to cluster properties that don't get restored after a whole cluster restore procedure#1095

Merged
JakeSCahill merged 3 commits intomainfrom
DOC-1285
May 1, 2025
Merged

Add metadata to cluster properties that don't get restored after a whole cluster restore procedure#1095
JakeSCahill merged 3 commits intomainfrom
DOC-1285

Conversation

@JakeSCahill
Copy link
Contributor

@JakeSCahill JakeSCahill commented Apr 29, 2025

Description

Resolves https://redpandadata.atlassian.net/browse/DOC-1285
Review deadline: April 30

This pull request updates documentation for cluster and object storage properties by adding a new attribute, "Gets restored during cluster restore," to clarify whether specific properties are restored during a cluster restore operation. Additionally, some formatting adjustments were made for consistency.

Documentation Updates:

New Attribute Added:

  • Added "Gets restored during cluster restore: No" to multiple properties in the cluster-properties.adoc and object-storage-properties.adoc files to indicate that these properties are not restored during a cluster restore. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15]

Formatting Adjustments:

  • Moved the "Restart required: Yes" section in object-storage-properties.adoc to ensure consistent ordering of attributes. [1] [2]

Page previews

Checks

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

Summary by CodeRabbit

  • Documentation
    • Updated property documentation to indicate which cluster and object storage properties do not get restored during a cluster restore operation.
    • Added a new attribute to relevant properties for clearer behavior clarification during cluster restore.
    • Adjusted the order of some property attributes for consistency.

@JakeSCahill JakeSCahill requested a review from a team as a code owner April 29, 2025 16:53
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Apr 29, 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 documentation for cluster and object storage properties was updated to include a new attribute, "Gets restored during cluster restore: No", for various properties. This addition clarifies which configuration properties are not restored during a cluster restore operation. The changes are purely additive, affecting only documentation text and property metadata annotations, with no modifications to property functionality, signatures, or behavior.

Changes

File(s) Change Summary
modules/reference/pages/properties/cluster-properties.adoc Added "Gets restored during cluster restore: No" to the cluster_id property documentation.
modules/reference/pages/properties/object-storage-properties.adoc Added "Gets restored during cluster restore: No" to multiple object storage properties; reordered some attributes for clarity.

Assessment against linked issues

Objective Addressed Explanation
Specify which cluster configs do not get restored (DOC-1285)

🪧 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

@JakeSCahill JakeSCahill requested a review from andrwng April 29, 2025 16:53
@netlify
Copy link

netlify bot commented Apr 29, 2025

Deploy Preview for redpanda-docs-preview ready!

Name Link
🔨 Latest commit 87d1b48
🔍 Latest deploy log https://app.netlify.com/sites/redpanda-docs-preview/deploys/6813354cb64ea90008d45b95
😎 Deploy Preview https://deploy-preview-1095--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 site configuration.

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 (1)
modules/reference/pages/properties/object-storage-properties.adoc (1)

120-126: Annotate cloud_storage_azure_container restore behavior

The restore attribute is helpful, but note that this block uses “Restart required” instead of the standard “Requires restart” header seen elsewhere. Consider renaming to *Requires restart:* Yes for consistency.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 460f54a and 8c8f4cc.

📒 Files selected for processing (2)
  • modules/reference/pages/properties/cluster-properties.adoc (1 hunks)
  • modules/reference/pages/properties/object-storage-properties.adoc (14 hunks)
🔇 Additional comments (13)
modules/reference/pages/properties/object-storage-properties.adoc (12)

36-40: Add restore behavior annotation for cloud_storage_api_endpoint

Including “Gets restored during cluster restore: No” makes it explicit that this endpoint configuration isn’t preserved during a restore operation. This improves clarity for operators.


84-90: Annotate cloud_storage_azure_adls_endpoint restore behavior

The new attribute clearly indicates that the ADLS endpoint override won’t be restored, aligning this property with the documented cluster restore semantics.


100-105: Document non-restoration of cloud_storage_azure_adls_port

Adding “Gets restored during cluster restore: No” for the ADLS port override ensures users know it won’t be reapplied after restore.


174-180: Mark cloud_storage_azure_shared_key as non-restored

Users should be aware that the shared key isn’t automatically reapplied on restore—this attribute makes that explicit.


190-196: Clarify non-restoration of cloud_storage_azure_storage_account

The new attribute ensures clarity that the storage account setting must be reset post-restore if needed.


206-212: Add restore info for cloud_storage_backend

Documenting that the chosen backend variant isn’t preserved during restore is a valuable operator hint.


240-246: Annotate cloud_storage_bucket as non-restored

Explicitly stating that the bucket setting won’t survive a restore prevents unexpected data-loss scenarios.


350-356: Document non-restoration of cloud_storage_cache_size

Adding the restore attribute for cache size helps users understand post-restore reconfiguration needs.


540-546: Annotate cloud_storage_credentials_host restore behavior

Now it’s clear that custom credential host settings aren’t reapplied automatically.


559-567: Mark cloud_storage_credentials_source as non-restored

This addition clarifies that the IAM credential source must be reconfigured after a restore.


1378-1386: Add restore annotation for cloud_storage_region

Making it explicit that region settings aren’t restored reduces confusion during disaster recovery.


1430-1438: Document non-restoration of cloud_storage_secret_key

This attribute ensures operators re-supply the secret key if required after a cluster restore.

modules/reference/pages/properties/cluster-properties.adoc (1)

301-307: Annotate cluster_id as non-restored

Adding “Gets restored during cluster restore: No” makes it explicit that the cluster identifier must be reset manually post-restore.

Copy link

@andrwng andrwng left a comment

Choose a reason for hiding this comment

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

LGTM! Thanks for making this change


*Gets restored during cluster restore:* No

*Accepted values*: `config_file`, `aws_instance_metadata`, `sts, gcp_instance_metadata`, `azure_vm_instance_metadata`, `azure_aks_oidc_federation`
Copy link
Contributor

Choose a reason for hiding this comment

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

Accepted values appear in [] in other entries.

Copy link
Contributor

@asimms41 asimms41 left a comment

Choose a reason for hiding this comment

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

LGTM. Just a couple of minor comments about consistency.

Co-authored-by: Angela Simms <102690377+asimms41@users.noreply.github.com>
@JakeSCahill JakeSCahill merged commit 2ebb9ce into main May 1, 2025
3 checks passed
@JakeSCahill JakeSCahill deleted the DOC-1285 branch May 1, 2025 08:48
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.

3 participants