Skip to content
This repository was archived by the owner on Jan 16, 2026. It is now read-only.
This repository was archived by the owner on Jan 16, 2026. It is now read-only.

Wavefront-Proxy service with non ClusterIP type #129

@vavdoshka

Description

@vavdoshka

We want to leverage Wavefront-Proxy in K8s to accept and process the metrics from non-K8s cluster origin, which would require the Proxy Service to be the type of LoadBalancer. Which is currently not possible:

In addition to this, we would want to have only one proxy Deployment per cluster and use it for both internal K8s metrics traffic and the traffic with different origins external to the K8s cluster. So that means we would need to have two services with different types, one ClusterIP for internal traffic (as is the case now) and one with LoadBalancer type to handle external traffic.

So to sum up I propose to:

  • add the possibility to define (enable) an extra service object for Wavefront Proxy with type LoadBalancer.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions