You recommend RBAC but then state that the k8s-dash starts with full permissions. That's not true at all when using RBAC. You need to define which namespaces, resources, etc get accessed. Right now with k8s if you deploy RBAC + k8s-dash (which is basically deprecated anyway) and don't set up its RBAC svc account you won't be able to view things in k8s without putting in your personal admin token because it would use the default service account which has no/very limited permissions.
Definitely suggest adding more RBAC examples to this. And things like ETCD w/SSL, etc.
If k8s-dash is deprecated, what's the replacement?
kubernetes dashboard[0] is still very much alive afaik.
Some providers / distros may have deprecated it, but the community hasn't.