₹200 free credit when you verify after signup, plus your first recharge doubled. Terms
Guides

Open the Kubernetes Dashboard on a BookMyHost cluster

Every managed Kubernetes cluster can open the standard Kubernetes Dashboard from the panel, with no kubeconfig on your laptop and nothing to install in the cluster. You sign in to the panel as usual, press one button, and a dashboard tab opens for that cluster.

By the BookMyHost Cloud team · Published · Updated · Prices read live from the BookMyHost Cloud rate card, in INR, excluding GST.

See VPS plansHourly billing, GST invoice, live in under a minute.

Open it from the panel

  1. Open the cluster

    In the panel go to Kubernetes and open the cluster. The cluster must be active.

  2. Choose the access level

    Press Open dashboard. Tick Read-only if you only want to look: a read-only session can view objects but cannot change them. Without it the session is admin, with the same power as your kubeconfig.

  3. Use the new tab

    The dashboard opens in a new tab on its own address, kd- followed by a random session name and then .bookmyhost.com. You are signed in already; there is no token to paste.

Who can open it

You need a panel login with permission to manage the cluster (owner, admin or technical role). Billing and viewer members cannot open it. Resellers and our staff acting on a client account can open it for that client, and every open and close is written to the audit log.

The dashboard address always ends in bookmyhost.com, also for clients of a reseller with a white-label panel. The dashboard itself carries no BookMyHost branding.

How a session ends

A session ends when you close it from the panel, sit idle for a while, reach its hard time limit, or lose the right to manage the cluster. Access through the panel stops at once. The credentials the session used inside the cluster stop working within about 10 seconds, because the cluster keeps a short cache of tokens.

Open a new session from the panel whenever you need one. You can keep a few sessions open per cluster at a time.

What it does not cover

  • Panel login only: the dashboard cannot be opened with an API key or through MCP, because it is a browser session. API keys and MCP can still read cluster details and download the kubeconfig where the key has the role.
  • Pod shells work, but through plain HTTP streaming rather than WebSockets, so a long idle shell may reconnect.
  • The dashboard keeps working during an upgrade, with a warning banner. Resize and restore wait until the upgrade ends.
FAQ

Questions on this guide

What address does the Kubernetes Dashboard open on?

On a kd- address under bookmyhost.com made just for that session: kd- followed by a random name and then .bookmyhost.com. Each session has its own address, so one session can never read another one's cookie.

What is the difference between admin and read-only?

Admin has the same rights as the cluster admin kubeconfig. Read-only maps to the built-in view role: you can look at workloads, logs and events but not create, edit or delete anything, and secrets stay out of view.

How fast does a session end when I close it?

Access through the panel ends immediately. The cluster tokens behind the session stop working within about 10 seconds. Closing the browser tab alone does not end the session; close it from the panel.

Can I open the dashboard with an API key or from MCP?

No. Opening the dashboard needs a panel login, because it creates a browser session with its own cookie. API keys and MCP have no endpoint for it.

Do I need to install the dashboard in the cluster?

No. Clusters come with the dashboard already installed. The panel adds only a few small service accounts in its own namespace, bmh-system, which you should leave alone.

Try it on hourly billing

Start small, resize in place, switch to a term when the workload settles. GST invoice either way. Every new account starts with ₹200 of free credit.

Build a server
WhatsApp