Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wavefront-Proxy service with non ClusterIP type #129

Open
vavdoshka opened this issue Dec 7, 2021 · 1 comment
Open

Wavefront-Proxy service with non ClusterIP type #129

vavdoshka opened this issue Dec 7, 2021 · 1 comment

Comments

@vavdoshka
Copy link
Contributor

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.
@helen-shao
Copy link
Contributor

This issue is tracked with K8SSAAS-1079.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants