The connectivity model refers to the network access and permissions that allow your Kubernetes cluster and event broker services to function correctly. The types of connectivity you need to consider in your deployment are:
- Messaging Connectivity: The connectivity required for messaging traffic (between event broker services and from applications to event broker services).
- Management Connectivity: The connectivity required for you to administer your event broker services using the Solace CLI, Broker Manager, or SEMP.
- Operational Connectivity: The connectivity required to set up your Kubernetes cluster and launch event broker services.
Messaging Connectivity
Messaging Connectivity refers to the way messaging clients access the event broker services. A messaging client can connect in three ways: via the public internet, via private IP addresses, or via a hybrid of both.
- Public Internet: Messaging clients connect to the event broker service endpoints over the public internet.
- Private IP Addresses: Messaging clients connect to the event broker service endpoints via private routes inside the customer's network.
- Hybrid: Messaging clients in internal networks and in the customer's cloud networks connect via network peering.
Your approach to messaging connectivity may influence the ownership model you choose. In Dedicated Regions, Solace uses network peering for messaging connectivity. We use the peering solutions listed below when configuring the network options for messaging connectivity:
- VPC peering on GCP
- VNet peering on Azure
- VPC peering or Transit Gateway (controlled availability) on AWS
If you require a different form of networking for your messaging connectivity, you can choose to deploy to a Customer-Controlled Region where you have control over network configuration. For a summary of how different deployment options can be combined, see Deployment Options Comparison.
For details about messaging connectivity and its use cases, see Management Connectivity for Event Broker Services and Messaging Connectivity for Outbound Connections and Client Applications.
Management Connectivity
Management Connectivity is required so that you can administer your event broker services. This category includes connectivity:
- over SSH to the Solace CLI
- from a browser to PubSub+ Broker Manager
- from applications to the event broker services using SEMP (requires the correct ports enabled)
For details about messaging connectivity, see Management Connectivity for Event Broker Services.
Operational Connectivity
Operational Connectivity refers to the network access you need to set up your Kubernetes cluster and launch event broker services. This includes connectivity from:
- the Kubernetes cluster to the Solace Container Registry (this is optional; you can use a mirror repository instead)
- the Datadog Agent to Datadog Home
- the Mission Control Agent to everything (Home Cloud, event broker services, Kubernetes cluster, Amazon S3)
For details about operational connectivity, see Operational Connectivity.