{
	"id": "348cf8b0-c003-4b99-8184-8153dd6fce0a",
	"created_at": "2026-04-06T03:37:58.868864Z",
	"updated_at": "2026-04-10T03:21:05.283278Z",
	"deleted_at": null,
	"sha1_hash": "2f75af66c7d17a0de368533e622563a82bce45ee",
	"title": "Deploy and Access the Kubernetes Dashboard",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 1142212,
	"plain_text": "Deploy and Access the Kubernetes Dashboard\r\nArchived: 2026-04-06 03:17:20 UTC\r\nDeploy the web UI (Kubernetes Dashboard) and access it.\r\nKubernetes Dashboard is deprecated and unmaintained.\r\nThe Kubernetes Dashboard project has been archived and is no longer actively maintained. For new installations,\r\nconsider using Headlamp.\r\nDashboard is a web-based Kubernetes user interface. You can use Dashboard to deploy containerized applications\r\nto a Kubernetes cluster, troubleshoot your containerized application, and manage the cluster resources. You can\r\nuse Dashboard to get an overview of applications running on your cluster, as well as for creating or modifying\r\nindividual Kubernetes resources (such as Deployments, Jobs, DaemonSets, etc). For example, you can scale a\r\nDeployment, initiate a rolling update, restart a pod or deploy new applications using a deploy wizard.\r\nDashboard also provides information on the state of Kubernetes resources in your cluster and on any errors that\r\nmay have occurred.\r\nDeploying the Dashboard UI\r\nNote:\r\nhttps://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/\r\nPage 1 of 7\n\nKubernetes Dashboard supports only Helm-based installation currently as it is faster and gives us better control\r\nover all dependencies required by Dashboard to run.\r\nThe Dashboard UI is not deployed by default. To deploy it, run the following command:\r\n# Add kubernetes-dashboard repository\r\nhelm repo add kubernetes-dashboard https://kubernetes.github.io/dashboard/\r\n# Deploy a Helm Release named \"kubernetes-dashboard\" using the kubernetes-dashboard chart\r\nhelm upgrade --install kubernetes-dashboard kubernetes-dashboard/kubernetes-dashboard --create-namespace --names\r\nAccessing the Dashboard UI\r\nTo protect your cluster data, Dashboard deploys with a minimal RBAC configuration by default. Currently,\r\nDashboard only supports logging in with a Bearer Token. To create a token for this demo, you can follow our\r\nguide on creating a sample user.\r\nWarning:\r\nThe sample user created in the tutorial will have administrative privileges and is for educational purposes only.\r\nCommand line proxy\r\nYou can enable access to the Dashboard using the kubectl command-line tool, by running the following\r\ncommand:\r\nkubectl -n kubernetes-dashboard port-forward svc/kubernetes-dashboard-kong-proxy 8443:443\r\nKubectl will make Dashboard available at https://localhost:8443.\r\nThe UI can only be accessed from the machine where the command is executed. See kubectl port-forward --\r\nhelp for more options.\r\nNote:\r\nThe kubeconfig authentication method does not support external identity providers or X.509 certificate-based\r\nauthentication.\r\nWelcome view\r\nWhen you access Dashboard on an empty cluster, you'll see the welcome page. This page contains a link to this\r\ndocument as well as a button to deploy your first application. In addition, you can view which system applications\r\nare running by default in the kube-system namespace of your cluster, for example the Dashboard itself.\r\nhttps://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/\r\nPage 2 of 7\n\nDeploying containerized applications\r\nDashboard lets you create and deploy a containerized application as a Deployment and optional Service with a\r\nsimple wizard. You can either manually specify application details, or upload a YAML or JSON manifest file\r\ncontaining application configuration.\r\nClick the CREATE button in the upper right corner of any page to begin.\r\nSpecifying application details\r\nThe deploy wizard expects that you provide the following information:\r\nApp name (mandatory): Name for your application. A label with the name will be added to the\r\nDeployment and Service, if any, that will be deployed.\r\nThe application name must be unique within the selected Kubernetes namespace. It must start with a\r\nlowercase character, and end with a lowercase character or a number, and contain only lowercase letters,\r\nnumbers and dashes (-). It is limited to 24 characters. Leading and trailing spaces are ignored.\r\nContainer image (mandatory): The URL of a public Docker container image on any registry, or a private\r\nimage (commonly hosted on the Google Container Registry or Docker Hub). The container image\r\nspecification must end with a colon.\r\nNumber of pods (mandatory): The target number of Pods you want your application to be deployed in.\r\nThe value must be a positive integer.\r\nA Deployment will be created to maintain the desired number of Pods across your cluster.\r\nhttps://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/\r\nPage 3 of 7\n\nService (optional): For some parts of your application (e.g. frontends) you may want to expose a Service\r\nonto an external, maybe public IP address outside of your cluster (external Service).\r\nNote:\r\nFor external Services, you may need to open up one or more ports to do so.\r\nOther Services that are only visible from inside the cluster are called internal Services.\r\nIrrespective of the Service type, if you choose to create a Service and your container listens on a port\r\n(incoming), you need to specify two ports. The Service will be created mapping the port (incoming) to the\r\ntarget port seen by the container. This Service will route to your deployed Pods. Supported protocols are\r\nTCP and UDP. The internal DNS name for this Service will be the value you specified as application name\r\nabove.\r\nIf needed, you can expand the Advanced options section where you can specify more settings:\r\nDescription: The text you enter here will be added as an annotation to the Deployment and displayed in\r\nthe application's details.\r\nLabels: Default labels to be used for your application are application name and version. You can specify\r\nadditional labels to be applied to the Deployment, Service (if any), and Pods, such as release, environment,\r\ntier, partition, and release track.\r\nExample:\r\nrelease=1.0\r\ntier=frontend\r\nenvironment=pod\r\ntrack=stable\r\nNamespace: Kubernetes supports multiple virtual clusters backed by the same physical cluster. These\r\nvirtual clusters are called namespaces. They let you partition resources into logically named groups.\r\nDashboard offers all available namespaces in a dropdown list, and allows you to create a new namespace.\r\nThe namespace name may contain a maximum of 63 alphanumeric characters and dashes (-) but can not\r\ncontain capital letters. Namespace names should not consist of only numbers. If the name is set as a\r\nnumber, such as 10, the pod will be put in the default namespace.\r\nIn case the creation of the namespace is successful, it is selected by default. If the creation fails, the first\r\nnamespace is selected.\r\nImage Pull Secret: In case the specified Docker container image is private, it may require pull secret\r\ncredentials.\r\nhttps://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/\r\nPage 4 of 7\n\nDashboard offers all available secrets in a dropdown list, and allows you to create a new secret. The secret\r\nname must follow the DNS domain name syntax, for example new.image-pull.secret . The content of a\r\nsecret must be base64-encoded and specified in a .dockercfg file. The secret name may consist of a\r\nmaximum of 253 characters.\r\nIn case the creation of the image pull secret is successful, it is selected by default. If the creation fails, no\r\nsecret is applied.\r\nCPU requirement (cores) and Memory requirement (MiB): You can specify the minimum resource\r\nlimits for the container. By default, Pods run with unbounded CPU and memory limits.\r\nRun command and Run command arguments: By default, your containers run the specified Docker\r\nimage's default entrypoint command. You can use the command options and arguments to override the\r\ndefault.\r\nRun as privileged: This setting determines whether processes in privileged containers are equivalent to\r\nprocesses running as root on the host. Privileged containers can make use of capabilities like manipulating\r\nthe network stack and accessing devices.\r\nEnvironment variables: Kubernetes exposes Services through environment variables. You can compose\r\nenvironment variable or pass arguments to your commands using the values of environment variables.\r\nThey can be used in applications to find a Service. Values can reference other variables using the\r\n$(VAR_NAME) syntax.\r\nUploading a YAML or JSON file\r\nKubernetes supports declarative configuration. In this style, all configuration is stored in manifests (YAML or\r\nJSON configuration files). The manifests use Kubernetes API resource schemas.\r\nAs an alternative to specifying application details in the deploy wizard, you can define your application in one or\r\nmore manifests, and upload the files using Dashboard.\r\nUsing Dashboard\r\nFollowing sections describe views of the Kubernetes Dashboard UI; what they provide and how can they be used.\r\nNavigation\r\nWhen there are Kubernetes objects defined in the cluster, Dashboard shows them in the initial view. By default\r\nonly objects from the default namespace are shown and this can be changed using the namespace selector located\r\nin the navigation menu.\r\nDashboard shows most Kubernetes object kinds and groups them in a few menu categories.\r\nAdmin overview\r\nhttps://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/\r\nPage 5 of 7\n\nFor cluster and namespace administrators, Dashboard lists Nodes, Namespaces and PersistentVolumes and has\r\ndetail views for them. Node list view contains CPU and memory usage metrics aggregated across all Nodes. The\r\ndetails view shows the metrics for a Node, its specification, status, allocated resources, events and pods running\r\non the node.\r\nWorkloads\r\nShows all applications running in the selected namespace. The view lists applications by workload kind (for\r\nexample: Deployments, ReplicaSets, StatefulSets). Each workload kind can be viewed separately. The lists\r\nsummarize actionable information about the workloads, such as the number of ready pods for a ReplicaSet or\r\ncurrent memory usage for a Pod.\r\nDetail views for workloads show status and specification information and surface relationships between objects.\r\nFor example, Pods that ReplicaSet is controlling or new ReplicaSets and HorizontalPodAutoscalers for\r\nDeployments.\r\nServices\r\nShows Kubernetes resources that allow for exposing services to external world and discovering them within a\r\ncluster. For that reason, Service and Ingress views show Pods targeted by them, internal endpoints for cluster\r\nconnections and external endpoints for external users.\r\nStorage\r\nStorage view shows PersistentVolumeClaim resources which are used by applications for storing data.\r\nConfigMaps and Secrets\r\nShows all Kubernetes resources that are used for live configuration of applications running in clusters. The view\r\nallows for editing and managing config objects and displays secrets hidden by default.\r\nLogs viewer\r\nPod lists and detail pages link to a logs viewer that is built into Dashboard. The viewer allows for drilling down\r\nlogs from containers belonging to a single Pod.\r\nhttps://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/\r\nPage 6 of 7\n\nWhat's next\r\nFor more information, see the Kubernetes Dashboard project page.\r\nSource: https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/\r\nhttps://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/\r\nPage 7 of 7",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/"
	],
	"report_names": [
		"web-ui-dashboard"
	],
	"threat_actors": [],
	"ts_created_at": 1775446678,
	"ts_updated_at": 1775791265,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/2f75af66c7d17a0de368533e622563a82bce45ee.pdf",
		"text": "https://archive.orkl.eu/2f75af66c7d17a0de368533e622563a82bce45ee.txt",
		"img": "https://archive.orkl.eu/2f75af66c7d17a0de368533e622563a82bce45ee.jpg"
	}
}