[bitnami/thanos] Receive component with different ingresses

[Spuxy]

Name and Version

bitnami/thanos: 15.14.1

What is the problem this feature will solve?

Creating separate ingress for:

• grpc
• http

People can define annotations specifically for different ingresses (eg. in my case i use nginx-ingress controller).
For example, this annotation https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#backend-protocol can be applied for two different ingresses

What is the feature you are proposing to solve the problem?

Like thanos-query has ingress (http) and ingress (grpc)

• https://artifacthub.io/packages/helm/bitnami/thanos?modal=template&template=query/ingress-grpc.yaml
• https://artifacthub.io/packages/helm/bitnami/thanos?modal=template&template=query/ingress.yaml

This solution with seprated ingresses (i dont know if anything else will be needed) will solve the problem.

What alternatives have you considered?

Created different values.yml to create/generate one service.
So i would have two values.yml, one with all configurations for all thanos components and one for one concrete manifest

[javsalgar]

Hi!

Thank you so much for reporting. I will forward it to the team but as it is not a critical feature we cannot guarantee an ETA. If you want to speed up the process, you can submit a PR and the team will check it.

[Spuxy]

More context, we need to expose one ingress in this case grpc to outside of the cluster for remote write.