![]() First, create a custom config for kubernetes-dashboard helm chart: cat > values-dashboard.yaml kubernetes-dashboard-role.yaml kubernetes-dashboard-rolebinding.yaml<<EOFĪpiVersion: /v1beta1 So, let's say you want to install it in the default namespace. ![]() Installing the dashboard is a pretty straightforward process. ![]() Kubernetes Dashboard does have namespace support. Or even more, make it read-only and disable access to some sensitive info, like secrets. But, you probably want to limit users for touching anything that is not part of their namespace. On top of that, all secrets are explicitly created, and ServiceAccount doesn't have permission to create any secret. The latest version of Kubernetes dashboard v2.0 is running without a cluster-admin role, which was too dangerous. Let's see how to install and configure it for this scenario. Kubernetes Dashboard is easy to install, but you might want to have it per namespace and to limit what users can do. If you are interacting with it daily or managing the cluster itself, you are probably more fine with CLI, aka kubectl. Even though I'm not Kubernetes Dashboard user, I understand why it is the easiest way for most people to interact with their apps running on top of Kubernetes.
0 Comments
Leave a Reply. |