Headlamp is a web-based interface for managing a cluster. It allows you to view cluster resources, manage them, and monitor application status without using kubectl.
Before installing the add-on, make sure that Nginx Ingress is installed in your cluster.
To verify that the add-on is installed correctly, run:
kubectl get pod -n headlamp
If the installation was successful, you will see a pod with the Running status.
After installation, the Headlamp icon will appear in the cluster control panel.

Click it to open the interface. If you are not authenticated, you will need to provide a token.
You can obtain the token from the Dashboard tab in the control panel by clicking Copy next to Dashboard token:

After authentication, the Headlamp interface will be displayed.

Headlamp interface
Main sections are:
If the Headlamp interface is exposed externally, it is recommended to configure additional basic authentication.
Headlamp does not support username and password authentication directly. Instead, basic authentication is configured at the ingress level.
Create a file with a username and password:
htpasswd -c auth admin
Here, admin is the username. You will be prompted to enter the desired password twice.
This command creates a file named auth.
If the htpasswd utility is not available, install the apache2-utils package.
Next, create a secret in the headlamp namespace using the generated file:
kubectl create secret generic headlamp-basic-auth \
--from-file=auth \
-n headlamp
Go to the Addons section in the cluster control panel and open the installed Headlamp add-on.
Enable advanced setup and locate the following block:
ingress:
enabled: true
annotations: {}
Remove {} next to annotations and add the required annotations:
ingress:
enabled: true
annotations:
nginx.ingress.kubernetes.io/auth-type: basic
nginx.ingress.kubernetes.io/auth-secret: headlamp-basic-auth
nginx.ingress.kubernetes.io/auth-realm: "Authentication Required"
Click Save and wait for the add-on to be updated.
After that, when accessing Headlamp, you will first be prompted for a username and password, and then for a token.
To change the password, create a new auth file and update the secret in the cluster.