- Manage StreamNative Clusters
StreamNative Cloud Clusters Overview
Use this topic to understand the cluster concepts in StreamNative Cloud.
Instances & Clusters
StreamNative Cloud organizes its clusters into Instances. Within any StreamNative Cloud organization, it is possible to host one or more Pulsar Instances. Each Pulsar Instance serves as a dedicated environment within a cloud provider, capable of hosting multiple Pulsar clusters along with various deployed components such as Connectors, Functions, etc. This setup allows different departments or teams to operate in separate instances to prevent overlap and interference.
A Pulsar Instance can be either fully Hosted on StreamNative's cloud account or on your own public cloud account through the Bring-Your-Own-Cloud (BYOC) deployment option.
Within each Pulsar Instance, multiple Pulsar clusters can be deployed across various regions. Each cluster within a Pulsar Instance is deployed to a specific cloud region as configured in its cloud provider settings. Furthermore, each Pulsar cluster provides various service endpoints to enable client libraries to connect, produce and consume messages, execute functions, run connectors, and perform SQL queries.
Clusters within a Pulsar instance can also replicate data among themselves using geo-replication.
StreamNative Cloud utilizes Public Cloud infrastructure to host Pulsar instances and clusters. Below is a diagram illustrating the relationship between Pulsar instances, clusters, and the cloud infrastructure:
Infrastructure Pools
As illustrated above, StreamNative Cloud infrastructure is organized into infrastructure pools. Each pool encompasses a collection of infrastructure environments, known as pool members, distributed across multiple regions within a cloud provider. These members can be equated to Kubernetes clusters dedicated to deploying Pulsar clusters.
A Pulsar Instance can be created within and deployed to a specific infrastructure pool. Each infrastructure pool can support multiple Pulsar Instances. When setting up a Pulsar Instance, you select the appropriate pool using its namespace and name. Within each Pulsar Instance, you can deploy clusters to various regions by specifying the desired region. StreamNative Cloud then deploys the Pulsar Cluster to the corresponding pool member in that region.
The type of Pulsar Instance, whether Hosted or BYOC, is determined by the location and configuration of its Infrastructure Pool. Infrastructure Pools can either be fully Hosted by StreamNative or set up in your own public cloud account through the BYOC deployment option.
Hosted Infrastructure Pools
Hosted Infrastructure Pools are fully managed and maintained on StreamNative's cloud account. These pools are pre-provisioned, and you can utilize them when setting up your Pulsar Instances and Clusters. Information on available Hosted Pools can be accessed through the StreamNative Cloud Console.
BYOC Infrastructure Pools
BYOC Infrastructure Pools must be provisioned prior to deploying any BYOC Pulsar Instances or Clusters. The setup process for a BYOC Pool includes establishing a Cloud Connection—this allows the StreamNative Cloud control plane to interact with your cloud account. It also involves defining and provisioning Pool Members within the Pool to deploy Pulsar Clusters across different regions of your cloud account. Provisioning Pool Members within a Pool is done by creating Cloud Environments in different regions. Each Cloud Environment defines the essential infrastructure resources such as compute, storage, and networking, that are necessary for a Pool Member to deploy Pulsar clusters.
Related Content
- Learn more information about cluster types and available regions, see Cluster Types and Regions.
- Learn more about how to provision & manage BYOC infrastructure pools, see Manage BYOC Infrastructure.
- Learn more about how to manage StreamNative instances, see Manage Instances.
- Learn more about how to manage StreamNative clusters, see Manage Clusters.