Difference between revisions of "Kubernetes Dashboard Installation"
Jump to navigation
Jump to search
(Created page with "===Create the Kubernetes Dashboard=== To avoid running the Dashboard on worker nodes, the following command needs to be launched before any worker nodes joining the cluster: (...") |
|||
| Line 1: | Line 1: | ||
=== | ===Kubernetes Dashboard deployed on Master Node=== | ||
To avoid running the Dashboard on worker nodes, the following command needs to be launched before any worker nodes joining the cluster: ('''It is important to note that the hyperlink in the [[Installing Kubernetes#Kubernetes on Ubuntu by Edureka|original video]] is not working, the following instruction has been tested as of July 21, 2021''') | To avoid running the Dashboard on worker nodes, the following command needs to be launched before any worker nodes joining the cluster: ('''It is important to note that the hyperlink in the [[Installing Kubernetes#Kubernetes on Ubuntu by Edureka|original video]] is not working, the following instruction has been tested as of July 21, 2021''') | ||
kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.2.0/aio/deploy/recommended.yaml | kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.2.0/aio/deploy/recommended.yaml | ||
Revision as of 04:12, 22 July 2021
Kubernetes Dashboard deployed on Master Node
To avoid running the Dashboard on worker nodes, the following command needs to be launched before any worker nodes joining the cluster: (It is important to note that the hyperlink in the original video is not working, the following instruction has been tested as of July 21, 2021)
kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.2.0/aio/deploy/recommended.yaml
A service account must be created to make dashboard available
kubectl create serviceaccount dashboard -n default
Then, it needs to create the dashboard-admin
kubectl create clusterrolebinding dashboard-admin -n default --clusterrole=cluster-admin --serviceaccount=default:dashboard
Then, one needs to get the secret key to be pasted into the web-based interface of Kubernetes Dashboard.
kubectl get secret $(kubectl get serviceaccount dashboard -o jsonpath="{.secrets[0].name}") -o jsonpath="{.data.token}" | base64 --decode
This will generate a long token string, something like this:
eyJhbGciOiJSUzI1NiIsImtpZCI6IjRPcEhLUU54QXE1R1dSdnhsZmdMaUxMN0NMdk8wZ1ZEUjhUMVFLZkdVaEkifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJkZWZhdWx0Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZWNyZXQubmFtZSI6ImRhc2hib2FyZC10b2tlbi1wd3FwNSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJkYXNoYm9hcmQiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC51aWQiOiJhOGRkMDE0OC1jNDQzLTRkODctYTVjOC01MjJmYmRjZGMxMGQiLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6ZGVmYXVsdDpkYXNoYm9hcmQifQ.jbjvJgnLCMhsWbdg_7A83PJZ3sLskS9MPTFEZGvUr8eC-I0tosPXgMBkiWgoAgPcFNpYjXWRN3Ia66vYTEHAc0kqSDsZAMbUP48pszBQR0InPk_7tt7kQn3Scx6FEhkRbxVXaiVqYaafxLdOQlbAP_Xz9KOTjq2L-RU0Pxf83FsAITpJbTVmX7oz_trZSEeP1knqjnnKKn3ppYoYWpAwD-FDDXlPwqvHidxLA-Db9rbxkVGSI2yAibtW6mgldStEC9uv64zBpleUVMIw7ys6a9LxuHuVNg29oZrWaIL7qi6rvvQIqvzcneRRUSC2E7pV-Jl7x80leyRL8SRUiKhBsg
To allow access to this dashboard, the following command must be run:
kubectl proxy