Cannot enable gateway while disabling jaeger ui

[philipgough]

The following snippet fails for me

      tenants:
        mode: openshift
        authentication:
          - tenantName: application
            tenantId: application
      template:
        gateway:
          enabled: true
        queryFrontend:
          jaegerQuery:
            enabled: false

Error: The TempoStack "tempostack" is invalid: spec.template.gateway.enabled: Invalid value: true: to use the gateway, please enable jaegerQuery

Probably misunderstanding something but the use case is to continue to leverage authn/authz at the gateway without the need for jaeger on the query path (I want the gateway read/write tracing endpoints to point at the Loki components/services) in such a case.

[frzifus]

I think is currently not supported since the read path is always referring to the query service.

tempo-operator/internal/manifests/gateway/gateway.go

Lines 164 to 175 in a701112

	Args: append([]string{
	fmt.Sprintf("--traces.tenant-header=%s", manifestutils.TenantHeader),
	fmt.Sprintf("--web.listen=0.0.0.0:%d", portPublic),
	fmt.Sprintf("--web.internal.listen=0.0.0.0:%d", portInternal),
	fmt.Sprintf("--traces.write.endpoint=%s:4317", naming.ServiceFqdn(tempo.Namespace, tempo.Name, manifestutils.DistributorComponentName)),
	fmt.Sprintf("--traces.read.endpoint=%s://%s:16686", httpScheme(params.Gates.HTTPEncryption),
	naming.ServiceFqdn(tempo.Namespace, tempo.Name, manifestutils.QueryFrontendComponentName)),
	fmt.Sprintf("--grpc.listen=0.0.0.0:%d", portGRPC),
	fmt.Sprintf("--rbac.config=%s", path.Join(tempoGatewayMountDir, "cm", tempoGatewayRbacFileName)),
	fmt.Sprintf("--tenants.config=%s", path.Join(tempoGatewayMountDir, "secret", manifestutils.GatewayTenantFileName)),
	"--log.level=info",
	}, tlsArgs...),

But I assume it could be supported. wdyt @andreasgerstmayr ?

[andreasgerstmayr]

This validation was added in #278.
I'm a bit confused, where should traces.read.endpoint point to if tempo-query (Jaeger UI) is disabled?

[pavolloffay]

@rubenvp8510 is adding support for exposing Tempo native API in the gateway observatorium/api#575

[andreasgerstmayr]

Ah, yes, so in that case we don't support the Jaeger-API compatible endpoints (traces.read.endpoint) but only the Tempo API endpoints (traces.tempo.endpoint). Makes sense.

[philipgough]

Yes so basically I was trying to run this with a custom built gateway. Sounds like it is all coming together already :)