-
Notifications
You must be signed in to change notification settings - Fork 193
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
Investigate exporting Submariner metrics without needing to open ports #1944
Comments
Note: Currently we open the Metrics port (TCP/8080 and TCP/8081) only within the local cluster and not to the outside world. Using NodePort might solve the issue, but it can open the corresponding port globally which may not be what we want. |
Submariner Gateway and Globalnet metrics require port to be opened on host for them to be accessible. This EP proposes a redesign which allows metrics to be accessible without requiring to open any ports in infra. Fixes github.com/submariner-io/submariner/issues/1944 Signed-off-by: Vishal Thapar <[email protected]>
Submariner Gateway and Globalnet metrics require port to be opened on host for them to be accessible. This EP proposes a redesign which allows metrics to be accessible without requiring to open any ports in infra. Fixes github.com/submariner-io/submariner/issues/1944 Signed-off-by: Vishal Thapar <[email protected]>
Submariner Gateway and Globalnet metrics require port to be opened on host for them to be accessible. This EP proposes a redesign which allows metrics to be accessible without requiring to open any ports in infra. Fixes github.com/submariner-io/submariner/issues/1944 Signed-off-by: Vishal Thapar <[email protected]>
Submariner Gateway and Globalnet metrics require port to be opened on host for them to be accessible. This EP proposes a redesign which allows metrics to be accessible without requiring to open any ports in infra. Fixes github.com/submariner-io/submariner/issues/1944 Signed-off-by: Vishal Thapar <[email protected]>
Submariner Gateway and Globalnet metrics require port to be opened on host for them to be accessible. This EP proposes a redesign which allows metrics to be accessible without requiring to open any ports in infra. Refer github.com/submariner-io/submariner/issues/1944 Signed-off-by: Vishal Thapar <[email protected]>
Submariner Gateway and Globalnet metrics require port to be opened on host for them to be accessible. This EP proposes a redesign which allows metrics to be accessible without requiring to open any ports in infra. Refer github.com/submariner-io/submariner/issues/1944 Signed-off-by: Vishal Thapar <[email protected]>
I think we can close it. This is fixed by: submariner-io/submariner-operator#2182 @vthapar can you please make sure we track any docs changes (actual docs and release notes) separately? |
Currently we need to open ports to access some Submariner metrics (at least those exported on a port on the host network).
We should look into some other way of exporting the metrics which doesn’t require this. One possible idea is to use
NodePort
.Work Items
The text was updated successfully, but these errors were encountered: