[dependabot]

Bumps github.com/grafana/tempo-operator from 0.22.0 to 0.23.1.

Release notes

Sourced from github.com/grafana/tempo-operator's releases.

Release v0.23.1

💡 Enhancements 💡

• operator: Upgrade Go to 1.26.10 (#1691)
• tempostack, tempomonolithic: Update Tempo to 2.10.10 (#1689)

Components

• Tempo: v2.10.10

Support

This release supports Kubernetes 1.25 to 1.36.

Release v0.23.0

💡 Enhancements 💡

• tempostack, tempomonolithic: Update the gateway image to main-2026-10-13-d17ce87 and the opa-openshift image to main-2026-09-22-cc6817a. (#1672)

• operator: Update Kubernetes dependencies to 1.37 (#1675)

• tempostack, tempomonolithic: Roll out pods when the storage secret changes (#1655)

• tempostack: Support overriding the pod anti affinity of a TempoStack component via the new spec.template..podAntiAffinity field (#1662) By default the pods of a component only prefer to be scheduled onto different nodes and failure domains, which the scheduler may ignore. This is true of zone-aware stacks as well: topology spread constraints balance the pods across zones, but inside a zone several replicas of a component can still land on the same node.

  A stack that needs a hard guarantee now sets its own anti affinity, per component:

  spec:
    template:
      ingester:
        podAntiAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
          - labelSelector:
              matchLabels:
                app.kubernetes.io/component: ingester
                app.kubernetes.io/instance: sample
            topologyKey: kubernetes.io/hostname

  The field replaces the default anti affinity of that component rather than adding to it. Note that a required term leaves the surplus pods Pending when a component has more replicas than schedulable nodes.

  The behavior follows the Grafana Loki Operator, which exposes the same field per component.

🧰 Bug fixes 🧰

... (truncated)

Changelog

Sourced from github.com/grafana/tempo-operator's changelog.

0.23.1

💡 Enhancements 💡

• operator: Upgrade Go to 1.26.10 (#1691)
• tempostack, tempomonolithic: Update Tempo to 2.10.10 (#1689)

Components

• Tempo: v2.10.10

Support

This release supports Kubernetes 1.25 to 1.36.

0.23.0

💡 Enhancements 💡

• tempostack, tempomonolithic: Update the gateway image to main-2026-10-13-d17ce87 and the opa-openshift image to main-2026-09-22-cc6817a. (#1672)

• operator: Update Kubernetes dependencies to 1.37 (#1675)

• tempostack, tempomonolithic: Roll out pods when the storage secret changes (#1655)

• tempostack: Support overriding the pod anti affinity of a TempoStack component via the new spec.template..podAntiAffinity field (#1662) By default the pods of a component only prefer to be scheduled onto different nodes and failure domains, which the scheduler may ignore. This is true of zone-aware stacks as well: topology spread constraints balance the pods across zones, but inside a zone several replicas of a component can still land on the same node.

  A stack that needs a hard guarantee now sets its own anti affinity, per component:

  spec:
    template:
      ingester:
        podAntiAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
          - labelSelector:
              matchLabels:
                app.kubernetes.io/component: ingester
                app.kubernetes.io/instance: sample
            topologyKey: kubernetes.io/hostname

  The field replaces the default anti affinity of that component rather than adding to it. Note that a required term leaves the surplus pods Pending when a component has more replicas than schedulable nodes.

  The behavior follows the Grafana Loki Operator, which exposes the same field per component.

🧰 Bug fixes 🧰

... (truncated)

Commits

• 2038af3 Prepare Release 0.23.1 (#1701)
• a67e02b Update Tempo to v2.10.10 (#1689)
• 5a482be chore(deps): update docker/setup-buildx-action action to v4.4.1 (#1694)
• 0bee63d chore(deps): bump distroless/static from 1c2c046 to d620678 (#1699)
• d0ca0ba chore(deps): bump distroless/static from f7f8f72 to 1c2c046 (#1623)
• 769d318 fix(deps): update k8s.io/utils digest to cf1189d (#1557)
• 4042e52 chore(deps): update module cel.dev/expr to v0.25.3 (#1572)
• 7640483 chore(deps): update github.com/google/pprof digest to 1facf8f (#1595)
• b3b8e24 chore(deps): bump the github-actions group across 1 directory with 3 updates ...
• 7004974 chore(deps): update sigs.k8s.io/json digest to 11ed52e (#1676)
• Additional commits viewable in compare view

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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

• Source mode: Auto
• Repository: rhobs/observability-operator
• Branch: release-coo-1.5
• File: .coderabbit.yaml
• Commit: a8e2cd4
• Layers: Repository YAML (base), Organization UI (inherited)
• Review profile: CHILL
• Plan: Enterprise
• Run ID: d5453268-6248-4a32-8b9f-cdc5a8dfa85e

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

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a rhobs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[jan--f]

/ok-to-test

[jan--f]

Reviewed the dependency and API changes and passing GitHub Actions. OpenShift-specific Prow coverage is not currently reported for this branch.

[jan--f]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dependabot[bot], jan--f

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [jan--f]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jan--f]

@dependabot rebase

[openshift-ci]

rebase

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.

[jan--f]

/lgtm