diff --git a/.chloggen/add-must-gather.yaml b/.chloggen/add-must-gather.yaml
deleted file mode 100755
index 4ddf81131..000000000
--- a/.chloggen/add-must-gather.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: new_component
-
-# The name of the component, or a single word describing the area of concern, (e.g. tempostack, tempomonolithic, github action)
-component: must-gather
-
-# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Add must-gather to collect information about the components deployed by the operator in a cluster.
-
-# One or more tracking issues related to the change
-issues: [1033]
-
-# (Optional) One or more lines of additional information to render under the primary note.
-# These lines will be padded with 2 spaces and then inserted directly into the document.
-# Use pipe (|) for multiline entries.
-subtext:
diff --git a/.chloggen/add_pod_security_context.yaml b/.chloggen/add_pod_security_context.yaml
deleted file mode 100755
index e3c9119e4..000000000
--- a/.chloggen/add_pod_security_context.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: enhancement
-
-# The name of the component, or a single word describing the area of concern, (e.g. tempostack, tempomonolithic, github action)
-component: tempostack
-
-# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Expose a way to set a PodSecurityContext on each component
-
-# One or more tracking issues related to the change
-issues: [996]
-
-# (Optional) One or more lines of additional information to render under the primary note.
-# These lines will be padded with 2 spaces and then inserted directly into the document.
-# Use pipe (|) for multiline entries.
-subtext:
diff --git a/.chloggen/bump_jaeger-to-1.62.yaml b/.chloggen/bump_jaeger-to-1.62.yaml
deleted file mode 100755
index 96aa8c82d..000000000
--- a/.chloggen/bump_jaeger-to-1.62.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: enhancement
-
-# The name of the component, or a single word describing the area of concern, (e.g. tempostack, tempomonolithic, github action)
-component: tempostack, tempomonolithic
-
-# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: bump jaeger to v1.62
-
-# One or more tracking issues related to the change
-issues: [1050]
-
-# (Optional) One or more lines of additional information to render under the primary note.
-# These lines will be padded with 2 spaces and then inserted directly into the document.
-# Use pipe (|) for multiline entries.
-subtext:
diff --git a/.chloggen/bump_tempo-query.yaml b/.chloggen/bump_tempo-query.yaml
deleted file mode 100755
index b261b6c0d..000000000
--- a/.chloggen/bump_tempo-query.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: enhancement
-
-# The name of the component, or a single word describing the area of concern, (e.g. tempostack, tempomonolithic, github action)
-component: tempostack
-
-# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Bump jaeger to v1.60 by replacing the tempo-query gRPC storage plugin due to the deprecation in Jaeger 1.58.0 with a gRPC standalone service.
-
-# One or more tracking issues related to the change
-issues: [1025]
-
-# (Optional) One or more lines of additional information to render under the primary note.
-# These lines will be padded with 2 spaces and then inserted directly into the document.
-# Use pipe (|) for multiline entries.
-subtext:
diff --git a/.chloggen/enable-130.yaml b/.chloggen/enable-130.yaml
deleted file mode 100644
index 729e6b222..000000000
--- a/.chloggen/enable-130.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: 'enhancement'
-
-# The name of the component, or a single word describing the area of concern, (e.g. operator, github action)
-component: operator
-
-# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Kubernetes 1.30 enablement
-
-# One or more tracking issues related to the change
-issues: [1030]
-
-# (Optional) One or more lines of additional information to render under the primary note.
-# These lines will be padded with 2 spaces and then inserted directly into the document.
-# Use pipe (|) for multiline entries.
-subtext:
diff --git a/.chloggen/fix-ingress-type-default.yaml b/.chloggen/fix-ingress-type-default.yaml
deleted file mode 100755
index 7097693cc..000000000
--- a/.chloggen/fix-ingress-type-default.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
-
-# The name of the component, or a single word describing the area of concern, (e.g. tempostack, tempomonolithic, github action)
-component: tempostack
-
-# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: The default value for the IngressType type is now correctly "" (empty string). Previously, it was impossible to select it in tools like the OpenShift web console, what could cause some issues.
-
-# One or more tracking issues related to the change
-issues: [1054]
-
-# (Optional) One or more lines of additional information to render under the primary note.
-# These lines will be padded with 2 spaces and then inserted directly into the document.
-# Use pipe (|) for multiline entries.
-subtext:
diff --git a/.chloggen/fix_hashring.yaml b/.chloggen/fix_hashring.yaml
deleted file mode 100755
index f1d8a8d05..000000000
--- a/.chloggen/fix_hashring.yaml
+++ /dev/null
@@ -1,19 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
-
-# The name of the component, or a single word describing the area of concern, (e.g. tempostack, tempomonolithic, github action)
-component: tempostack
-
-# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Add support for memberlist bind network configuration
-
-# One or more tracking issues related to the change
-issues: [1060]
-
-# (Optional) One or more lines of additional information to render under the primary note.
-# These lines will be padded with 2 spaces and then inserted directly into the document.
-# Use pipe (|) for multiline entries.
-subtext: |
-  Adds support to configure the memberlist instance_addr field using the pod network IP range instead of the default private network range used. 
-  In managed Kubernetes/OpenShift cluster environments as well as in special on-prem setup the private IP range might not be available for using them. 
-  With this change set the TempoStack administrator can choose as a bind address the current pod network IP assigned by the cluster's pod network.
diff --git a/.chloggen/fix_jaeger-query-certs.yaml b/.chloggen/fix_jaeger-query-certs.yaml
deleted file mode 100755
index d1ecc3405..000000000
--- a/.chloggen/fix_jaeger-query-certs.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
-
-# The name of the component, or a single word describing the area of concern, (e.g. tempostack, tempomonolithic, github action)
-component: tempostack
-
-# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: grant jaeer-query access to pki certs
-
-# One or more tracking issues related to the change
-issues: [1051]
-
-# (Optional) One or more lines of additional information to render under the primary note.
-# These lines will be padded with 2 spaces and then inserted directly into the document.
-# Use pipe (|) for multiline entries.
-subtext:
diff --git a/.chloggen/fix_red-metrics.yaml b/.chloggen/fix_red-metrics.yaml
deleted file mode 100755
index 4421bb9fc..000000000
--- a/.chloggen/fix_red-metrics.yaml
+++ /dev/null
@@ -1,41 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: breaking
-
-# The name of the component, or a single word describing the area of concern, (e.g. tempostack, tempomonolithic, github action)
-component: tempostack
-
-# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Use new default metrics namespace/prefix for span RED metrics in Jaeger query.
-
-
-# One or more tracking issues related to the change
-issues: [1072]
-
-# (Optional) One or more lines of additional information to render under the primary note.
-# These lines will be padded with 2 spaces and then inserted directly into the document.
-# Use pipe (|) for multiline entries.
-subtext: |
-  Use the new RED metrics default namespace `traces.span.metrics` for retrieval from Prometheus.
-  Since OpenTelemetry Collector version 0.109.0 the default namespace is set to traces.span.metrics.
-  The namespace taken into account by jaeger-query can be configured via a TempoStack CR entry.
-  To achieve this the Operator will set the jaeger-query `--prometheus.query.namespace=` flag.
-  Since Jaeger version 1.62, jaeger-query uses `traces.span.metrics` as default too.
-
-  Example how to restore the default namespace used prior to version `0.109.0`, by configuring an empty value for `redMetricsNamespace` in the TempoStack CR:
-  ```
-  apiVersion: tempo.grafana.com/v1alpha1
-  kind: TempoStack
-  ...
-  spec:
-    template:
-      queryFrontend:
-        jaegerQuery:
-          enabled: true
-          monitorTab:
-            enabled: true
-            prometheusEndpoint: "http://myPromInstance:9090"
-            redMetricsNamespace: ""
-  ```
-  More details can be found here:
-  - https://github.com/jaegertracing/jaeger/pull/6007
-  - https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/34485
diff --git a/.chloggen/fix_sm_query_frontend.yaml b/.chloggen/fix_sm_query_frontend.yaml
deleted file mode 100755
index b949ec15d..000000000
--- a/.chloggen/fix_sm_query_frontend.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
-
-# The name of the component, or a single word describing the area of concern, (e.g. tempostack, tempomonolithic, github action)
-component: tempostack
-
-# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Create query-frontend service monitor with HTTP protocol when gateway is disabled
-
-# One or more tracking issues related to the change
-issues: [1070]
-
-# (Optional) One or more lines of additional information to render under the primary note.
-# These lines will be padded with 2 spaces and then inserted directly into the document.
-# Use pipe (|) for multiline entries.
-subtext:
diff --git a/.chloggen/fix_sts_when_tls_is_enabled.yaml b/.chloggen/fix_sts_when_tls_is_enabled.yaml
deleted file mode 100755
index 71c78a1da..000000000
--- a/.chloggen/fix_sts_when_tls_is_enabled.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
-
-# The name of the component, or a single word describing the area of concern, (e.g. tempostack, tempomonolithic, github action)
-component: tempostack
-
-# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note:  Fix panic when toggling spec.storage.tls.enabled to true, when using Tempo with AWS STS
-
-# One or more tracking issues related to the change
-issues: [1067]
-
-# (Optional) One or more lines of additional information to render under the primary note.
-# These lines will be padded with 2 spaces and then inserted directly into the document.
-# Use pipe (|) for multiline entries.
-subtext:
diff --git a/.chloggen/fix_tls_tempo-query.yaml b/.chloggen/fix_tls_tempo-query.yaml
deleted file mode 100755
index 4fa4a9b34..000000000
--- a/.chloggen/fix_tls_tempo-query.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
-
-# The name of the component, or a single word describing the area of concern, (e.g. tempostack, tempomonolithic, github action)
-component: tempostack, tempomonolithic
-
-# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Mount CA and Certs to tempo-query when tls is enabled.
-
-# One or more tracking issues related to the change
-issues: [1038]
-
-# (Optional) One or more lines of additional information to render under the primary note.
-# These lines will be padded with 2 spaces and then inserted directly into the document.
-# Use pipe (|) for multiline entries.
-subtext:
diff --git a/.chloggen/fix_unknown_flag.yaml b/.chloggen/fix_unknown_flag.yaml
deleted file mode 100755
index 521c26c4a..000000000
--- a/.chloggen/fix_unknown_flag.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
-
-# The name of the component, or a single word describing the area of concern, (e.g. tempostack, tempomonolithic, github action)
-component: tempostack, tempomonolithic
-
-# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: The operator no longer sets the `--prometheus.query.support-spanmetrics-connector` flag that got removed in Jaeger 1.58.
-
-# One or more tracking issues related to the change
-issues: [1036]
-
-# (Optional) One or more lines of additional information to render under the primary note.
-# These lines will be padded with 2 spaces and then inserted directly into the document.
-# Use pipe (|) for multiline entries.
-subtext: The Flag controled whether the metrics queries should match the OpenTelemetry Collector's spanmetrics connector naming or spanmetrics processor naming.
diff --git a/.chloggen/reencrypt_gw_default.yaml b/.chloggen/reencrypt_gw_default.yaml
deleted file mode 100755
index 7fc7d9db0..000000000
--- a/.chloggen/reencrypt_gw_default.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: enhancement
-
-# The name of the component, or a single word describing the area of concern, (e.g. tempostack, tempomonolithic, github action)
-component: tempostack, tempomonolithic
-
-# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Make re-encrypt route the default TLS termination to allow access outside the cluster.
-
-# One or more tracking issues related to the change
-issues: [1027]
-
-# (Optional) One or more lines of additional information to render under the primary note.
-# These lines will be padded with 2 spaces and then inserted directly into the document.
-# Use pipe (|) for multiline entries.
-subtext:
diff --git a/.chloggen/tempo-query-find-traces-jobs.yaml b/.chloggen/tempo-query-find-traces-jobs.yaml
deleted file mode 100755
index 294deef9f..000000000
--- a/.chloggen/tempo-query-find-traces-jobs.yaml
+++ /dev/null
@@ -1,21 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: enhancement
-
-# The name of the component, or a single word describing the area of concern, (e.g. tempostack, tempomonolithic, github action)
-component: tempostack, tempomonolithic
-
-# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Add tempo-query CRD option to speed up trace search.
-
-# One or more tracking issues related to the change
-issues: [1048]
-
-# (Optional) One or more lines of additional information to render under the primary note.
-# These lines will be padded with 2 spaces and then inserted directly into the document.
-# Use pipe (|) for multiline entries.
-subtext: |
-  Following CRD options were added to speed up trace search in Jaeger UI/API. The trace search first
-  searches for traceids and then it gets a full trace. With this configuration option the requests
-  to get the full trace can be run in parallel:
-  For `TempoStack` - `spec.template.queryFrontend.jaegerQuery.findTracesConcurrentRequests`  
-  For `TempoMonolithic` - `spec.jaegerui.findTracesConcurrentRequests`
diff --git a/.chloggen/tempo-query_ReadinessProbe.yaml b/.chloggen/tempo-query_ReadinessProbe.yaml
deleted file mode 100755
index f54c16d5d..000000000
--- a/.chloggen/tempo-query_ReadinessProbe.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
-
-# The name of the component, or a single word describing the area of concern, (e.g. tempostack, tempomonolithic, github action)
-component: tempostack
-
-# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Use the ReadinessProbe to better indicate when tempo-query is ready to accept requests. Improving the startup reliability by avoiding lost data.
-
-# One or more tracking issues related to the change
-issues: [1058]
-
-# (Optional) One or more lines of additional information to render under the primary note.
-# These lines will be padded with 2 spaces and then inserted directly into the document.
-# Use pipe (|) for multiline entries.
-subtext: Without a readiness check in place, there is a risk that data will be lost when the queryfrontend pod is ready but the tempo query API is not yet available.
diff --git a/.chloggen/tempo-query_server-tls.yaml b/.chloggen/tempo-query_server-tls.yaml
deleted file mode 100755
index eaf5ce7d5..000000000
--- a/.chloggen/tempo-query_server-tls.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: enhancement
-
-# The name of the component, or a single word describing the area of concern, (e.g. tempostack, tempomonolithic, github action)
-component: tempostack
-
-# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: bump tempo-query to version with separate tls settings for server and client
-
-# One or more tracking issues related to the change
-issues: [1057]
-
-# (Optional) One or more lines of additional information to render under the primary note.
-# These lines will be padded with 2 spaces and then inserted directly into the document.
-# Use pipe (|) for multiline entries.
-subtext:
diff --git a/.chloggen/timeout.yaml b/.chloggen/timeout.yaml
deleted file mode 100755
index e8de1bf44..000000000
--- a/.chloggen/timeout.yaml
+++ /dev/null
@@ -1,18 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: breaking
-
-# The name of the component, or a single word describing the area of concern, (e.g. tempostack, tempomonolithic, github action)
-component: tempostack, tempomonolithic
-
-# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Add unified timeout configuration. It changes the default to 30s.
-
-# One or more tracking issues related to the change
-issues: [1045]
-
-# (Optional) One or more lines of additional information to render under the primary note.
-# These lines will be padded with 2 spaces and then inserted directly into the document.
-# Use pipe (|) for multiline entries.
-subtext: |
-  Adding `spec.timeout` CRD option to configure timeout on all components and default it to 30s.
-  Before Tempo server was defaulting to 3m, gateway to 2m, OpenShift route to 30s (for query), oauth-proxy to 30s (for query).
diff --git a/.chloggen/update_tempo.yaml b/.chloggen/update_tempo.yaml
deleted file mode 100644
index d9b67b28d..000000000
--- a/.chloggen/update_tempo.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: enhancement
-
-# The name of the component, or a single word describing the area of concern, (e.g. tempostack, tempomonolithic, github action)
-component: operator
-
-# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Update Tempo to v2.6.1
-
-# One or more tracking issues related to the change
-issues: [1044, 1064]
-
-# (Optional) One or more lines of additional information to render under the primary note.
-# These lines will be padded with 2 spaces and then inserted directly into the document.
-# Use pipe (|) for multiline entries.
-subtext:
diff --git a/CHANGELOG.md b/CHANGELOG.md
index f53be2782..650179799 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -3,6 +3,82 @@ Changes by Version
 
 <!-- next version -->
 
