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

2.1) Prepare the chart

• Select the option, manage files

• Upload the ZIP folder

• Run the following command to extract the ZIP file

unzip SmartGatewayHelmChart.zip 

 
cd helm-deployment   # folder where Chart.yaml exists

2.2) Install (choose your cloud) 

Note: datasynchub namespace is created automatically. 

Then, execute this command

helm install oneconnect . \
 --namespace oneconnect \
 --create-namespace \
 --values values-aws.yaml \
 --set dockerHub.token=YOUR_TOKEN

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)