Bird
Raised Fist0
Kubernetesdevops~5 mins

Kubernetes dashboard - Commands & Configuration

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Introduction
Managing many applications and resources in Kubernetes can be hard using only commands. The Kubernetes dashboard is a web interface that helps you see and control your cluster easily without typing many commands.
When you want to quickly check the status of your pods, deployments, and services visually.
When you need to troubleshoot issues by looking at logs and events in one place.
When you want to create or update Kubernetes resources without writing YAML files manually.
When you prefer a graphical interface to monitor resource usage like CPU and memory.
When you want to give team members a simple way to view and manage the cluster without deep command-line knowledge.
Commands
This command installs the Kubernetes dashboard by applying the official dashboard manifest to your cluster.
Terminal
kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml
Expected OutputExpected
namespace/kubernetes-dashboard created serviceaccount/kubernetes-dashboard created service/kubernetes-dashboard created secret/kubernetes-dashboard-certs created secret/kubernetes-dashboard-csrf created secret/kubernetes-dashboard-key-holder created configmap/kubernetes-dashboard-settings created role.rbac.authorization.k8s.io/kubernetes-dashboard created rolebinding.rbac.authorization.k8s.io/kubernetes-dashboard created deployment.apps/kubernetes-dashboard created service/dashboard-metrics-scraper created deployment.apps/dashboard-metrics-scraper created
This command starts a proxy to securely access the dashboard locally through your browser.
Terminal
kubectl proxy
Expected OutputExpected
Starting to serve on 127.0.0.1:8001
This command generates a login token for the dashboard to authenticate you securely.
Terminal
kubectl -n kubernetes-dashboard create token admin-user
Expected OutputExpected
eyJhbGciOiJSUzI1NiIsImtpZCI6IjYzYzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5YzY5In0.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlcm5ldGVzLWRhc2hib2FyZCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJhZG1pbi11c2VyLXRva2VuLXRzZCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvdXNlcm5hbWUiOiJhZG1pbi11c2VyIiwic3ViIjoiYWNjb3VudDprdWJlcm5ldGVzLWRhc2hib2FyZDphZG1pbi11c2VyIn0.XYZ1234567890abcdef
Open this URL in your browser to access the Kubernetes dashboard through the proxy.
Terminal
open http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/
Expected OutputExpected
No output (command runs silently)
Key Concept

If you remember nothing else from this pattern, remember: the Kubernetes dashboard gives you a simple web view to manage and monitor your cluster without complex commands.

Common Mistakes
Trying to access the dashboard URL directly without running 'kubectl proxy'.
The dashboard is not exposed publicly by default, so direct access is blocked for security.
Always run 'kubectl proxy' first to create a secure local tunnel to the dashboard.
Not creating or using a valid login token to sign in to the dashboard.
Without a token, you cannot authenticate and access the dashboard features.
Generate a token with 'kubectl -n kubernetes-dashboard create token admin-user' and use it to log in.
Applying an outdated or incorrect dashboard manifest URL.
This can cause installation failures or install an insecure or incompatible dashboard version.
Use the official and latest stable dashboard manifest URL from the Kubernetes GitHub repository.
Summary
Install the Kubernetes dashboard using the official manifest with 'kubectl apply'.
Start a local proxy with 'kubectl proxy' to securely access the dashboard in your browser.
Generate a login token to authenticate and use the dashboard safely.
Open the dashboard URL through the proxy to view and manage your cluster visually.

Practice

(1/5)
1. What is the primary purpose of the Kubernetes dashboard?
easy
A. To automatically scale pods based on CPU usage
B. To replace the kubectl command-line tool entirely
C. To serve as a container runtime for Kubernetes
D. To provide a web-based user interface for managing Kubernetes clusters

Solution

  1. Step 1: Understand the role of Kubernetes dashboard

    The dashboard is designed as a web UI to help users visually manage and monitor their Kubernetes clusters.

  2. Step 2: Compare with other Kubernetes components

    It does not replace kubectl, nor does it handle scaling or container runtime tasks.

  3. Final Answer:

    To provide a web-based user interface for managing Kubernetes clusters -> Option D

  4. Quick Check:

    Kubernetes dashboard = Web UI for cluster management [OK]
