fix: bump cactus parser chart version and disable OTel metric pushing by default

charts/cactus-backend/Chart.yaml

@@ -2,7 +2,7 @@ apiVersion: v2
 name: cactus-backend
 description: A backend that exposes an API for the Cactus app to use.
 type: application
-version: 0.5.10
+version: 0.5.11
 appVersion: "0.2"
 maintainers:
   - name: dataviruset
@@ -25,7 +25,7 @@ dependencies:
   repository: https://juicedata.github.io/charts/
   condition: juicefs-s3-gateway.enabled
 - name: cactus-parser
-  version: 0.0.3
+  version: 0.0.5
   repository: https://charts.lookingglassprotocol.com
   condition: cactus-parser.enabled
 - name: opentelemetry-collector

charts/cactus-backend/README.md

@@ -63,7 +63,7 @@ To upgrade your deployment:
 helm upgrade cactus-backend matterless/cactus-backend
 ```
 
-**Important:**  
+**Important:**
 Before upgrading from chart version please review the following steps:
 
 1. **Review the [values.yaml](./values.yaml) file** for any new, deprecated, or changed configuration options.
@@ -128,6 +128,12 @@ Version 0.5.0 introduces significant changes to the feature set of the Cactus Ba
   * For Prometheus integration, enable `podMonitor` and the `prometheus` port, and see the [Spanmetrics Connector for Prometheus](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/connector/spanmetricsconnector).
   * For additional configuration details, consult the [OpenTelemetry Collector documentation](https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-collector).
 
+### Upgrading to 0.5.11
+
+#### Fixes
+
+* OpenTelemetry integration is now disabled by default. To enable telemetry for both the Cactus Backend and Cactus Parser, set `cactus-backend.envVars.OTEL_ENABLED` and `cactus-backend.cactus-parser.envVars.OTEL_ENABLED` to `true` in your configuration. If you would like to use the OpenTelemetry sub-chart it can be enabled by setting `opentelemetry-collector.enable` to true just like before.
+
 ## Chart Structure
 
 - `Chart.yaml` - Chart metadata

charts/cactus-backend/values.yaml

@@ -340,6 +340,7 @@ envVars:
 
   # APP_KEY: cactus-backend  # This is the app key used together with the app secret (defined in the secretData above or by using existingSecret) to access Auki services. You should obtain it from the apps section of the Auki console.
   OTEL_COLLECTOR_GRPC_ENDPOINT: http://cactus-backend-opentelemetry-collector:4317  # The grpc endpoint for the opentelemetry collector, it should be Release.name-opentelemetry-collector:4317.
+  OTEL_ENABLED: false
 ## Autoscaling configuration
 ## ref: https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/
 autoscaling:
@@ -392,6 +393,7 @@ cactus-parser:
     enabled: false
   envVars:
     OTEL_COLLECTOR_GRPC_ENDPOINT: http://cactus-backend-opentelemetry-collector:4317  # The grpc endpoint for the opentelemetry collector, it should be Release.name-opentelemetry-collector:4317.
+    OTEL_ENABLED: false
 opentelemetry-collector:
   enabled: false
   mode: deployment

charts/cactus-parser/Chart.yaml

@@ -2,7 +2,7 @@ apiVersion: v2
 name: cactus-parser
 description: Used to deploy parsers that load product data from a source when requested from cactus-backend
 type: application
-version: 0.0.5
+version: 0.0.6
 appVersion: "0.0"
 maintainers:
   - name: dataviruset

charts/cactus-parser/values.yaml

@@ -282,6 +282,7 @@ envVars:
   S3_PATH_PREFIX: cactus-parser  # The path prefix for the S3 bucket. This cannot be empty when blob storage type is s3.
 
   OTEL_COLLECTOR_GRPC_ENDPOINT: http://cactus-parser-opentelemetry-collector:4317  # The grpc endpoint for the opentelemetry collector, it should be Release.name-opentelemetry-collector:4317.
+  OTEL_ENABLED: false
 ## Autoscaling configuration
 ## ref: https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/
 autoscaling: