Skip to content

docs: Fix cloud-divergent xrefs in single-sourced Cloud Topics content #1722

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
micheleRP merged 1 commit into from
May 29, 2026
+4 −2
Merged

docs: Fix cloud-divergent xrefs in single-sourced Cloud Topics content #1722

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion modules/develop/pages/manage-topics/cloud-topics.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@
:learning-objective-2: Create a Cloud Topic using rpk after enabling Cloud Topics on your cluster
:learning-objective-3: Identify Cloud Topics limitations and configurations that reduce cross-AZ networking costs
// tag::single-source[]
ifdef::env-cloud[:producers-page: develop:topics/configure-producers-for-cloud-topics.adoc]
ifndef::env-cloud[:producers-page: develop:manage-topics/configure-producers-for-cloud-topics.adoc]

ifndef::env-cloud[]
[NOTE]
Expand Down Expand Up @@ -83,6 +85,6 @@ You can make a topic a Cloud Topic only at topic creation time.

In addition to replication, cross-AZ ingress (producer) and egress (consumer) traffic can also contribute substantially to cloud networking costs. When running multi-AZ clusters in general, Redpanda strongly recommends using xref:develop:consume-data/follower-fetching.adoc[Follower Fetching], which allows consumers to avoid crossing network zones. When possible, you can use xref:develop:produce-data/leader-pinning.adoc[leader pinning], which positions a topic's partition leader close to the producers, providing a similar benefit for ingress traffic. These features can add additional savings to the replication cost savings of Cloud Topics.

For client-side tuning guidance, see xref:develop:manage-topics/configure-producers-for-cloud-topics.adoc[Configure producers for Cloud Topics].
For client-side tuning guidance, see xref:{producers-page}[Configure producers for Cloud Topics].

// end::single-source[]
2 changes: 1 addition & 1 deletion modules/develop/partials/cloud-topics-overview.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
// tag::intro[]
Starting in v26.1, Redpanda provides glossterm:Cloud Topic[,Cloud Topics] to support multi-modal streaming workloads in the most cost-effective way possible: as a per-topic configuration running mixed latency workloads. While standard Redpanda
ifdef::env-cloud[]
xref:get-started:config-topics.adoc[topics]
xref:develop:topics/config-topics.adoc[topics]
endif::[]
ifndef::env-cloud[]
xref:develop:manage-topics/config-topics.adoc[topics]
Expand Down
Loading