Get started with Infinite File Storage, a shared file system without fixed capacity limits
As services grow, operating file storage becomes more than simply securing enough capacity. Multiple servers need to read and write the same files, access methods vary by operating system, and data must be separated by team or application. When rapidly growing data is added to the equation, an operating plan based on a fixed storage capacity can quickly reach its limits.
Infinite File Storage, newly added to KakaoCloud File Storage, is a scalable shared file system designed for these environments. You can create multiple shared volumes in a single file system, and both SMB and NFS protocols are supported so files can be shared across various client environments, including Windows, Linux, and macOS.
As of May 2026, Infinite File Storage is provided as Beta. During the Beta period, some features, availability, and operating policies may change. Before applying it to a production environment, check the latest documentation and service announcements.
Why do you need a shared file system?
File-based workloads remain essential to many services. This is because many types of data must preserve file and directory structures, such as user-uploaded content, documents managed by operations teams, application logs and analytics data, and configuration files referenced by multiple servers.
If this data is distributed across each server's local disk, operational complexity increases. File replication or synchronization between servers becomes necessary, and it is difficult to consistently manage the latest file state and access permissions. Especially in environments where multiple Virtual Machine instances or Kubernetes Engine clusters need to use the same data, a shared file system can significantly reduce operational burden.
Key features of Infinite File Storage
Infinite File Storage is a file system focused on operating according to actual usage and sharing structure, rather than creating storage after estimating a large capacity in advance.
1. Scalable structure without fixed capacity limits
An Infinite file system is provided as a scalable structure that can be used without a fixed storage size limit. It is suitable for services where data growth is difficult to predict, or environments where file storage volume fluctuates greatly during specific periods such as events or seasons. You can reduce the burden of allocating excessive spare capacity or repeatedly planning expansions whenever storage runs low. Because billing is also based on actual usage, you can manage the cost structure more flexibly.
2. Simultaneous support for SMB and NFS
Infinite File Storage provides SMB and NFS file services. You can use NFS for Linux/UNIX-based servers and SMB for Windows-based environments, choosing the protocol that fits the operating system and workload characteristics.
NFS: Suitable for configuring shared volumes for Linux servers, Kubernetes Engine workloads, analytics, and batch applications. For the mount procedure, see Mount an NFS file system.SMB: Suitable for Windows-based work environments and user- or group-based file sharing integrated with Active Directory. For the mount procedure, see Mount an SMB file system.
SMB file systems can be configured for user- and group-level permission management based on Active Directory integration, making them useful for collaborative storage within an organization or department-specific shared folders.
3. Manage multiple shared volumes in one file system
In Infinite File Storage, you can create multiple shared volumes in a single file system. A shared volume is a logical storage unit used to separate data by service or application, and each volume provides an independent access point. For how to create and configure permissions, see Manage shared volumes.
For example, you can divide volumes in one Infinite file system as follows.
| Shared volume | Example use |
|---|---|
content-prod | Store production content used by a service |
content-stage | Store content for review and staging environments |
analytics-input | Store source files used for analytics jobs |
team-share | Shared folder for an operations team or collaborating organization |
With this configuration, you can operate one file system while separating data boundaries and access paths by workload.
4. Access control by file service type
An important part of a shared file system is "who can access it, from where, and with what permissions." Infinite File Storage provides different access control methods depending on the file service type.
NFS: Configure access permissions based on IP addresses or IP rangesSMB: Configure shared volume access permissions by user or group
For NFS-based workloads, you can restrict the access scope based on the IP addresses of application servers or Kubernetes Worker Nodes. To use it as a dynamic persistent volume in Kubernetes, also see Configure NFS Client Provisioner. For SMB-based workloads, you can control shared folder access based on your organization's user and group permission policies.
Comparison of the two file systems
KakaoCloud File Storage provides Infinite file systems and Basic file systems depending on the use case. Both are shared file systems, but they are suited to different operating models.
| Category | Infinite file system | Basic file system |
|---|---|---|
| Capacity structure | Scalable structure without fixed limits | Based on capacity configured in advance, up to 16 TiB |
| Billing method | Based on actual used capacity | Based on created capacity |
| Protocols | SMB, NFS | NFS |
| Sharing structure | Multiple shared volumes can be created in one file system | Operated by file system |
| Access control | SMB account-based, NFS IP-based | NFS IP-based |
| Suitable environment | Environments where data growth is difficult to predict and multiple shared volumes and multi-OS access are required | Environments that need to operate an NFS-based file system reliably within a fixed capacity |
If you need to set capacity in advance and operate simply based on NFS, Basic file system is suitable. Conversely, if data growth is difficult to predict, or you need multiple shared volumes and the option to use SMB or NFS, consider Infinite file system.
Things to check before you start
Before adopting Infinite File Storage, review the following items first.
- Client operating system and protocol: Prioritize NFS for Linux/UNIX systems and SMB for Windows-based environments.
- Network access path: Check whether the Virtual Machine instances, Kubernetes Worker Nodes, and Windows clients that access the file system can communicate in the same network environment.
- Access control criteria: Design policies based on IP addresses for NFS and user or group permissions for SMB.
- Shared volume separation criteria: Decide how to divide shared volumes by service, environment, team, and data type.
- File operation patterns: Design the directory structure to avoid large-scale file creation and deletion, recursive commands, or excessive concentration of files in a single directory.
Before creating an SMB file system, you must also check the prerequisites for Active Directory integration. A domain name, DNS server, service account with domain join permissions, network ports, and other items are required. See SMB file system prerequisites and File system service ports.
Wrap-up
Infinite File Storage Beta is a new option for operating file-based workloads more flexibly. Its scalable structure without fixed capacity limits, usage-based billing, support for SMB and NFS, multiple shared volumes, and access control features can be applied to service data sharing, collaborative storage, Kubernetes shared volumes, and file-based analytics data storage.
For detailed concepts and usage, see the File Storage documentation.
Thank you.