Storage Requirements in Customer-Controlled Clusters
You must ensure that your Kubernetes cluster provides for the event broker service's ephemeral and persistent storage requirements:
- Ephemeral Storage Requirements
-
- 2.25 GiB per event broker service node.
- Persistent Storage Requirements:
-
-
20 GiB for event broker service related data.
-
Additional persistent storage based on default message spool size for an event broker service class size. If you configure your spool sizes to be larger than default, you must have sufficient persistent storage to meet the custom spool size. For more information, see Configuring Message Spool Sizes.
-
Solace Cloud requires the use of dynamic volume provisioning. For more information, see Dynamic Volume Provisioning.
The tables below summarize the ephemeral and persistent storage requirements of an event broker service, by class and version. For more information, see:
Dynamic Volume Provisioning
Solace Cloud requires dynamic volume provisioning, which is requested through Persistent Volume Claims managed by Kubernetes StatefulSets. This requirement requires that the infrastructure provide a storage backend that is supported by one of the Kubernetes' storage plugins. In addition, Solace Cloud requires a block storage backend for dynamic volume provisioning (we do not support filesystem-based backends).
-
You must format your disks with XFS.
-
Solace does not support the Network File System (NFS) protocol as part of your storage solution with Solace Cloud
-
To accomplish data encryption at rest for the software event broker messages and configuration, the storage backend must provide encrypted volumes. The event broker service itself does not provide data encryption at rest.
If you are deploying Solace Cloud to an on-premises Customer-Controlled Cluster, you must consider the supported storage solutions and volume performance requirements. For more information, see Dynamic Volume Provisioning in Resource Requirements for Kubernetes for On-Premises Deployments in Customer-Controlled Clusters.
Event Broker Service Ephemeral Storage Requirements
The following table lists the ephemeral storage requirements for event broker services. The ephemeral storage requirement is on a per-event broker basis (one for Enterprise-100 Standalone
| Service Class | Ephemeral Storage Request Limit | |
|---|---|---|
| Per Event Broker Service Node | Per Event Broker Service | |
| Enterprise-100 Standalone | 2.25 GiB | 2.25 GiB |
| Standalone Enterprise 250 to Enterprise 100K | 2.25 GiB | 2.25 GiB |
| High availability Enterprise 250 to Enterprise 100K | 2.25 GiB | 6.75 GiB |
Event Broker Service Persistent Storage Requirement
The following table lists the event broker service's persistent storage requirement based on the data requirement of the event broker service itself. The persistent storage requirement for data is on a per-event broker basis (one for Enterprise-100 Standalone
| Event Broker Service Data Requirement | ||
|---|---|---|
| Enterprise-100 Standalone
|
High Availability Event Broker Service | |
| Per Event Broker Service Messaging Node | Per High Availability Event Broker Service | |
| 20 GiB | 20 GiB | 40 GiB |
Event Broker Service Default Message Spool Size Requirements
The following table
-
The Enterprise-100 Standalone service class is a standalone messaging node (requires one pod). The Enterprise 250 High Availability and all larger High Availability Service Classes are HA groups, which require two messaging pods (primary and backup) and one monitoring pod.
-
The numbers in the table below do not account for the 20 GiB of space required for data related to the event broker itself. This requirement is outlined in Event Broker Service Persistent Storage Requirement.
The tables below provide the persistent disk space requirements for:
Note that standalone event broker services are not available by default. Contact Solace for more information.
Volume Size for High Availability Event Broker Services
The table below lists the minimum required persistent disk space requirement for an event broker service based on the default spool size for a given service class.
| Service Class | Message Spool Size | Persistent Disk Space Requirement |
|
|---|---|---|---|
| Version 10.7.1 to version 10.10.1 |
Version 10.11.1 and later |
||
| Enterprise 250 | 50 GB | 65 GiB x 2 | 64 GiB x2 |
| Enterprise 1K | 200 GB | 260 GiB x 2 | 256 GiB x 2 |
| Enterprise 5K | 400 GB | 520 GiB x 2 | 512 GiB x 2 |
| Enterprise 10K | 600 GB | 780 GiB x 2 | 780 GiB x 2 |
| Enterprise 50K | 800 GB | 1040 GiB x 2 | 1024 GiB x 2 |
| Enterprise 100K | 1000 GB | 1300 GiB x 2 | 1300 GiB x 2 |
Volume Size for Standalone Event Broker Services
The table below lists the minimum required persistent disk space requirement for a standalone event broker service based on the default spool size for a given service class. Note that standalone event broker services are not available by default. Contact Solace for more information.
The numbers in the table below do not account for the 20 GiB of space required for data related to the event broker itself. This requirement is outlined in Event Broker Service Persistent Storage Requirement.
| Service Class | Message Spool Size | Persistent Disk Space Requirement |
|
|---|---|---|---|
| Version 10.7.1 to version 10.10.1 |
Version 10.11.1 and later |
||
| Enterprise-100 Standalone | 25 GB | 35 GiB | 32 GiB |
| Enterprise 250 Standalone | 50 GB | 45 GiB | 64 GiB |
| Enterprise 1K Standalone | 200 GB | 240 GiB | 256 GiB |
| Enterprise 5K Standalone | 400 GB | 500 GiB | 512 GiB |
| Enterprise 10K Standalone | 600 GB | 760 GiB | 780 GiB |
| Enterprise 50K Standalone | 800 GB | 1020 GiB | 1024 GiB |
| Enterprise 100K Standalone | 1000 GB | 1280 GiB | 1280 GiB |