Bosca / Kubernetes

Bosca Kubernetes

Your clusters,
in your platform.

A full Kubernetes console, built into Bosca Studio. Register your clusters, watch their state stream in live, and operate your workloads — with kubeconfigs that stay on the server, never in the browser.

How it works

Register, watch, operate.

01

Register

Upload a cluster's kubeconfig. Bosca encrypts it, keeps it on the server, and connects through the controller.

02

Watch

Health, nodes, pods, and events stream into Studio — logs and metrics tick in real time as they happen.

03

Operate

Scale, restart, delete, and apply — every action gated to admins, checked at every layer.

What you can do

A real console, not a dashboard

View, stream, and operate — every registered cluster, every workload, and the resources around them, from inside the platform you already run.

Multi-cluster

Register every cluster and switch between them from one console — the switcher follows you across the subsystem.

Live fleet health

Nodes, capacity, and a healthy / degraded / failing badge per cluster, kept current.

Workloads

Deployments through CronJobs — scale, restart, delete, and apply a manifest, right from the table.

Live pod logs

Stream a pod's logs and metrics over a live connection, with pause and clear.

Config & secrets

ConfigMaps and Secrets, with a Secret's values kept masked — its keys are all you see.

Networking & Gateway API

Services, Ingresses, and Network Policies, plus Gateways and their HTTPRoutes.

Operators

The operators you run get first-class views — cert-manager certificates and CloudNativePG Postgres clusters.

Credentials stay server-side

The controller holds every kubeconfig; the browser gets data about your cluster, never the credentials.

Live, not polled

State that streams in

The console holds a live connection open instead of making you reload. A pod's logs ride a Kubernetes watch and land as it writes them; its CPU and memory, and the cluster's capacity, are sampled on a live interval and pushed straight to you. Switch clusters and the streams follow.

  • Pod logs ride a Kubernetes watch, arriving as they're written.
  • Pod and cluster metrics are sampled live and pushed to you.
  • The stream reconnects on its own, and shows its state.
  • Pause or clear the log view without dropping the stream.
pod · web-7c9 · logsstreaming
12:04:01 GET /api/health 200 3ms
12:04:01 GET /api/feed 200 41ms
12:04:02 cache hit · feed:home
12:04:02 POST /api/track 202 2ms

Secure by design

Credentials that never leave the server

A cluster's kubeconfig is encrypted at rest and lives only on the server — the controller decrypts it in memory to make a call, and the browser only ever receives data about your cluster, never the credentials. And every operation is gated to a Bosca administrator — checked on the server, then checked again at the controller.

  • Kubeconfigs are encrypted and stay on the server.
  • The browser gets cluster data, never the credentials.
  • Every read, write, and stream is gated to an admin.
  • That gate holds at every layer, not just the UI.
admin gate
resolveradmin check
streamre-checked every 60s
controlleradmin check

Your clusters, where your platform is

One console for every cluster — live, secure, and part of the platform you already run, not another tool on the side.