+## 0.14.0
+
+### 🛑 Breaking changes 🛑
+
+- `tempostack`: Use new default metrics namespace/prefix for span RED metrics in Jaeger query. (#1072)
+  Use the new RED metrics default namespace `traces.span.metrics` for retrieval from Prometheus.
+  Since OpenTelemetry Collector version 0.109.0 the default namespace is set to traces.span.metrics.
+  The namespace taken into account by jaeger-query can be configured via a TempoStack CR entry.
+  To achieve this the Operator will set the jaeger-query `--prometheus.query.namespace=` flag.
+  Since Jaeger version 1.62, jaeger-query uses `traces.span.metrics` as default too.
+  
+  Example how to restore the default namespace used prior to version `0.109.0`, by configuring an empty value for `redMetricsNamespace` in the TempoStack CR:
+  ```
+  apiVersion: tempo.grafana.com/v1alpha1
+  kind: TempoStack
+  ...
+  spec:
+    template:
+      queryFrontend:
+        jaegerQuery:
+          enabled: true
+          monitorTab:
+            enabled: true
+            prometheusEndpoint: "http://myPromInstance:9090"
+            redMetricsNamespace: ""
+  ```
+  More details can be found here:
+  - https://github.com/jaegertracing/jaeger/pull/6007
+  - https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/34485
+  
+- `tempostack, tempomonolithic`: Add unified timeout configuration. It changes the default to 30s. (#1045)
+  Adding `spec.timeout` CRD option to configure timeout on all components and default it to 30s.
+  Before Tempo server was defaulting to 3m, gateway to 2m, OpenShift route to 30s (for query), oauth-proxy to 30s (for query).
+  
+
+### 🚀 New components 🚀
+
+- `must-gather`: Add must-gather to collect information about the components deployed by the operator in a cluster. (#1033)
+
+### 💡 Enhancements 💡
+
+- `tempostack`: Expose a way to set a PodSecurityContext on each component (#996)
+- `tempostack, tempomonolithic`: bump jaeger to v1.62 (#1050)
+- `tempostack`: Bump jaeger to v1.60 by replacing the tempo-query gRPC storage plugin due to the deprecation in Jaeger 1.58.0 with a gRPC standalone service. (#1025)
+- `operator`: Kubernetes 1.30 enablement (#1030)
+- `tempostack, tempomonolithic`: Make re-encrypt route the default TLS termination to allow access outside the cluster. (#1027)
+- `tempostack, tempomonolithic`: Add tempo-query CRD option to speed up trace search. (#1048)
+  Following CRD options were added to speed up trace search in Jaeger UI/API. The trace search first
+  searches for traceids and then it gets a full trace. With this configuration option the requests
+  to get the full trace can be run in parallel:
+  For `TempoStack` - `spec.template.queryFrontend.jaegerQuery.findTracesConcurrentRequests`  
+  For `TempoMonolithic` - `spec.jaegerui.findTracesConcurrentRequests`
+  
+- `tempostack`: bump tempo-query to version with separate tls settings for server and client (#1057)
+- `operator`: Update Tempo to v2.6.1 (#1044, #1064)
+
+### 🧰 Bug fixes 🧰
+
+- `tempostack`: The default value for the IngressType type is now correctly "" (empty string). Previously, it was impossible to select it in tools like the OpenShift web console, what could cause some issues. (#1054)
+- `tempostack`: Add support for memberlist bind network configuration (#1060)
+  Adds support to configure the memberlist instance_addr field using the pod network IP range instead of the default private network range used. 
+  In managed Kubernetes/OpenShift cluster environments as well as in special on-prem setup the private IP range might not be available for using them. 
+  With this change set the TempoStack administrator can choose as a bind address the current pod network IP assigned by the cluster's pod network.
+  
+- `tempostack`: grant jaeer-query access to pki certs (#1051)
+- `tempostack`: Create query-frontend service monitor with HTTP protocol when gateway is disabled (#1070)
+- `tempostack`: Fix panic when toggling spec.storage.tls.enabled to true, when using Tempo with AWS STS (#1067)
+- `tempostack, tempomonolithic`: Mount CA and Certs to tempo-query when tls is enabled. (#1038)
+- `tempostack, tempomonolithic`: The operator no longer sets the `--prometheus.query.support-spanmetrics-connector` flag that got removed in Jaeger 1.58. (#1036)
+  The Flag controled whether the metrics queries should match the OpenTelemetry Collector's spanmetrics connector naming or spanmetrics processor naming.
+- `tempostack`: Use the ReadinessProbe to better indicate when tempo-query is ready to accept requests. Improving the startup reliability by avoiding lost data. (#1058)
+  Without a readiness check in place, there is a risk that data will be lost when the queryfrontend pod is ready but the tempo query API is not yet available.
+
+### Components
+- Tempo: [v2.6.1](https://github.com/grafana/tempo/releases/tag/v2.6.1)
+
 ## 0.13.0
 
 ### 🧰 Bug fixes 🧰
diff --git a/Makefile b/Makefile
index d20cf86c9..4cf6707d0 100644
--- a/Makefile
+++ b/Makefile
@@ -1,5 +1,5 @@
 # Current Operator version
-OPERATOR_VERSION ?= 0.13.0
+OPERATOR_VERSION ?= 0.14.0
 TEMPO_VERSION ?= 2.6.1
 JAEGER_QUERY_VERSION ?= 1.62.0
 TEMPO_QUERY_VERSION ?= 2.6.1
diff --git a/bundle/community/manifests/tempo-operator.clusterserviceversion.yaml b/bundle/community/manifests/tempo-operator.clusterserviceversion.yaml
index a759d4db2..ed99cc042 100644
--- a/bundle/community/manifests/tempo-operator.clusterserviceversion.yaml
+++ b/bundle/community/manifests/tempo-operator.clusterserviceversion.yaml
@@ -73,8 +73,8 @@ metadata:
       ]
     capabilities: Deep Insights
     categories: Logging & Tracing,Monitoring
-    containerImage: ghcr.io/grafana/tempo-operator/tempo-operator:v0.13.0
-    createdAt: "2024-10-16T08:06:57Z"
+    containerImage: ghcr.io/grafana/tempo-operator/tempo-operator:v0.14.0
+    createdAt: "2024-10-30T12:08:06Z"
     description: Create and manage deployments of Tempo, a high-scale distributed
       tracing backend.
     operatorframework.io/cluster-monitoring: "true"
@@ -83,7 +83,7 @@ metadata:
     operators.operatorframework.io/project_layout: go.kubebuilder.io/v3
     repository: https://github.com/grafana/tempo-operator
     support: Grafana Tempo Operator SIG
-  name: tempo-operator.v0.13.0
+  name: tempo-operator.v0.14.0
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
@@ -1475,7 +1475,7 @@ spec:
                   value: quay.io/observatorium/opa-openshift:main-2024-10-09-7237863
                 - name: RELATED_IMAGE_OAUTH_PROXY
                   value: quay.io/openshift/origin-oauth-proxy:4.14
-                image: ghcr.io/grafana/tempo-operator/tempo-operator:v0.13.0
+                image: ghcr.io/grafana/tempo-operator/tempo-operator:v0.14.0
                 livenessProbe:
                   httpGet:
                     path: /healthz
@@ -1625,7 +1625,7 @@ spec:
     name: tempo-gateway-opa
   - image: quay.io/openshift/origin-oauth-proxy:4.14
     name: oauth-proxy
-  version: 0.13.0
+  version: 0.14.0
   webhookdefinitions:
   - admissionReviewVersions:
     - v1
diff --git a/bundle/openshift/manifests/tempo-operator.clusterserviceversion.yaml b/bundle/openshift/manifests/tempo-operator.clusterserviceversion.yaml
index ff9c1a100..20a0dc3fd 100644
--- a/bundle/openshift/manifests/tempo-operator.clusterserviceversion.yaml
+++ b/bundle/openshift/manifests/tempo-operator.clusterserviceversion.yaml
@@ -73,8 +73,8 @@ metadata:
       ]
     capabilities: Deep Insights
     categories: Logging & Tracing,Monitoring
-    containerImage: ghcr.io/grafana/tempo-operator/tempo-operator:v0.13.0
-    createdAt: "2024-10-12T18:04:06Z"
+    containerImage: ghcr.io/grafana/tempo-operator/tempo-operator:v0.14.0
+    createdAt: "2024-10-30T12:08:04Z"
     description: Create and manage deployments of Tempo, a high-scale distributed
       tracing backend.
     operatorframework.io/cluster-monitoring: "true"
@@ -83,7 +83,7 @@ metadata:
     operators.operatorframework.io/project_layout: go.kubebuilder.io/v3
     repository: https://github.com/grafana/tempo-operator
     support: Grafana Tempo Operator SIG
-  name: tempo-operator.v0.13.0
+  name: tempo-operator.v0.14.0
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
@@ -1485,7 +1485,7 @@ spec:
                   value: quay.io/observatorium/opa-openshift:main-2024-10-09-7237863
                 - name: RELATED_IMAGE_OAUTH_PROXY
                   value: quay.io/openshift/origin-oauth-proxy:4.14
-                image: ghcr.io/grafana/tempo-operator/tempo-operator:v0.13.0
+                image: ghcr.io/grafana/tempo-operator/tempo-operator:v0.14.0
                 livenessProbe:
                   httpGet:
                     path: /healthz
@@ -1646,7 +1646,7 @@ spec:
     name: tempo-gateway-opa
   - image: quay.io/openshift/origin-oauth-proxy:4.14
     name: oauth-proxy
-  version: 0.13.0
+  version: 0.14.0
   webhookdefinitions:
   - admissionReviewVersions:
     - v1
diff --git a/config/manager/kustomization.yaml b/config/manager/kustomization.yaml
index d91a4b8a1..220bacf10 100644
--- a/config/manager/kustomization.yaml
+++ b/config/manager/kustomization.yaml
@@ -9,4 +9,4 @@ kind: Kustomization
 images:
 - name: controller
   newName: ghcr.io/grafana/tempo-operator/tempo-operator
-  newTag: v0.13.0
+  newTag: v0.14.0
diff --git a/config/manifests/community/bases/tempo-operator.clusterserviceversion.yaml b/config/manifests/community/bases/tempo-operator.clusterserviceversion.yaml
index c0f246a74..5a934c3c8 100644
--- a/config/manifests/community/bases/tempo-operator.clusterserviceversion.yaml
+++ b/config/manifests/community/bases/tempo-operator.clusterserviceversion.yaml
@@ -5,7 +5,7 @@ metadata:
     alm-examples: '[]'
     capabilities: Deep Insights
     categories: Logging & Tracing,Monitoring
-    containerImage: ghcr.io/grafana/tempo-operator/tempo-operator:v0.13.0
+    containerImage: ghcr.io/grafana/tempo-operator/tempo-operator:v0.14.0
     description: Create and manage deployments of Tempo, a high-scale distributed
       tracing backend.
     operatorframework.io/cluster-monitoring: "true"
diff --git a/config/manifests/openshift/bases/tempo-operator.clusterserviceversion.yaml b/config/manifests/openshift/bases/tempo-operator.clusterserviceversion.yaml
index 3215680de..7e6fad297 100644
--- a/config/manifests/openshift/bases/tempo-operator.clusterserviceversion.yaml
+++ b/config/manifests/openshift/bases/tempo-operator.clusterserviceversion.yaml
@@ -5,7 +5,7 @@ metadata:
     alm-examples: '[]'
     capabilities: Deep Insights
     categories: Logging & Tracing,Monitoring
-    containerImage: ghcr.io/grafana/tempo-operator/tempo-operator:v0.13.0
+    containerImage: ghcr.io/grafana/tempo-operator/tempo-operator:v0.14.0
     description: Create and manage deployments of Tempo, a high-scale distributed
       tracing backend.
     operatorframework.io/cluster-monitoring: "true"