Longhorn Cluster
You set up a longhorn cluster by installing its storage parts onto your Kubernetes nodes. It turns local disks across your servers into shared block storage for your apps. Most teams install the tool with a standard chart or manifest file. They then link Kubernetes role rules to control who can manage volumes. When teams give out broad admin roles, any user can delete live disks or read snapshots. How a longhorn cluster works on Kubernetes A longhorn cluster runs as a set of containers inside
Cluster: the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
You set up a longhorn cluster by installing its storage parts onto your Kubernetes nodes. It turns local disks across your servers into shared block storage for your apps. Most teams install the tool with a standard chart or manifest file. They then link Kubernetes role rules to control who can manage volumes. When teams give out broad admin roles, any user can delete live disks or read snapshots.
How a longhorn cluster works on Kubernetes
A longhorn cluster runs as a set of containers inside your Kubernetes system. It uses a manager part on each node to watch disks and volume claims. When a pod asks for storage, the manager builds an engine for that single volume. It also makes copies of the data across different nodes to keep files safe. If one server goes down, another node takes over the volume right away.
Because each volume has its own small engine, one bad disk will not break other apps. Teams can take point-in-time snapshots or send backups to remote object storage. You control all of these storage tasks through standard Kubernetes custom resources or a web dashboard. Access to these storage controls relies on the native role rules inside Kubernetes.
Setting up roles and permissions for storage teams
To lock down your storage, you bind Kubernetes roles to user groups in your identity tool. You can grant read-only rights so developers can check volume health without changing disk settings. Platform admins get write rights to create storage classes, run backups, and fix broken nodes. You should also lock down the web dashboard so it does not sit open on the network.
Many teams share a single admin config file during late-night incidents to fix disk issues fast. Once several people hold that same key, you lose track of who ran which storage action. Even with separate user roles, Kubernetes role rules are broad by nature. A user with rights to fix one volume often gets rights to change every volume in that namespace.
Cluster: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
What native storage roles solve and what they miss
Native Kubernetes roles do a good job of deciding who can enter the cluster. They stop random users from opening the storage dashboard or listing volume secrets. They also let you separate read tasks from write tasks at the resource level. For basic setup work, these built-in rules give you a solid first wall of defense.
Still, native role checks stop working once a user logs in and starts a session. The system decides who can connect, not what individual commands or requests do in flight. An engineer with valid edit rights can still wipe a production volume by mistake. Standard logs show that an API call happened, but they often miss the full human context. Teams also struggle when a support engineer needs temporary write rights for just ten minutes. Granting and removing static role bindings by hand takes too much time and leaves old rules behind.
Govern statements and responses across databases and APIs
Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev runs beside each supported service as an open-source proxy, a sidecar for your database or API.
First, hoop.dev guardrails block banned queries before they run. Then hoop.dev data masking rewrites matched sensitive values in responses in memory. The audit trail records every statement and verdict per resource. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.
Frequently asked questions
What does a longhorn cluster do for stateful apps?
It gives stateful apps reliable block storage using the local disks on your Kubernetes nodes. It copies volume data across nodes so pods keep their files if a server fails.
How do you back up data in this storage system?
You can take local snapshots inside the cluster or send volume backups to external object storage. If a whole cluster fails, you can restore those backups to a new set of nodes.
Why are Kubernetes roles not enough for storage security?
Kubernetes roles only check if a user has general rights to a resource type. They do not review single commands in flight or remove temporary access on their own.