Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.
Object storage
Tempo Operator supports AWS S3, Azure, GCS, Minio and OpenShift Data Foundation for TempoStack object storage.
AWS S3
Requirements
- Create a bucket on AWS.
Installation
Deploy the Tempo Operator to your cluster.
Create an Object Storage secret with keys as follows:
kubectl create secret generic tempostack-dev-s3 \ --from-literal=bucket="<BUCKET_NAME>" \ --from-literal=endpoint="<AWS_BUCKET_ENDPOINT>" \ --from-literal=access_key_id="<AWS_ACCESS_KEY_ID>" \ --from-literal=access_key_secret="<AWS_ACCESS_KEY_SECRET>"where
tempostack-dev-s3is the secret name.Create an instance of TempoStack by referencing the secret name and type as
s3:spec: storage: secret: name: tempostack-dev-s3 type: s3
Azure
Requirements
- Create a bucket on Azure.
Installation
Deploy the Tempo Operator to your cluster.
Create an Object Storage secret with keys as follows:
kubectl create secret generic tempostack-dev-azure \ --from-literal=container="<AZURE_CONTAINER_NAME>" \ --from-literal=account_name="<AZURE_ACCOUNT_NAME>" \ --from-literal=account_key="<AZURE_ACCOUNT_KEY>"where
tempostack-dev-azureis the secret name.Create an instance of TempoStack by referencing the secret name and type as
azure:spec: storage: secret: name: tempostack-dev-azure type: azure
Google Cloud Storage
Requirements
- Create a project on Google Cloud Platform.
- Create a bucket under same project.
- Create a service account under same project for GCP authentication.
Installation
Deploy the Tempo Operator to your cluster.
Copy the service account credentials received from GCP into a file name
key.json.Create an Object Storage secret with keys
bucketnameandkey.jsonas follows:kubectl create secret generic tempostack-dev-gcs \ --from-literal=bucketname="<BUCKET_NAME>" \ --from-file=key.json="<PATH/TO/KEY.JSON>"where
tempostack-dev-gcsis the secret name,<BUCKET_NAME>is the name of bucket created in requirements step and<PATH/TO/KEY.JSON>is the file path where thekey.jsonwas copied to.Create an instance of TempoStack by referencing the secret name and type as
gcs:spec: storage: secret: name: tempostack-dev-gcs type: gcs
MinIO
Requirements
Deploy MinIO on your cluster, e.g. using the MinIO Operator or another method.
Create a bucket on MinIO using the CLI.
Installation
Deploy the Tempo Operator to your cluster.
Create an Object Storage secret with keys as follows:
kubectl create secret generic tempostack-dev-minio \ --from-literal=bucket="<BUCKET_NAME>" \ --from-literal=endpoint="<MINIO_BUCKET_ENDPOINT>" \ --from-literal=access_key_id="<MINIO_ACCESS_KEY_ID>" \ --from-literal=access_key_secret="<MINIO_ACCESS_KEY_SECRET>"where
tempostack-dev-miniois the secret name.Create an instance of TempoStack by referencing the secret name and type as
s3:spec: storage: secret: name: tempostack-dev-minio type: s3
OpenShift Data Foundation
Requirements
Deploy the OpenShift Data Foundation on your cluster.
Create a bucket via an ObjectBucketClaim.
Installation
Deploy the Tempo Operator to your cluster.
Create an Object Storage secret with keys as follows:
kubectl create secret generic tempostack-dev-odf \ --from-literal=bucket="<BUCKET_NAME>" \ --from-literal=endpoint="https://s3.openshift-storage.svc" \ --from-literal=access_key_id="<ACCESS_KEY_ID>" \ --from-literal=access_key_secret="<ACCESS_KEY_SECRET>"where
tempostack-dev-odfis the secret name. You can copy the values forBUCKET_NAME,ACCESS_KEY_IDandACCESS_KEY_SECRETfrom your ObjectBucketClaim’s accompanied secret.Create an instance of TempoStack by referencing the secret name and type as
s3:spec: storage: secret: name: tempostack-dev-odf type: s3


