Skip to content

/ kubo-release

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

Jump to bottom

InfluxDB is exposed via NodePort, but it should not #138

Closed
alex-slynko opened this issue Nov 27, 2017 · 2 comments
Closed

InfluxDB is exposed via NodePort, but it should not #138

alex-slynko opened this issue Nov 27, 2017 · 2 comments
Labels
accepted

Comments

@alex-slynko
Copy link
Member

@alex-slynko alex-slynko commented Nov 27, 2017

InfluxDB is used only by Kubernetes dashboard and is exposed via NodePort for some reason.
Community spec uses unexposed InfluxDB https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/cluster-monitoring/influxdb/influxdb-service.yaml
@cf-gitbot
Copy link

@cf-gitbot cf-gitbot commented Nov 27, 2017

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/153172804

The labels on this github issue will be updated when the story is started.
tvs added a commit that referenced this issue Dec 1, 2017
@tvs
Remove NodePort from Influxdb since it is only used internally
abe83b8 
Issue #138

[#153172804]
@glestaris
Copy link

@glestaris glestaris commented Dec 1, 2017

@tvs seemed to have addressed the issue. Closing this.
@glestaris glestaris closed this Dec 1, 2017
@cf-gitbot cf-gitbot added accepted and removed delivered labels Dec 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
accepted
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
@glestaris @alex-slynko @cf-gitbot
You can’t perform that action at this time.