Optimized for:

Before you start (requirements)

You need:

• Compressed folder: SmartGatewayHelmChart.zip
• Kubernetes 1.19+
• Helm 3.0+
• Cluster access (kubectl configured)
• Docker Hub token (Docker Hub Token will be provided by the Onibex Team)
• PersistentVolume provisioner (MySQL and DataSyncHub)
• Cloud-specific controllers/CSI drivers (LoadBalancer + Storage)

Verify tooling:

• kubectl version --client
• helm version
• kubectl get nodes

1. EKS (AWS)

Go to your EKS resources and connect to CloudShell by selecting the icon as shown in the image.

Verify your AWS identity:

Execute the next command: aws sts get-caller-identity

List your EKS clusters in the region where they were created.

Run the following command, replacing the region with the one where your cluster is located:

aws eks list-clusters --region us-east-2

Configure kubectl access to your EKS cluster (update kubeconfig)

Run the following command and replace CLUSTER_NAME with the name of the cluster you want to select, as shown in the image:

aws eks update-kubeconfig --region us-east-2 --name CLUSTER_NAME

1.2) Prepare the chart

• Select the option, manage files
  

• Upload the ZIP folder

• Run the following command to extract the ZIP file

2. Install Strimzi Operator

Strimzi is the Kubernetes operator that manages Kafka clusters declaratively. It must be installed and running before any Kafka resources are applied.

Step 2.1 — Install via Helm

Step 2.2 — Verify Operator Health

Important

Do not proceed to Step 2 until the strimzi-cluster-operator pod shows 1/1 Running. The operator must be healthy before it can process Kafka resources.

3. Deploy Kafka Stack

Deploy the full Kafka stack: Kafka 4.2 in KRaft mode (not compatible with ZooKeeper), Confluent Schema Registry 7.6.0, and Kafka Connect.

Kafka Connect is the component that runs connectors to external databases and platforms such as MySQL and DataBricks.

Phase 1 — Deploy the Kafka Cluster

Replace [your-docker-token] with your Docker Hub personal access token before running this command.

Wait until all four pods are Running before moving to Phase 2:

helm install oneconnect . --namespace oneconnect --create-namespace --values values-aws.yaml --set dockerHub.token=YOUR_TOKEN --set networking.loadBalancer.type=external --timeout 15m

Note: Don't forget to insert your token in the command

• First, verify that the pods are healthy; To verify this, execute the following command

# List all pods in the oneconnect namespace

kubectl get pods -n oneconnect

# For additional details (including restart count and current status)

kubectl get pods -n oneconnect -w

• You should see something like:

Verify the services and get the external IP:

# View all services

kubectl get svc -n oneconnect

• Look specifically for the internal-frontend service. You should see something like:

• Access the platform: Once you have the EXTERNAL-IP, open it in your browser:

For example, if the IP is a33bd3f701d5e442abc9828d940699d7-289592184.us-east-2.elb.amazonaws.com:

http://a33bd3f701d5e442abc9828d940699d7-289592184.us-east-2.elb.amazonaws.com:5050

NOTE: These same steps are valid for the multi-cloud support functionality in EKS (AWS) or GKE (GCP)