How to Manage Files on Kubernetes with NebuaCloud Drive

Kubernetes is very good at running applications and surprisingly poor at holding onto files. The storage it provides is designed to be attached to a single application, not browsed, organized, or shared by a person. So the moment a team needs to share a document, hand a client an export, or park some media somewhere sensible, they reach for an unrelated tool - a personal cloud drive, an email attachment, a separate storage account.

Drive is NebuaCloud's answer to that gap: file storage that lives alongside your infrastructure instead of outside it. This article covers what it does today.

Why files don't fit the Kubernetes model

Kubernetes storage is built for applications, not people:

• Storage is normally tied to one application and disappears or moves with it
• There's no built-in way to browse folders, search, or organize files by hand
• There's nowhere natural to put a database export, a migrated site's media, or a file a colleague needs to download

So teams bolt on a separate storage product for anything that isn't consumed directly by an application. It works, but it's one more account, one more set of logins, and one more thing disconnected from where the actual infrastructure lives.

What file storage should give you

• Files that outlast any one application - they survive restarts, redeployments, and changes
• A way to browse and organize - folders, search, drag-and-drop - not just a technical interface
• Controlled sharing - hand a file to someone outside your company without giving them access to your platform
• Storage that scales with your plan, not an open-ended bill
• No setup - available the moment you need it

How Drive works

Each organization gets its own private storage, created automatically the first time you open the Drive tab - nothing to configure or connect first. Organizations that want dedicated storage can install one from the Marketplace, and Drive uses it directly.

What's available today

• Browse and organize - a full file browser for folders and files
• Drag-and-drop upload - with live progress, including many files at once
• Copy and move - between folders, including nested ones
• Search everywhere - find a file across all your storage, not just the current folder
• Trash bin - deleted files are recoverable; restore or permanently delete
• Shareable links - optionally password-protected, optionally with an expiry date, for handing a file to someone outside your company
• Usage tracking - see how much of your storage you've used
• Plan-based limits - storage is capped by plan rather than unlimited by default

A concrete example

A team needs to hand a database export to a client who has no access to the platform:

1. Drag the file into Drive - progress shows live.
2. Create a share link, set a password, and set it to expire in 7 days.
3. Send the link. The client downloads the file without needing an account.
4. When it's no longer needed, delete it - it goes to trash first, so an accidental delete isn't final.

Where Drive is headed

Today Drive is a standalone, general-purpose file store for your organization. The next step is connecting it to other parts of the platform that produce files - the clearest case being WordPress migration, where a site's media library is currently exported but has to be moved into place by hand. See How to Migrate a WordPress Site to Kubernetes. Drive is the obvious home for that media, but the two aren't linked automatically yet.

The takeaway

Kubernetes doesn't give teams a good place for files that people - not applications - need to work with. Drive fills that gap with browsing, sharing, and organization on top of durable per-organization storage that needs no setup. It's a complete file storage product today; the deeper integration with workflows like migration is where it's going next.

Try it with NebuaCloud -> deploy in minutes

Current Availability

Note: Drive is fully shipped: browsing, drag-and-drop upload with progress, copy and move, search, a trash bin, password- and expiry-protected share links, and plan-based storage limits are all live today, with private per-organization storage available by default or a dedicated instance from the Marketplace.

Drive is not yet integrated with other platform workflows that produce files, such as WordPress migration - that connection is a roadmap direction, not a current feature.