Add ability to run Kyma Dashboard locally

Description

Add the ability to run the Kyma Dashboard locally.
In the previous CLI, there was a kyma dashboard command that was responsible for running the Kyma Dashboard Docker image locally and automatically passing the kubeconfig to the Kyma Dashboard (as far as I remember, it was pushed on the public/kubeconfig/kubeconfig.yaml path, and the user was logged in using the kubeconfigID path).

Reintroducing this capability would allow users to quickly access the dashboard without manually setting up and configuring Docker containers.

Reasons

Improves developer experience by restoring a useful CLI command that was available in the past.
Simplifies the process of running Kyma Dashboard locally, especially for new contributors and users.
Reduces manual steps of configuring Docker and kubeconfig, minimizing chances of user error.
Provides an easy way to test and interact with Kyma clusters in a local development environment.

Attachments

Busola documentation: Run Kyma Dashboard via Docker

@pbochynski

If adjustments are needed in Busola, please ping me. Also, if you have other suggestions to fix this problem, please contact me or @pbochynski. We are open to discussion.

@mrCherry97

@mrCherry97 would it run on arm architecture?

when I tried the command, I got an erroro that there is no image for arm

docker run --rm -it -p 3001:3001 -v "${KUBECONFIG}":/app/core-ui/kubeconfig/$(basename "${KUBECONFIG}") --pid=host --name busola europe-docker.pkg.dev/kyma-project/prod/busola:latest

Unable to find image 'europe-docker.pkg.dev/kyma-project/prod/busola:latest' locally
latest: Pulling from kyma-project/prod/busola
docker: no matching manifest for linux/arm64/v8 in the manifest list entries

If we expose it in cli, we will expose the problem.
Please build a mutli-arch image

there was no usecase for multiarch, so we removed it (faster build), but now the usecase exist, so we will bring it back.

@kwiatekus

@kwiatekus PR is merged, I see on post that everything is working, so images are multiarch. Please clear my assaginee.

kyma dashboard - inteactive, opens browser
kyma dashboard start starts in background, opens browser (if container exists, doesnt create new)
kyma dashboard stop stops the background container

Here is the code from the previous implementation:
https://github.com/kyma-project/cli/blob/release-2.20/pkg/dashboard/dashboard.go

It was used like this:
https://github.com/kyma-project/cli/blob/release-2.20/cmd/kyma/dashboard/cmd.go#L52

kyma dashboard start starts in background, opens browser (if container exists, doesnt create new)

I propose not to open the browser by default. In my opinion, we should just start a new container and print the localhost address in the terminal, on which address Busola is available. Of course, we can implement a flag like --open to automatically open the browser if expected.

@vicslavova

Previously browser was opening automatically, also as a user I'm expecting Kyma Dashboard to open after running the command. Maybe that will be a good question to UX @vicslavova

Agree with Mateusz - My guess is that if the user is starting a local dashboard, their final goal is to have the dashboard open. So, let's cover the more common use case and open it automatically on kyma dashboard start. Even if on a rare occasion it turns out that the user just wanted to start it and not open it, I think it won’t be such a pain for them to close it.

This issue is blocked until kyma-project/busola#4553 is resolved, due to busola blocking local ip adresses.

Navigation Menu

Repository navigation

Add ability to run Kyma Dashboard locally #2554

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Add ability to run Kyma Dashboard locally #2554

Description

Activity

mrCherry97 commented on Aug 21, 2025

kwiatekus commented on Oct 17, 2025

mrCherry97 commented on Oct 17, 2025

mrCherry97 commented on Oct 21, 2025

kwiatekus commented on Oct 23, 2025

pPrecel commented on Oct 23, 2025

pPrecel commented on Dec 11, 2025

mrCherry97 commented on Dec 12, 2025

vicslavova commented on Dec 15, 2025

FilipRudy commented on Jan 23, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions