feature requestDeveloper Tools · DevOps & InfrastructurestructuralOpen SourceGithubFeature Request

Support Gateway API in Tempo Helm chart

Feature request to add Gateway API HTTPRoute support in the Grafana Tempo Helm chart for Kubernetes.

1mentions
1sources
3.25

Signal

Visibility

Sign in free to unlock the full scoring breakdown, root-cause analysis, and solution blueprint.

Sign up free

Already have an account? Sign in

Deep Analysis

Root causes, cross-domain patterns, and opportunity mapping

Sign up free to read the full analysis — no credit card required.

Already have an account? Sign in

Solution Blueprint

Tech stack, MVP scope, go-to-market strategy, and competitive landscape

Sign up free to read the full analysis — no credit card required.

Already have an account? Sign in

Similar Problems

surfaced semantically
Developer Tools74% match

Inference gateway lacks hostname and TLS configuration

A Kubernetes-based model-serving control plane exposes each inference gateway only as an ephemeral IP over plain HTTP, with no way to assign a stable hostname or terminate TLS. This makes it awkward to put the gateway behind DNS or in front of real production clients, undermining its role as a single front door to the model fleet.

Developer Tools73% match

Helm chart cant update index mappings after creation

Helm chart cannot update index document mappings once created; must use PUT API directly with overwrite flag.

Developer Tools72% match

MetalLB Helm Chart Cannot Disable hostNetwork for Speakers

MetalLB Helm chart hardcodes hostNetwork: true for speaker pods with no way to override it in values.yaml.

Data & Infrastructure71% match

Reverse Proxies Lack Per-Service TLS Toggle for Self-Hosted Apps

Self-hosters running internal services like Proxmox or Kasm need to skip TLS verification on a per-service basis when using self-signed certificates on a LAN. Current reverse proxy tooling requires global static configuration, forcing users to choose between a blanket insecure setting or manual static file edits for each service.

Developer Tools70% match

Grafana License Changes Force Migration to Open-Source Dashboards

Grafana license changes to AGPL create compatibility concerns for projects distributing example monitoring dashboards. Teams need to migrate dashboard definitions to open-source alternatives like Perses to avoid licensing restrictions.

Problem descriptions, scores, analysis, and solution blueprints may be updated as new community data becomes available.