-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
False
-
None
-
False
-
-
Hi team,
I tested tempo-operator.v0.13.0-1 with OD by enabling :
- servingCertsService (the feature flag)
- tls with caName (set explicitly to openshift-service-ca.crt) or not
So, tempo-operator will fail by creating invalid deployment manifest for the distributor !
apiVersion: tempo.grafana.com/v1alpha1 kind: TempoStack metadata: name: tempo spec: extraConfig: tempo: memberlist: # # To workaroud because our cluster use non-private pod CIDR. # bind_addr: - \${MY_POD_IP} managementState: Managed storage: secret: # # Notice that's the name of the secret we created # name: s3 type: s3 tls: caName: openshift-service-ca.crt enabled: true storageSize: 10Gi template: distributor: tls: # # OpenShift feature flag servingCertsService is enabled and TLS is enabled # with caName or not, tempo-operator will faill by creating invalid deploy # for the distributor: # [ # spec.template.spec.volumes[5].secret.secretName: Required value, # spec.template.spec.volumes[5].name: Required value, # spec.template.spec.containers[0].volumeMounts[5].name: Required value, # spec.template.spec.containers[0].volumeMounts[5].name: Not found: "" # ] # enabled: true queryFrontend: jaegerQuery: enabled: true ingress: route: termination: edge type: route
For more information: https://redhat-internal.slack.com/archives/C013N9P9R6F/p1727719937262889?thread_ts=1727451795.582309&cid=C013N9P9R6F