You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:helm/wavefront/templates/proxy-service.yaml
Line 65 in 85f8f35
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 withLoadBalancer
type to handle external traffic.So to sum up I propose to:
The text was updated successfully, but these errors were encountered: