Cohesity Kubernetes Backup
You set up a cohesity kubernetes backup by linking your cluster to the backup platform. This link uses a dedicated service account and cluster role to read state and volumes. Teams often grant broad admin rights to get backups running fast. Broad roles create risk when engineers or tools interact with live namespaces. How cohesity kubernetes backup works with cluster roles Kubernetes role-based access control uses four main objects to manage permissions. A Role sets permissions inside one spe
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 a cohesity kubernetes backup by linking your cluster to the backup platform. This link uses a dedicated service account and cluster role to read state and volumes. Teams often grant broad admin rights to get backups running fast. Broad roles create risk when engineers or tools interact with live namespaces.
How cohesity kubernetes backup works with cluster roles
Kubernetes role-based access control uses four main objects to manage permissions. A Role sets permissions inside one specific namespace. A ClusterRole sets permissions across the whole cluster and covers nodes or all namespaces. Permissions in Kubernetes are purely additive, which means there are no deny rules.
A RoleBinding grants permissions inside one namespace by referencing a Role or a ClusterRole. A ClusterRoleBinding grants permissions across the entire cluster at once. For a cohesity kubernetes backup to capture full apps, it needs a ClusterRoleBinding. The backup service account must read persistent volumes, secrets, and pod specs across namespaces.
To run pre-backup or post-backup scripts, the role also needs subresource permissions. In Kubernetes, subresources like pod logs or pod execution use a slash format. Granting create permissions on the pod execution subresource lets the backup tool run commands. It can freeze a database inside a pod before taking a volume snapshot.
Why native roles leave an operational gap during restores
Native Kubernetes roles solve the basic problem of who can talk to the API server. You can scope the backup service account so it only reads the resources it needs. This setup works well for automated jobs that run on a set schedule.
The operational gap appears when human engineers step in to test or fix a restore. During an incident, engineers need to inspect restored pods, check logs, and verify data. Native roles only check if a user can start a pod execution session. Once the session starts, Kubernetes does not check the commands running inside the shell.
An engineer checking a restored database pod might run a query that returns real customer data. Native roles also cannot mask sensitive fields like emails, phone numbers, or card numbers in flight. Also, the resource names restriction in Kubernetes does not block create calls on subresources. Teams often hand out broad namespace roles during recovery and forget to revoke them later.
Kubernetes RBAC + Backup Security: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Securing human access to backup namespaces and clusters
To keep backup and restore workflows safe, teams must separate machine roles from human roles. The backup tool keeps its scoped service account for snapshot jobs. Engineers who verify backups or fix failed restores need a different workflow.
Instead of giving engineers static cluster keys, teams should check every command and query in flight. When an engineer inspects a restored pod, the team needs a clear log of every action. Risky commands should require a quick approval from a peer before they run. Data masking should also rewrite sensitive fields like national IDs in query results during restore checks.
Govern kubectl and API calls in flight
Identity providers and Kubernetes RBAC decide who logs into a cluster. They cannot redact keys inside returned JSON objects or hold a risky delete call for review. By design, hoop.dev runs as an open-source proxy, a sidecar for your Kubernetes API, checking requests and responses without replacing RBAC.
First, hoop.dev guardrails refuse banned methods, paths, or headers before they run. Next, hoop.dev data masking rewrites sensitive keys in returned Secret, ConfigMap, and log responses in memory, and writes each decision to the audit trail. Explore the repo on GitHub.
Frequently asked questions
What permissions does a cohesity kubernetes backup need?
The backup tool needs a ClusterRole and ClusterRoleBinding to read cluster state and volumes. It also needs pod execution subresource permissions if it runs scripts inside containers.
Can Kubernetes RBAC block specific commands inside a restored pod?
No, Kubernetes RBAC only controls who can start an execution session on a pod. It does not inspect or block individual shell commands once the session is open.
Why are ClusterRoleBindings risky for human engineers during recovery?
A ClusterRoleBinding grants permissions across every namespace in the cluster with no deny rules. If an engineer gets this binding for a restore, they can read secrets across all apps.
Short role checks help teams work fast. Simple rules make each review clear. Good logs keep every team safe. Scoped keys stop bad changes early.
Related guides
In this post