Re:Privilege escalation through Kubernetes dashboard
by andrewstuart2 on Friday January 11, 2019 @12:59AM
(#18881330)
Either don't expose the dashboard, or explicitly give it a service account with zero access. I think it should be well-known by now that anything you run in-cluster gets a builtin service account token, defaulting to the default service account for that namespace.
[ Parent
| on HN ]
Re:Privilege escalation through Kubernetes dashboard
by sieabahlpark on Friday January 11, 2019 @01:32AM
(#18881448)
You'd be surprised a lot of things are overlooked with the premise of shipping faster.
Don't worry about security, we need to ship.
Re:Privilege escalation through Kubernetes dashboard
by GauntletWizard on Friday January 11, 2019 @01:37AM
(#18881462)
I ran my k8s dashboard behind a ClusterIP service - You could get to it through the kube-proxy, but you already had to be auth'd to the cluster, first. This was fine for a cluster small enough that any user already had admin, though we did worry a little bit that someone would compromise a pod, scan for a bit, and escalate through the dashboard.