chore: prepare v3.0.2 release (#7438)

Author: zhxiaogg

CHANGELOG.md

@@ -1,6 +1,6 @@
 <!-- next version -->
 
-# v3.0.1
+# v3.0.2
 
 ## 🔒 Security 🔒
 

docs/sources/tempo/set-up-for-tracing/setup-tempo/deploy/kubernetes/tanka.md

@@ -227,7 +227,7 @@ Install the `k.libsonnet`, Jsonnet, and Memcached libraries.
 
    tempo {
     _images+:: {
-          tempo: 'grafana/tempo:3.0.1',
+          tempo: 'grafana/tempo:3.0.2',
       },
 
        tempo_distributor_container+:: container.withPorts([

example/docker-compose/distributed/docker-compose.yaml

@@ -1,7 +1,7 @@
 services:
   # tempo, backend and kafka
   distributor:
-    image: &tempoImage grafana/tempo:3.0.1
+    image: &tempoImage grafana/tempo:3.0.2
     depends_on:
       - redpanda
     command: "-target=distributor -config.file=/etc/tempo.yaml"

example/docker-compose/multitenant/docker-compose.yaml

@@ -1,6 +1,6 @@
 services:
   tempo:
-    image: grafana/tempo:3.0.1
+    image: grafana/tempo:3.0.2
     command: [ "-config.file=/etc/tempo.yaml", "-target=all"]
     volumes:
       - ./tempo.yaml:/etc/tempo.yaml

example/docker-compose/readme.md

@@ -33,9 +33,9 @@ See below for a list of all examples and the features they demonstrate
 ### Build images (optional)
 
 This step is not necessary, but it can be nice for local testing. The examples use the released
-`grafana/tempo:3.0.1` image by default. To test local code, run the following from the project root
-folder and either update the compose files to use `grafana/tempo:3.0.1` or tag the locally built image
-as `grafana/tempo:3.0.1`:
+`grafana/tempo:3.0.2` image by default. To test local code, run the following from the project root
+folder and either update the compose files to use `grafana/tempo:3.0.2` or tag the locally built image
+as `grafana/tempo:3.0.2`:
 
 ```console
 make docker-images

example/docker-compose/single-binary/docker-compose.yaml

@@ -1,6 +1,6 @@
 services:
   tempo:
-    image: grafana/tempo:3.0.1
+    image: grafana/tempo:3.0.2
     command: "-target=all -config.file=/etc/tempo.yaml"
     restart: always
     volumes:

example/tk/readme.md

@@ -22,7 +22,7 @@ k3d cluster create tempo --api-port 6443 --port "3000:80@loadbalancer"
 If you wish to use a local image, you can import these into k3d
 
 ```console
-k3d image import grafana/tempo:3.0.1 --cluster tempo
+k3d image import grafana/tempo:3.0.2 --cluster tempo
 ```
 
 Next either deploy the microservices or the single binary. You can also use tanka [inline environments](https://tanka.dev/inline-environments) to deploy Tempo with either of the two.

operations/jsonnet-compiled/microservices-with-extras/gen/Deployment-distributor.yaml

@@ -29,7 +29,7 @@ spec:
       - args:
         - -config.file=/conf/tempo.yaml
         - -target=distributor
-        image: grafana/tempo:3.0.1
+        image: grafana/tempo:3.0.2
         imagePullPolicy: IfNotPresent
         name: distributor
         ports:

operations/jsonnet-compiled/microservices-with-extras/gen/Deployment-metrics-generator.yaml

@@ -27,7 +27,7 @@ spec:
       - args:
         - -config.file=/conf/tempo.yaml
         - -target=metrics-generator
-        image: grafana/tempo:3.0.1
+        image: grafana/tempo:3.0.2
         name: metrics-generator
         ports:
         - containerPort: 3200

operations/jsonnet-compiled/microservices-with-extras/gen/Deployment-querier.yaml

@@ -29,7 +29,7 @@ spec:
       - args:
         - -config.file=/conf/tempo.yaml
         - -target=querier
-        image: grafana/tempo:3.0.1
+        image: grafana/tempo:3.0.2
         imagePullPolicy: IfNotPresent
         name: querier
         ports: