Update 26.2 (client compatibility, Iceberg translation) single sourcing for Cloud - #1857
Conversation
✅ Deploy Preview for redpanda-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughKafka client documentation now uses environment-independent validation text and grouped Go/Python client lists. Iceberg schema documentation now includes translation and Schema Registry context guidance for cloud environments, while broker version gating and version-specific wording remain limited to self-managed deployments. Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 `@modules/manage/pages/iceberg/specify-iceberg-schema.adoc`:
- Around line 440-445: Update the Schema Registry context guidance in the
env-cloud and non-cloud documentation blocks to explicitly describe whether key
decoding modes schema_id_prefix and schema_latest resolve schemas using the
configured Schema Registry context; if they do, document that lookup behavior
alongside the existing context and qualified-subject explanation.
🪄 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: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 51ad457d-5632-49c5-815f-47a428deb763
📒 Files selected for processing (2)
modules/develop/pages/kafka-clients.adocmodules/manage/pages/iceberg/specify-iceberg-schema.adoc
💤 Files with no reviewable changes (1)
- modules/develop/pages/kafka-clients.adoc
| ifndef::env-cloud[] | ||
| Starting in Redpanda 26.2, Schema Registry contexts are enabled by default. See xref:manage:schema-reg/schema-reg-contexts.adoc[Schema Registry contexts] to learn about contexts and qualified subject naming before you configure this property. | ||
| endif::[] | ||
| ifdef::env-cloud[] | ||
| Schema Registry contexts are enabled by default. See xref:manage:schema-reg/schema-reg-contexts.adoc[Schema Registry contexts] to learn about contexts and qualified subject naming before you configure this property. | ||
| endif::[] |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
Document Schema Registry context behavior for key decoding.
This section only names the legacy value modes, while this page now also supports key:mode=schema_id_prefix and key:mode=schema_latest. Clarify whether key schema lookups use the configured context, and document the behavior if they do.
🤖 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 `@modules/manage/pages/iceberg/specify-iceberg-schema.adoc` around lines 440 -
445, Update the Schema Registry context guidance in the env-cloud and non-cloud
documentation blocks to explicitly describe whether key decoding modes
schema_id_prefix and schema_latest resolve schemas using the configured Schema
Registry context; if they do, document that lookup behavior alongside the
existing context and qualified-subject explanation.
3 participants
Description
Related: redpanda-data/cloud-docs#657
This pull request updates documentation to unify and clarify instructions for both self-hosted and cloud environments, primarily by removing conditional content that previously differentiated between the two. It also makes version requirements and feature availability clearer for Redpanda features such as Kafka client compatibility and Iceberg schema translation.
Documentation unification and clarification:
env-cloud) conditionals from the Kafka client compatibility section, presenting a single, unified explanation of validated clients and compatibility for both self-hosted and cloud users.Version requirement and feature availability updates:
Resolves https://redpandadata.atlassian.net/browse/
Review deadline:
Page previews
These pages are single-sourced, and this PR contains the source/
env-cloudconditional changes. Review both renderings:Cloud (single-sourced) rendering — for SME review of Cloud accuracy. Built by the tandem cloud-docs PR #657, which pulls this branch and applies the
env-cloudattribute:Self-managed (streaming) rendering:
Checks