Resolve "Tempo storage-subnet netpol not enabled in some cases"

General MR

Summary

• Addressed bug where providing tempo.objectStorage values does not result in creating an egress network policy from temp to external storage-subnets.

Relevant logs/screenshots

Used the following values to validate:

tempo:
  objectStorage:
    endpoint: "s3.us-gov-west-555.amazonaws.com"
    region: "us-gov-west-555"
    bucket: "my-external-objectstore-for-tempo"

Also verified the original mechanism still works on its own and when both are set

Used the following values to validate original way:

tempo:
  values:
    upstream:
      tempo:
        storage:
          trace:
            backend: "local"

Linked Issue

issue

Upgrade Notices

N/A