How to Configure Rancher Break Glass Access
You set up rancher break glass access by creating a local admin user for outages. You store those emergency login keys in a safe vault until your main login fails. Most teams build this backup path so engineers can fix broken clusters during an outage. If you give out broad admin roles, one bad command can break a live cluster. How rancher break glass access works in native setups Rancher manages multiple Kubernetes clusters from one central control plane. In daily work, engineers log in thro
Your coding agents run with your access.
Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.
You set up rancher break glass access by creating a local admin user for outages. You store those emergency login keys in a safe vault until your main login fails. Most teams build this backup path so engineers can fix broken clusters during an outage. If you give out broad admin roles, one bad command can break a live cluster.
How rancher break glass access works in native setups
Rancher manages multiple Kubernetes clusters from one central control plane. In daily work, engineers log in through a central identity provider. That provider maps each person to a set of cluster roles. Sometimes the identity provider goes down or loses network links to the control plane. When that happens, engineers cannot log in through the normal path to fix the issue.
Teams prepare for this by setting up a local fallback user inside the control plane. This local user does not rely on external login tools. Teams also download fallback cluster files that talk right to the downstream Kubernetes API. These files let responders reach the cluster even if the main Rancher server fails. Security teams keep these files and passwords locked away during normal work hours.
When an incident starts, an on-call engineer asks to check out the emergency keys. Once they get the keys, they log in with full cluster admin rights. After the outage ends, the security team rotates the passwords and revokes the old keys.
What native emergency roles solve and what they miss
Native fallback accounts solve a major problem during a system outage. They make sure your team is never locked out of a failing cluster. Even if your identity provider or management server dies, responders can still log in. This setup handles the basic problem of who can enter the cluster during a crisis.
Still, native emergency roles leave a big gap once the session starts. A fallback account almost always holds full admin rights across the whole cluster. Once an engineer logs in, the system does not check single commands in flight. A stressed responder at three in the morning can delete a whole namespace by mistake. They can also read secret objects that hold customer emails, phone numbers, or card numbers.
Break-Glass Access Procedures + Rancher Access Control: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Native role rules only decide who gets in at the start of a session. They do not pause risky delete commands for a quick peer check. They also do not mask sensitive data in command results before it hits the screen.
How to manage emergency cluster sessions safely
To keep clusters safe during an incident, teams need control over single actions. Instead of handing out raw admin files, teams should route emergency work through one point. This setup lets responders run safe read commands right away to find the root cause.
When a responder needs to change a cluster resource, the system can check that action. Risky write or delete commands can wait for a quick approval from a second person. At the same time, data masking rewrites emails and card numbers in the output results. This keeps private data safe while the engineer fixes the broken app. Every command and output line goes into an audit log for the post-incident review. You get fast recovery during an outage without giving up control over live cluster actions.
Check database and API queries on the wire
Identity tools, roles, and network rules decide who opens a session. Setup alone cannot check what each query does or mask sensitive values in a response once a session starts. When workflows touch Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, or internal HTTP APIs, hoop.dev sits inline in the wire protocol beside those services as an open-source proxy, a sidecar for your Postgres or API. On every query an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human review.
Your login details and client tools stay as they are while hoop.dev guardrails refuse bad deletes or drops before they run, and hoop.dev data masking rewrites matched sensitive values in responses in memory. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and writes every query and decision to an audit trail that generates evidence for HIPAA, GDPR, and PCI DSS. See the source on GitHub.
Frequently asked questions
When should a team use rancher break glass access?
Teams should only use this path when the main login system or server is down. You should never use fallback admin accounts for daily cluster work or routine app updates.
How do you revoke emergency cluster keys after an outage?
After you fix the outage, an admin must rotate the local password right away. You also need to delete the old API tokens so no one can reuse them.
Why are static kubeconfig files risky for emergency use?
Static files often hold long-lived admin tokens that bypass central login checks. If someone copies the file to a laptop, they keep full admin rights without oversight.
Related guides
In this post