Skip to content

DOC-1606 Document Cloud Feature Support ordered rack region preferenc…#537

Merged
JakeSCahill merged 4 commits into26.1from
DOC-1606-Document-Cloud-Feature-Support-ordered-rack-region-preference-for-leader-pinning
Mar 31, 2026
Merged

DOC-1606 Document Cloud Feature Support ordered rack region preferenc…#537
JakeSCahill merged 4 commits into26.1from
DOC-1606-Document-Cloud-Feature-Support-ordered-rack-region-preference-for-leader-pinning

Conversation

@micheleRP
Copy link
Copy Markdown
Contributor

@micheleRP micheleRP commented Mar 26, 2026

Description

This pull request single sources the new ordered rack preference feature for Leader Pinning. This updates cloud-docs with the new feature in the "What's New".

  • Updated the leader-pinning.adoc page to include new learning objectives about configuring preferred leader placement using rack labels, configuring ordered rack preference for priority-based failover, and identifying conditions where preferred placement is not possible. The title was also changed for clarity.
  • Added an entry to the April 2026 section of whats-new-cloud.adoc announcing support for the ordered_racks configuration value in Leader Pinning, explaining its behavior compared to the previous racks option.

Documentation build configuration:

  • Updated the Antora playbook (local-antora-playbook.yml) to pull documentation from the branch that documents the new ordered rack preference feature for Leader Pinning.

Resolves https://github.com/redpanda-data/documentation-private/issues/
Review deadline:

Page previews

What's New

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 March 26, 2026 02:08
@netlify
Copy link
Copy Markdown

netlify bot commented Mar 26, 2026

Deploy Preview for rp-cloud ready!

Name Link
🔨 Latest commit c817044
🔍 Latest deploy log https://app.netlify.com/projects/rp-cloud/deploys/69cb147f1dee1200082e7e05
😎 Deploy Preview https://deploy-preview-537--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
Copy Markdown
Contributor

coderabbitai bot commented Mar 26, 2026

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.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 89ac5dea-c701-4791-b4d7-6b209da7cd1e

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

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

This PR updates documentation and configuration files to document a new ordered rack preference feature for Leader Pinning. The local Antora playbook is updated to include a feature branch from the documentation repository. The Leader Pinning documentation page is renamed to "Configure Leader Pinning" and enriched with learning objective attributes. A new "April 2026" section is added to the "What's New in Redpanda Cloud" page to introduce the ordered rack preference capability.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • travisdowns
  • mattschumpert
  • nicolaferraro
🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title directly relates to the main objective of documenting the ordered rack preference feature for Leader Pinning, clearly summarizing the primary change across all modified files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check ✅ Passed The pull request description comprehensively covers all key changes, includes page previews, marks appropriate checkboxes, and provides sufficient context for reviewers.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch DOC-1606-Document-Cloud-Feature-Support-ordered-rack-region-preference-for-leader-pinning

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

:description: Learn about leader pinning and how to configure a preferred partition leader location based on cloud availability zones or regions.
= Configure Leader Pinning
:description: Learn about Leader Pinning and how to configure a preferred partition leader location based on cloud availability zones or regions.
:learning-objective-1: Configure preferred partition leader placement using rack labels
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The learning objectives do not render in the Cloud version. Should they?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

They don't show in the s-m version either. Asking Claude...

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The problem is clear now — the :learning-objective-N: attributes are defined inside the // tag::single-source[] block
(body), not in the page header. Let me check how working pages define them and how they're actually rendered.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@micheleRP @Feediver1 I don't know if we need changes to this file, unless the learning objectives are different for Cloud. For Self-Managed, the learning objective attributes are inside the single-source block here: https://github.com/redpanda-data/docs/blob/v-WIP/26.1/modules/develop/pages/produce-data/leader-pinning.adoc?plain=1

So once v-WIP/26.1 is merged to main, this page should just also render those same learning objectives

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

need to circle back after merge to make sure they render.

…red-rack-region-preference-for-leader-pinning
branches: HEAD
- url: https://github.com/redpanda-data/documentation
branches: [main, v/*, shared, site-search]
branches: [DOC-1607-Document-feature-Support-ordered-rack-region-preference-for-leader-pinning, v/*, shared, site-search]
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This branch is already merged in v-WIP/26.1, shouldn't this now point to v-WIP/26.1 for a preview?

@JakeSCahill JakeSCahill changed the base branch from main to 26.1 March 31, 2026 13:46
@JakeSCahill JakeSCahill merged commit d3995f3 into 26.1 Mar 31, 2026
@JakeSCahill JakeSCahill deleted the DOC-1606-Document-Cloud-Feature-Support-ordered-rack-region-preference-for-leader-pinning branch March 31, 2026 13:48
@coderabbitai coderabbitai bot mentioned this pull request Mar 31, 2026
4 tasks
JakeSCahill added a commit that referenced this pull request Mar 31, 2026
* DOC-1606 Document Cloud Feature Support ordered rack region preferenc… (#537)

* DOC01606 Document Cloud Feature Support ordered rack region preference for leader pinning

* style edit

* Apply suggestion from @JakeSCahill

---------

Co-authored-by: Joyce Fee <102751339+Feediver1@users.noreply.github.com>
Co-authored-by: Jake Cahill <45230295+JakeSCahill@users.noreply.github.com>

* DOC-1809 Document Cloud Feature Group-based Access Control via OIDC (#536)

* DOC-1809 Document Cloud Feature Group-based Access Control via OIDC

* note GBAC not supported in Serverless

* trigger Netlify rebuild

* Apply suggestion from @JakeSCahill

---------

Co-authored-by: Jake Cahill <45230295+JakeSCahill@users.noreply.github.com>

* DOC-1811 Document Cloud Feature User-based throughput quotas (#534)

* DOC-1811 Document Cloud Feature User-based throughput quotas

* fix: restore docs repo branch to main in local playbook

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: Jake Cahill <45230295+JakeSCahill@users.noreply.github.com>

* DOC-1825 Document Cloud Feature Cloud Topics (#526)

* DOC-1825 Document Cloud Feature Cloud Topics

* move files & add aliases, consistent with docs repo

* Add Next steps section to create-topic.adoc and rename nav entry to Overview

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Update modules/develop/pages/topics/index.adoc

Co-authored-by: Joyce Fee <102751339+Feediver1@users.noreply.github.com>

* incorporate doc review feedback

* chore: trigger Netlify rebuild for PR 526

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* fix: restore docs repo branch to main in local playbook

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Joyce Fee <102751339+Feediver1@users.noreply.github.com>
Co-authored-by: Joyce Fee <joyce@redpanda.com>

* DOC-1599 Document Cloud feature cross-region RRR on AWS (#524)

* DOC-1599 Document feature cross-region RRR on AWS

* coderabbit feedback

* update What's New

* Revert "DOC-1809 Document Cloud Feature Group-based Access Control via OIDC (#536)"

This reverts commit e6c4671.

---------

Co-authored-by: Michele Cyran <michele@redpanda.com>
Co-authored-by: Joyce Fee <102751339+Feediver1@users.noreply.github.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: Joyce Fee <joyce@redpanda.com>
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