Skip to content

OBSDOCS-3855: Document high availability for TempoStack - #119033

Open
max-cx wants to merge 2 commits into
openshift:standalone-distributed-tracing-docs-mainfrom
max-cx:OBSDOCS-3855
Open

OBSDOCS-3855: Document high availability for TempoStack#119033
max-cx wants to merge 2 commits into
openshift:standalone-distributed-tracing-docs-mainfrom
max-cx:OBSDOCS-3855

Conversation

@max-cx

@max-cx max-cx commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Version(s): distributed-tracing-docs-main, distributed-tracing-docs-3.11

Issue: https://redhat.atlassian.net/browse/OBSDOCS-3855

Link to docs preview:
https://119033--ocpdocs-pr.netlify.app/openshift-distributed-tracing/latest/configuring/distr-tracing-tempo-high-availability.html
https://119033--ocpdocs-pr.netlify.app/openshift-distributed-tracing/latest/configuring/distr-tracing-tempo-configuring.html#distr-tracing-tempo-config-size_distr-tracing-tempo-configuring

QE review:

  • N/A. The linked PR that this PR serves as a review for was prepared by the SME.

Additional information: This PR is a peer review of #117798

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 31, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 31, 2026

Copy link
Copy Markdown

@max-cx: This pull request references OBSDOCS-3855 which is a valid jira issue.

Details

In response to this:

Version(s): distributed-tracing-docs-main, distributed-tracing-docs-3.11

Issue: https://redhat.atlassian.net/browse/OBSDOCS-3855

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information: Based on #117798

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Aug 31, 2026
@ocpdocs-previewbot

ocpdocs-previewbot commented Aug 31, 2026

Copy link
Copy Markdown

@max-cx
max-cx force-pushed the OBSDOCS-3855 branch 2 times, most recently from ffba890 to ca28ce6 Compare August 31, 2026 15:12
Add a Configuring high availability assembly for distributed tracing,
structured like the Loki tuning documentation, covering:

* replication factor and ingester quorum
* the per-component replica defaults of each deployment size
* pod placement and the operator-managed pod anti-affinity rules
* the PodDisruptionBudget of each component and the resulting behavior
  during cluster restarts
* zone-aware replication, how to configure it, and how to recover
  ingester pods from a failed zone

Also update the deployment sizing reference, which described the
pre-high-availability behavior: it now lists the default replica count of
every component per size, states that the per-component resource values
are per replica, and the resource totals account for the replica counts
instead of assuming a single replica of every component except the
ingester.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@max-cx
max-cx force-pushed the OBSDOCS-3855 branch 5 times, most recently from be5682a to d72c562 Compare September 1, 2026 14:13
@max-cx

max-cx commented Sep 1, 2026

Copy link
Copy Markdown
Contributor Author

LGTM.
Additional peer review done against the style guides by using Claude Code.

@max-cx max-cx changed the title WIP: OBSDOCS-3855: Document high availability for TempoStack OBSDOCS-3855: Document high availability for TempoStack Sep 1, 2026
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 1, 2026
@openshift-ci

openshift-ci Bot commented Sep 1, 2026

Copy link
Copy Markdown

@max-cx: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants