build(deps): bump github.com/grafana/tempo-operator from 0.18.0 to 0.20.0

[dependabot]

Bumps github.com/grafana/tempo-operator from 0.18.0 to 0.20.0.

Release notes

Sourced from github.com/grafana/tempo-operator's releases.

Release v0.20.0

🛑 Breaking changes 🛑

• operator: Migrate operator configuration from ConfigMap to environment variables (#1348) The default operator deployment no longer uses a ConfigMap-based configuration file. Configuration is now managed through environment variables.

  To continue using a ConfigMap: Mount your controller_manager_config.yaml ConfigMap and add the --config=/path/to/config.yaml flag to the operator deployment args. Environment variables will still take precedence over the config file.

  To migrate to environment variables: Use FEATURE_GATES for boolean flags (comma-separated, prefix with - to disable) and individual env vars for other settings.

  Example OLM Subscription override:

  spec:
    config:
      env:
      - name: FEATURE_GATES
        value: "prometheusOperator,observability.metrics.createServiceMonitors,-networkPolicies"
      - name: TLS_PROFILE
        value: "Intermediate"

  Available feature gates: openshift.route, openshift.servingCertsService, openshift.oauthProxy, httpEncryption, grpcEncryption, prometheusOperator, grafanaOperator, builtInCertManagement, observability.metrics.createServiceMonitors, observability.metrics.createPrometheusRules, networkPolicies

  Other env vars: DISTRIBUTION, TLS_PROFILE, OPENSHIFT_BASE_DOMAIN, DEFAULT_POD_SECURITY_CONTEXT (JSON), BUILT_IN_CERT_MANAGEMENT_CA_VALIDITY, BUILT_IN_CERT_MANAGEMENT_CA_REFRESH, BUILT_IN_CERT_MANAGEMENT_CERT_VALIDITY, BUILT_IN_CERT_MANAGEMENT_CERT_REFRESH

💡 Enhancements 💡

• tempostack, tempomonolithic: Add configurable defaultPodSecurityContext to operator config (#1240) The operator now supports a configurable defaultPodSecurityContext in the operator configuration. This allows setting default pod security context fields (fsGroup, runAsUser, etc.) that are merged into pod security contexts when specific fields are not set by the user. For Community distributions, fsGroup is set to 10001 to ensure volume permissions work correctly with certain CSI drivers (AWS EBS, DigitalOcean, etc.) that mount volumes with root:root ownership. For OpenShift, this is set to an empty object {} as SCCs manage security contexts automatically.

• tempostack, tempomonolithic: Add MCP (Model Context Protocol) server configuration to TempoStack and TempoMonolithic CRDs (#1319) The MCP server allows AI assistants to query tracing data from Tempo. Enable it by setting spec.template.queryFrontend.mcpServer.enabled: true for TempoStack or spec.query.mcpServer.enabled: true for TempoMonolithic.

... (truncated)

Changelog

Sourced from github.com/grafana/tempo-operator's changelog.

0.20.0

🛑 Breaking changes 🛑

• operator: Migrate operator configuration from ConfigMap to environment variables (#1348) The default operator deployment no longer uses a ConfigMap-based configuration file. Configuration is now managed through environment variables.

  To continue using a ConfigMap: Mount your controller_manager_config.yaml ConfigMap and add the --config=/path/to/config.yaml flag to the operator deployment args. Environment variables will still take precedence over the config file.

  To migrate to environment variables: Use FEATURE_GATES for boolean flags (comma-separated, prefix with - to disable) and individual env vars for other settings.

  Example OLM Subscription override:

  spec:
    config:
      env:
      - name: FEATURE_GATES
        value: "prometheusOperator,observability.metrics.createServiceMonitors,-networkPolicies"
      - name: TLS_PROFILE
        value: "Intermediate"

  Available feature gates: openshift.route, openshift.servingCertsService, openshift.oauthProxy, httpEncryption, grpcEncryption, prometheusOperator, grafanaOperator, builtInCertManagement, observability.metrics.createServiceMonitors, observability.metrics.createPrometheusRules, networkPolicies

  Other env vars: DISTRIBUTION, TLS_PROFILE, OPENSHIFT_BASE_DOMAIN, DEFAULT_POD_SECURITY_CONTEXT (JSON), BUILT_IN_CERT_MANAGEMENT_CA_VALIDITY, BUILT_IN_CERT_MANAGEMENT_CA_REFRESH, BUILT_IN_CERT_MANAGEMENT_CERT_VALIDITY, BUILT_IN_CERT_MANAGEMENT_CERT_REFRESH

💡 Enhancements 💡

• tempostack, tempomonolithic: Add configurable defaultPodSecurityContext to operator config (#1240) The operator now supports a configurable defaultPodSecurityContext in the operator configuration. This allows setting default pod security context fields (fsGroup, runAsUser, etc.) that are merged into pod security contexts when specific fields are not set by the user. For Community distributions, fsGroup is set to 10001 to ensure volume permissions work correctly with certain CSI drivers (AWS EBS, DigitalOcean, etc.) that mount volumes with root:root ownership. For OpenShift, this is set to an empty object {} as SCCs manage security contexts automatically.

• tempostack, tempomonolithic: Add MCP (Model Context Protocol) server configuration to TempoStack and TempoMonolithic CRDs (#1319) The MCP server allows AI assistants to query tracing data from Tempo. Enable it by setting spec.template.queryFrontend.mcpServer.enabled: true for TempoStack or spec.query.mcpServer.enabled: true for TempoMonolithic.

... (truncated)

Commits

• fd473ff Prepare Release 0.20.0 (#1379)
• a3a8a14 chore(deps): update alpine docker tag to v3.23 (#1333)
• abb7589 fix(deps): update k8s.io/utils digest to 914a6e7 (#1358)
• 5d8e1a8 Bump github/codeql-action from 4.32.0 to 4.32.2 (#1368)
• 50eeac4 Bump docker/build-push-action from 6.18.0 to 6.19.1 (#1374)
• 458fa6d Update to Tempo 2.10.0 (#1375)
• da1f726 [Chore] Fix network policy deletion when disabled and Jaeger UI access (#1364)
• 5dc9f39 Test operator configuration using env vars (#1366)
• c867c56 fix: monolithic: use gateway serving cert for ingestion if gateway is enabled...
• 8504e05 fix: get cp address from k8s service endpoints (#1373)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign marioferh for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a rhobs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[danielmellado]

/ok-to-test

[openshift-ci]

@dependabot[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/observability-operator-e2e	cf217ed	link	true	/test observability-operator-e2e

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.