Kubernetes dashboard - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Kubernetes dashboard?

The Kubernetes dashboard is a web-based user interface that allows you to manage and monitor your Kubernetes clusters easily without using command-line tools.

beginner

How do you access the Kubernetes dashboard securely?

You access the Kubernetes dashboard securely by creating a proxy with the command kubectl proxy and then opening the dashboard URL http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/ in your browser.

intermediate

What is the purpose of a Service Account in the Kubernetes dashboard?

A Service Account provides the dashboard with permissions to access cluster resources. It defines what the dashboard can see and do inside the cluster.

beginner

Which command installs the Kubernetes dashboard in your cluster?

You install the Kubernetes dashboard using: kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml.

intermediate

Why should you use Role-Based Access Control (RBAC) with the Kubernetes dashboard?

RBAC controls who can access the dashboard and what actions they can perform, helping to keep your cluster secure by limiting permissions.

What is the main function of the Kubernetes dashboard?

A Monitor network traffic only

B Provide a web interface to manage Kubernetes clusters

C Store container images

D Replace kubectl command-line tool

The Kubernetes dashboard provides a web interface to manage and monitor Kubernetes clusters easily.

Which command starts a proxy to access the Kubernetes dashboard locally?

A kubectl proxy

B kubectl dashboard start

C kubectl run proxy

D kubectl access dashboard

The command kubectl proxy creates a secure tunnel to access the dashboard locally.

What does a Service Account do for the Kubernetes dashboard?

A Runs the dashboard server

B Stores dashboard configuration files

C Defines dashboard permissions in the cluster

D Manages container images

A Service Account defines what the dashboard can access and do inside the Kubernetes cluster.

How do you install the Kubernetes dashboard?

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

B kubectl install dashboard

C docker pull kubernetes/dashboard

D kubectl create dashboard

You install the dashboard by applying the official YAML file with kubectl.

Why is RBAC important for the Kubernetes dashboard?

A It updates the dashboard automatically

B It speeds up the dashboard loading time

C It manages container storage

D It controls user permissions for security

RBAC controls who can access the dashboard and what they can do, enhancing cluster security.

Explain how to securely access the Kubernetes dashboard from your local machine.

Think about creating a secure tunnel and the URL you open in your browser.

Describe the role of Service Accounts and RBAC in managing Kubernetes dashboard permissions.

Consider how Kubernetes controls who can do what inside the cluster.

Practice

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