From b378c6ec064536762784e313a6c62ce08edb410f Mon Sep 17 00:00:00 2001 From: Mayne0213 Date: Fri, 9 Jan 2026 18:42:13 +0900 Subject: [PATCH] FIX(tempo): move extraEnv under tempo section for S3 credentials - Move extraEnv from top-level to tempo section where chart expects it - Move extraVolumeMounts under tempo section for proper WAL mounting - Fixes Access Denied error when connecting to MinIO --- tempo/helm-values.yaml | 36 +++++++++++++++++++----------------- 1 file changed, 19 insertions(+), 17 deletions(-) diff --git a/tempo/helm-values.yaml b/tempo/helm-values.yaml index 3c28204..197a1b0 100644 --- a/tempo/helm-values.yaml +++ b/tempo/helm-values.yaml @@ -63,32 +63,34 @@ tempo: enabled: true remoteWriteUrl: http://prometheus-kube-prometheus-prometheus.prometheus.svc:9090/api/v1/write + # MinIO S3 credentials + extraEnv: + - name: AWS_ACCESS_KEY_ID + valueFrom: + secretKeyRef: + name: minio-s3-credentials + key: AWS_ACCESS_KEY_ID + - name: AWS_SECRET_ACCESS_KEY + valueFrom: + secretKeyRef: + name: minio-s3-credentials + key: AWS_SECRET_ACCESS_KEY + + # Additional volume mounts for WAL + extraVolumeMounts: + - name: tempo-data + mountPath: /var/tempo + # ============================================================================= # Persistence - Disabled (use emptyDir for WAL, data in MinIO) # ============================================================================= persistence: enabled: false -# emptyDir for WAL +# emptyDir volume for WAL extraVolumes: - name: tempo-data emptyDir: {} -extraVolumeMounts: - - name: tempo-data - mountPath: /var/tempo - -# MinIO S3 credentials -extraEnv: - - name: AWS_ACCESS_KEY_ID - valueFrom: - secretKeyRef: - name: minio-s3-credentials - key: AWS_ACCESS_KEY_ID - - name: AWS_SECRET_ACCESS_KEY - valueFrom: - secretKeyRef: - name: minio-s3-credentials - key: AWS_SECRET_ACCESS_KEY # ============================================================================= # Service