TempoStack Pods fails to contact with the object storage as using HTTP in RHOCP 4

Solution Verified - Updated -

Issue

  • TempoStack Pods with Error or CrashLoopBackOff Status
  • TempoStack tries to reach the S3 endpoint over HTTP, even when the endpoint is explicitly configured with HTTPS in the secret.
  • Tempo pods are trying to contact with the object storage using HTTP instead of HTTPS as defined in the endpoint

        level=error ts=2025-07-15T08:09:06.42393708Z caller=main.go:124 msg="error running Tempo" err="failed to init module services: error initialising module: store: failed to create store: unexpected error from ListObjects on <BucketName>: Get \"http://s3xxxxxxxxxx/?location=\": dial tcp xxxxxxx:80: i/o timeout"
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Red Hat Tempo Operator
    • 0.18.0
  • S3 Compatible Object Storage

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content