No option to create Ingress that points to 2 different ports in the Service

[keoren3]

I wanted to pass the traces through port 14317 (And 14317 in the backend), while still having the UI available in port 443 (And 14318 in the backend).

I couldn't find any way to do it since the backend-port is attached directly to the HTTP port for the service:
{{- $svcPort := .Values.service.http_port -}}

Am I missing anything?

If I'm not missing anything, I'll create a fix for this (Enable to override the svc port)

[vmihailenco]

Uptrace has 2 ports: 14317 for OTLP/gRPC and 14318 for OTLP/HTTP & UI. You can change those 2 ports, but you can't have a 3rd port just for the UI.

Does that help?

[keoren3]

I want both ports to be enabled.
So that the Ingress will have 2 backends for the same URL (With different ports) for example:
uptrace.example.com:443 -> uptrace:14318
uptrace.example.com:14317 -> uptrace:14317

Is there a way to do it?

[vmihailenco]

I guess we're speaking about different things. Let's look at your fix so I can understand better.

uptrace.example.com:443 -> uptrace:14318
uptrace.example.com:14317 -> uptrace:14317

Well, this is just proxying with port re-mapping so it should be possible in principle. But I am not sure if this chart allows that :)

[keoren3]

I'll create a PR ASAP, and we can talk about it

[keoren3]

So I've created a change, but I'm not able to push my branch.
I looked at the contributing guide lines but nothing regarding Git is mentioned there.

[vmihailenco]

@keoren3 you're supposed to fork the repo and push your branch there: see GitHub documentation.

[RouR]

I guess we're speaking about different things. Let's look at your fix so I can understand better.

uptrace.example.com:443 -> uptrace:14318
uptrace.example.com:14317 -> uptrace:14317

Well, this is just proxying with port re-mapping so it should be possible in principle. But I am not sure if this chart allows that :)

same issue