Resource Requirements for Kubernetes for On-Premises Deployments in Customer-Controlled Regions

This section lists the various resources required to run PubSub+ Cloud in an Kubernetes environment in an on-premises Customer-Controlled Region. These requirements are beyond, or replace those specified in General Resource Requirements for Kubernetes and Default Port Configuration.

For more information, see the following:

Dynamic Volume Provisioning

PubSub+ 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, PubSub+ 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 PubSub+ 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.

Supported Storage Solutions

We have tested PubSub+ Cloud to work with the following storage solutions:

  • Portworx
  • Ceph
  • Cinder (Openstack)
  • vSphere storage for Kubernetes

Volume Performance Requirements

PubSub+ Cloud requires a storage backend that can providing the following performance:

Requirement Latency IOPS
Minimum 3 ms 1 K
Recommended 1 ms 10 K

The latency and IO operations per second are the most important considerations. Performance below the minimum threshold will severely impair guaranteed messaging performance.