Add yaml file sample for Azure Storage (#2827)

* Add yaml file sample for storage * Improve sample description The example is from a configuration using helm charts * Update docs/sources/tempo/configuration/azure.md Co-authored-by: Kim Nylander <[email protected]> --------- Co-authored-by: Joe Elliott <[email protected]> Co-authored-by: Kim Nylander <[email protected]>
grafana · Aug 22, 2023 · 865896e · 865896e
1 parent 2c91ade
commit 865896e
Showing 1 changed file with 24 additions and 0 deletions.
diff --git a/docs/sources/tempo/configuration/azure.md b/docs/sources/tempo/configuration/azure.md
@@ -17,6 +17,30 @@ Tempo requires the following configuration to authenticate to and access Azure b
       - For a user-assigned managed identity, you'll need to set `user_assigned_id` to the client ID for the managed identity in the configuration file.
   - Via Azure Workload Identity. To use Azure Workload Identity, you'll need to enable Azure Workload Identity on your cluster, add the required label and annotation to the service account and the required pod label.
 
+## Sample configuration
+
+This sample configuration shows how to set up Azure blob storage using Helm charts and an access key from Kubernetes secrets.
+
+```yaml
+tempo:
+  storage:
+    trace:
+      backend: azure
+      azure:
+        container_name: container-name
+        storage_account_name: storage-account-name
+        storage_account_key: ${STORAGE_ACCOUNT_ACCESS_KEY}
+
+  extraArgs:
+    config.expand-env: true
+  extraEnv:
+    - name: STORAGE_ACCOUNT_ACCESS_KEY
+      valueFrom:
+        secretKeyRef:
+          name: secret-name
+          key: STORAGE_ACCOUNT_ACCESS_KEY
+```
+
 ## Azure blocklist polling
 
 If you are hosting Tempo on Azure, two values may need to be updated to ensure consistent successful blocklist polling. If you are