Superstream "Bring Your Own Cloud" is the perfect solution for customers who prefer or can't have an external connection from outside their cloud to their Kafka clusters.
Step 1: Check out our "Environment Readiness Checklist"
Step 2: Deploy
Superstream is using a Helm chart to deploy its agent.
You can deploy as many agents as needed and spread your clusters between them based on your environmental preferences.
The Superstream chart will deploy the following pods:
2 Superstream engines
2 Superstream auto-scaler instances
1 Telegraf agent for monitoring
1. Configure the custom_values.yaml file
You can always get your superstreamAccountId and superstreamActivationToken through the console or within the automatic email you received when you signed up.
custom_values.yaml
############################################################
# GLOBAL configuration for Superstream Agent
############################################################
global:
agentName: "" # Define the superstream agent name within 32 characters, excluding '.', and using only lowercase letters, numbers, '-', and '_'.
superstreamAccountId: "" # Provide the account ID associated with the deployment, which could be used for identifying resources or configurations tied to a specific account.
superstreamActivationToken: "" # Enter the activation token required for services or resources that need an initial token for activation or authentication.
2. Deploy
Head over to the custom_values.yaml file location and run:
Appendix C - Deploy Superstream Engine using labels, tolerations, nodeSelector and etc'
To inject custom labels into all services deployed by Superstream, utilize the global.labels variable.
############################################################
# GLOBAL configuration for Superstream Agent
############################################################
global:
agentName: "" # Define the superstream agent name within 32 characters, excluding '.', and using only lowercase letters, numbers, '-', and '_'.
superstreamAccountId: "" # Provide the account ID associated with the deployment, which could be used for identifying resources or configurations tied to a specific account.
superstreamActivationToken: "" # Enter the activation token required for services or resources that need an initial token for activation or authentication.
labels:
tests: ok
To configure tolerations, nodeSelector, and affinity settings for each deployed service, the adjustments in the following example need to be done:
############################################################
# GLOBAL configuration for Superstream Agent
############################################################
global:
agentName: "" # Define the superstream agent name within 32 characters, excluding '.', and using only lowercase letters, numbers, '-', and '_'.
superstreamAccountId: "" # Provide the account ID associated with the deployment, which could be used for identifying resources or configurations tied to a specific account.
superstreamActivationToken: "" # Enter the activation token required for services or resources that need an initial token for activation or authentication.
superstreamAgent:
tolerations:
- key: "app"
value: "connectors"
effect: "NoExecute"
autoScaler:
tolerations:
- key: "app"
value: "connectors"
effect: "NoExecute"
telegraf:
tolerations:
- key: "app"
value: "connectors"
effect: "NoExecute"
Appendix D - Deploy Superstream from local registry
To deploy Superstream from local registry, override default values using global.image variable in custom.valuesfile:
############################################################
# GLOBAL configuration for Superstream Agent
############################################################
global:
agentName: "" # Define the superstream agent name within 32 characters, excluding '.', and using only lowercase letters, numbers, '-', and '_'.
superstreamAccountId: "" # Provide the account ID associated with the deployment, which could be used for identifying resources or configurations tied to a specific account.
superstreamActivationToken: "" # Enter the activation token required for services or resources that need an initial token for activation or authentication.
image:
# Global image pull policy to use for all container images in the chart
# can be overridden by individual image pullPolicy
pullPolicy:
# Global list of secret names to use as image pull secrets for all pod specs in the chart
# secrets must exist in the same namespace
# https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
pullSecretNames: []
# Global registry to use for all container images in the chart
# can be overridden by individual image registry
registry:
Best practices
Dev / Staging environments
Connecting your Development/Staging Kafka Clusters to Superstream is recommended. This can be done using either one or more dedicated Superstream engines (data planes) for each environment or the same engine connected to the production clusters.
Review the to ensure your environment is ready for deployment and to avoid potential issues.
Create a custom_values.yaml file and edit the relevant values (An example can be found ).
