kbridge

Give your team kubectl, not kubeconfigs

kbridge sits between people and Kubernetes clusters. Users run kubectl-style commands with no cluster credentials, and every command is checked against their role, run as them, and recorded.

Get started View on GitHub

Self-hosted and open source · Apache 2.0 · Alpha, v0.3.1-alpha.1

A developer works with kubectl syntax, is refused where the role says no, and the admin sees every attempt.

What changes

Kubernetes cluster access without kubeconfigs or a VPN

Giving an engineer access usually means handing out a credential or opening a network path. kbridge puts a control plane between people and clusters, so you do neither.

Instead of a kubeconfig per developer, per cluster

No credentials on laptops

Users sign in to the control plane. Cluster credentials never leave the agent, and access is revoked in one place.

Instead of a VPN, a bastion or a public endpoint

No inbound ports

Each cluster's agent dials out to the control plane, so there is nothing inbound to open or maintain.

Instead of a shared credential that hides who did what

Every command runs as the person

The agent impersonates kbridge:<email>, so Kubernetes RBAC and the cluster's own audit log see the user, not the agent.

Instead of stitching together logs from several clusters

One audit log across every cluster

Who ran which command where, and whether it ran. Refused commands are recorded too.

Automation and AI agents

Kubernetes access for AI agents: an account, not a credential

An automation or AI agent with its own kbridge account holds no cluster credential. Every command it runs is checked against its role and recorded under its name, so you can see exactly what it did and what it was refused.

# the agent, signed in as deploy-bot@example.com $ kb scale deploy web --replicas=3 -n team-a deployment.apps/web scaled $ kb delete pod x -n kube-system Error: permission denied: delete pod in namespace "kube-system" on cluster "staging" is not allowed for deploy-bot@example.com; ask a kbridge admin to extend your role # what the admin sees: kb admin audit USER CLUSTER STATUS COMMAND deploy-bot@example.com staging success scale deploy web --replicas=3 -n team-a deploy-bot@example.com staging denied delete pod x -n kube-system

How it works

How kbridge controls kubectl access

  1. Each cluster runs a small agent

    It dials out to the control plane over gRPC. No inbound port is opened and no kubeconfig leaves the cluster.

  2. Users run kb with kubectl syntax

    The CLI sends their login token and the command to the control plane. There is nothing new to learn.

  3. The control plane checks the command

    The user's role decides. Nothing reaches a cluster without passing this one check, and a refusal says why and who can help.

  4. The agent runs kubectl as the user

    It impersonates kbridge:<email>, so the cluster's RBAC and audit log see the person, not the agent.

  5. The attempt is recorded

    Whether it ran or was refused: user, cluster, command and outcome, in the kbridge audit log.

Admin console

An audit log and admin console for every kubectl command

A read-only web console ships inside the control plane. It makes no third-party requests.

  • Cluster connection and policy sync state
  • The audit log with filters and CSV export
  • Agent tokens, and users with their roles and access

Security in brief

Kubernetes access security in three facts

  1. Users never hold a cluster credential

    Only the agent inside the cluster does, and it never hands it out.

  2. Commands run as the user

    Through impersonation, so Kubernetes RBAC still applies and the cluster's audit log names the person.

  3. Every attempt is recorded

    Allowed or refused, in one audit log across every cluster.

Read the security model →

Coming next

What's next for kbridge

Not in v0.3.1-alpha.1 yet. Each card says how far along it is.

In development

Guardrails

Rules that evaluate the command itself before it is forwarded, so a destructive operation is refused or needs a reason.

In development

Just-in-time access

Request a role for a bounded window with a reason. Someone approves, and it expires on its own.

Planned

Single sign-on

OIDC login, so people sign in with the identity provider they already have.

See the roadmap →

FAQ

Questions about kubectl access with kbridge

What is kbridge?

kbridge is an open-source, self-hosted access gateway for Kubernetes. Users run kubectl commands through the kb CLI without holding cluster credentials. A control plane checks each command against the user's role, an agent inside the cluster runs it as that user, and every attempt is recorded.

How do I give someone kubectl access without a kubeconfig?

Create a kbridge account for them and bind it to a role. They install kb, log in, and run kubectl commands. No kubeconfig is created or distributed: the cluster credentials stay with the agent inside the cluster.

Does kbridge need inbound firewall rules or a VPN?

No. The agent in each cluster opens an outbound connection to the control plane, so nothing inbound is opened on the cluster. Users only need to reach the control plane.

How does kbridge audit kubectl commands?

Every attempt is recorded with the user, cluster, namespace, command and outcome, whether it ran or was refused. Admins read it with kb admin audit or in the admin console. Commands run as the user, so the cluster's own audit log names the person too.

Does kbridge work with Kubernetes RBAC?

Yes. The agent runs each command as kbridge:<email> through impersonation, so Kubernetes RBAC applies to every request. The agent also keeps the cluster's RoleBindings in step with the kbridge policy.

Can AI agents and CI pipelines use kbridge?

Yes. Give each one its own kbridge account. It holds no cluster credential, every command it runs is checked against its role, and the audit log records what it did under its own name.

Which kubectl commands work through kbridge?

kb takes kubectl syntax, including streaming commands such as logs -f, exec -it and port-forward. There is nothing new to learn.

Is kbridge free and open source?

Yes. kbridge is open source under the Apache 2.0 license and self-hosted: one control plane and one small agent per cluster, installed with Helm.

Start here

Get started with kbridge

Run your own kbridge

The Helm quick start puts the control plane and an agent on one cluster. It works on a local kind cluster.

Helm quick start →

Take it to production

Secrets, TLS and more clusters. Then the security checklist, onboarding users, and operations.

Production install →

You have an account

Your admin gave you a URL, an email and a password. Install kb, log in, and run commands.

CLI reference →