Hint: Dashboard = visual cluster management tool [OK]
Common Mistakes:
  • Thinking dashboard replaces kubectl
  • Confusing dashboard with autoscaling
  • Assuming dashboard is a container runtime
2. Which command correctly installs the Kubernetes dashboard?
easy
A. kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml
B. kubectl create dashboard
C. kubectl run dashboard --image=kubernetes/dashboard
D. kubectl install dashboard

Solution

  1. Step 1: Identify the installation method for the dashboard

    The official way to install the Kubernetes dashboard is by applying the recommended YAML manifest from the official GitHub repository.

  2. Step 2: Verify the command syntax

    kubectl apply -f [URL] is the correct syntax to apply a manifest file from a URL.

  3. Final Answer:

    kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml -> Option A

  4. Quick Check:

    Install dashboard = kubectl apply -f URL [OK]
Hint: Use kubectl apply with official dashboard YAML URL [OK]
Common Mistakes:
  • Using kubectl create instead of apply
  • Trying kubectl run which is for pods
  • Using non-existent kubectl install command
3. After running kubectl proxy, what URL should you open in your browser to access the Kubernetes dashboard?
medium
A. http://localhost:8080/dashboard
B. http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/
C. https://dashboard.kubernetes.local
D. http://127.0.0.1:6443/dashboard

Solution

  1. Step 1: Understand kubectl proxy behavior

    Running kubectl proxy creates a local proxy on port 8001 that forwards requests to the Kubernetes API server.

  2. Step 2: Identify the dashboard proxy URL

    The dashboard is accessed via the API server proxy path: /api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/ on localhost port 8001.

  3. Final Answer:

    http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/ -> Option B

  4. Quick Check:

    Dashboard URL after proxy = localhost:8001/api/v1/... [OK]
Hint: Dashboard URL uses kubectl proxy on localhost:8001 [OK]
Common Mistakes:
  • Using wrong port like 8080 or 6443
  • Trying HTTPS without proxy
  • Using a made-up domain name
4. You installed the Kubernetes dashboard but get a 403 Forbidden error when accessing it. What is the most likely cause?
medium
A. You did not create a login token or proper access permissions
B. The dashboard service is not running
C. kubectl proxy is not installed
D. Your browser does not support HTTPS

Solution

  1. Step 1: Understand 403 Forbidden meaning

    A 403 error means access is denied due to lack of permissions or authentication.

  2. Step 2: Check dashboard access requirements

    The dashboard requires a valid login token with proper RBAC permissions to allow access.

  3. Final Answer:

    You did not create a login token or proper access permissions -> Option A

  4. Quick Check:

    403 Forbidden = missing token or permissions [OK]
Hint: 403 means missing token or permissions [OK]
Common Mistakes:
  • Assuming service is not running without checking
  • Thinking kubectl proxy is missing (it's a client tool)
  • Blaming browser HTTPS support
5. You want to securely access the Kubernetes dashboard remotely without exposing it publicly. Which approach is best?
hard
A. Expose the dashboard service with a LoadBalancer type service
B. Disable authentication on the dashboard for easy access
C. Use kubectl proxy on your local machine and SSH tunnel to the cluster
D. Access the dashboard directly via the cluster IP from anywhere

Solution

  1. Step 1: Consider security for remote access

    Exposing the dashboard publicly or disabling authentication is insecure and not recommended.

  2. Step 2: Use kubectl proxy with SSH tunneling

    Running kubectl proxy locally and creating an SSH tunnel to the cluster securely forwards traffic without exposing the dashboard publicly.

  3. Final Answer:

    Use kubectl proxy on your local machine and SSH tunnel to the cluster -> Option C

  4. Quick Check:

    Secure remote access = kubectl proxy + SSH tunnel [OK]
Hint: Secure access = kubectl proxy plus SSH tunnel [OK]
Common Mistakes:
  • Exposing dashboard publicly with LoadBalancer
  • Disabling authentication for convenience
  • Trying to access cluster IP directly without security