To evaluate the services Streaming Data Manager offers, we recommend creating a test environment and using our demo application. This way you can start over any time, and try all the options you are interested in without having to worry about changes made to your existing environment, even if it’s not used in production. You can also use the free edition of Streaming Data Manager for evaluation.
Production installation is very similar, but of course you won’t need to deploy the demo application, and you must exactly specify which components you want to use.
Before deploying Streaming Data Manager on your cluster, complete the prerequisites.
CAUTION:To install Streaming Data Manager on an existing Service Mesh Manager installation, the cluster must run Service Mesh Manager version 1.11 or later. If your cluster is running an earlier Service Mesh Manager version, you must upgrade it first.
Supported providers and Kubernetes versions
The cluster must run a Kubernetes version that Service Mesh Manager supports: Kubernetes 1.21, 1.22, 1.23, 1.24.
Service Mesh Manager is tested and known to work on the following Kubernetes providers:
- Amazon Elastic Kubernetes Service (Amazon EKS)
- Google Kubernetes Engine (GKE)
- Azure Kubernetes Service (AKS)
- Red Hat OpenShift 4.11
- On-premises installation of stock Kubernetes with load balancer support (and optionally PVCs for persistence)
Calisti resource requirements
Make sure that your Kubernetes or OpenShift cluster has sufficient resources to install Calisti. The following table shows the number of resources needed on the cluster:
|CPU||- 32 vCPU in total
- 4 vCPU available for allocation per worker node (If you are testing on a cluster at a cloud provider, use nodes that have at least 4 CPUs, for example, c5.xlarge on AWS.)
|Memory||- 64 GiB in total
- 4 GiB available for allocation per worker node for the Kubernetes cluster (8 GiB in case of the OpenShift cluster)
|Storage||12 GB of ephemeral storage on the Kubernetes worker nodes (for Traces and Metrics)|
These minimum requirements need to be available for allocation within your cluster, in addition to the requirements of any other loads running in your cluster (for example, DaemonSets and Kubernetes node-agents). If Kubernetes cannot allocate sufficient resources to Service Mesh Manager, some pods will remain in Pending state, and Service Mesh Manager will not function properly.
Enabling additional features, such as High Availability increases this value.
The default installation, when enough headroom is available in the cluster, should be able to support at least 150 running
Pods with the same amount of
Services. For setting up Service Mesh Manager for bigger workloads, see scaling Service Mesh Manager.
CAUTION:When using Streaming Data Manager on Amazon EKS, you must install the EBS CSI driver add-on on your cluster.
- To install Streaming Data Manager from the command line, see Install SDM from the command line.
- To install Streaming Data Manager using GitOps methods, see Install SDM - GitOps.
- To install the Streaming Data Manager demo application, see Recommendations demo application.
Note: Streaming Data Manager components are installed into the