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

Allow to relocate dashboard and heapster out of kube-system #2655

Closed
farcaller opened this issue Dec 8, 2017 · 2 comments
Closed

Allow to relocate dashboard and heapster out of kube-system #2655

farcaller opened this issue Dec 8, 2017 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@farcaller
Copy link
Contributor

Dashboard version: 1.8
Kubernetes version: 1.8.5

Currently the dashboard has a few places where kube-system namespace is hardcoded, which makes simple namespacing of the dashboard very troublesome.

This creates issues with pods isolation. kube-system has all the pods that are required for cluster health, while the dashboard itself isn't on the critical path. It makes it very hard to isolate some components, e.g. if one were to use a NetworkPolicy to only allow heapster to talk to influxdb they might cause a cluster-level disruption as presence of a NetworkPolicy in kube-system will block dns traffic too.

It should be easier to extract the dashboard and relevant components (heapster and influxdb) to a dedicated namespace to manage the access to them granularly. I include heapster in here as its only consumer in my setup is the dashboard, prometheus does the "real" monitoring instead.

@maciaszczykm
Copy link
Member

It is partly finished. Last adjustments will be done in #3495.

/close

@k8s-ci-robot
Copy link
Contributor

@maciaszczykm: Closing this issue.

In response to this:

It is partly finished. Last adjustments will be done in #3495.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

4 participants