Allow to relocate dashboard and heapster out of kube-system #2655
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.
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.
The text was updated successfully, but these errors were encountered: