Azure - OneConnect Deployment and Configuration

Azure - OneConnect Deployment and Configuration

One Connect Platform: Kubernetes Azure Deployment Manual for Private Network

This manual outlines the steps required to deploy the One Connect system on a Kubernetes cluster within a Private Network (meaning the OneConnect Platform will not be accessible from the internet) using an automated script. The process configures the necessary services, deployments, and resources to ensure the system functions properly.

Prerequisites

Before you begin, ensure the following requirements are met:

  • You have access to the Kubernetes cluster where the system will be deployed.

  • You have downloaded the deployment package: OneConnect Kubernetes

  • A bash shell available to run the script.

  • You have the necessary permissions to execute scripts in the deployment environment.

  • The terminal where the script is executed must have Docker installed in order for the deployment to function correctly.


Installation Steps


1. Creating Kubernetes Service

  1. Log in to Azure services
  1. Select Kubernetes Services services.

  1. Create a new Kubernetes cluster.

  1. The subscription will be selected in project details.
  2. Add a new resource group with a name that can be identified in next steps.

  1. In cluster details, select the Azure instance size (for a POC we recommend selecting Dev/Test; for production environment we recommend Production Economy).

  1. Select the region where you want to deploy the cluster and leave the other options by default, unless a specific option is needed.

  1. In this step of nodes, if necessary, additional nodes can be added (there is no One Connect restriction on the number of nodes required).

  1. Ultimately, Review + create, review the details of the new cluster to be created.
  2. In the conceptual testing network section, it is possible to leave the default options unless a specific configuration for the deployment network is required.
  3. For input and output traffic between pods, the network policy must be configured in 'none', since all pods interact with each other. If the cluster requires a specific network policy, the traffic that will be allowed between pods should be reviewed individually.
  4. Once the networking section is reviewed, press Create and the cluster can be created by One Connect. The above sections are needed.
The following screens will be observed while the cluster is created.


Once the creation process is completed, the new cluster can be viewed in the list of Kubernetes services.


To run the deployment, click the Connect button


Next, click on "Open Cloud Shell"

With Cloud Shell open, upload the file you previously downloaded as requested in the prerequisites



2. Extract the Deployment Archive

First, extract the contents of the .zip file in the data and control panel in Kubernetes:

unzip oneconnectkubernetes.zip

Navigate to the extracted directory:

cd oneconnect-kubernetes

3. Configure the .env file 

Open the oneconnect.env file using the "nano" command (i.e. nano oneconnect.env) and update the environment variables according to your deployment needs.

For advanced Kubernetes configurations, refer to the following manual.

Finally, save your configurations by clicking Ctrl + X, and then select yes by typing the "Y" key; Enter.
Note
The DOCKERHUB_TOKEN variable will be provided by the Onibex Sales team. Make sure to request it in advance, as it is required to download the Docker images before starting the deployment.
4. Run the setup.sh Script
Grant execution permissions to the script (if not already set):
  1. chmod +x generate-deployments.sh
  2. chmod +x setup.sh
Run the following scripts
  1.  ./generate-deployments.sh
After the previous one, run the following
  1. ./setup.sh
 If you are unable to execute the script, make sure to install dos2unix and then run the script again. You can install it and convert the script using the following commands:
sudo apt-get install dos2unix
sudo yum install dos2unix
dos2unix setup.sh 
dos2unix oneconnect.env
dos2unix generate-deployments.sh
./setup.sh
5. Viewing and Using External IP
After creating the Internal Load Balancer, a service named internal-frontend will appear in your system (make sure to check "Services"). In this row, an additional IP address will be displayed in the "External IP" column, next to the internal IP. This external IP should be used to access the portal on port 5050.

Welcome to OneConnect Cloud!
Your new OneConnect Cloud access portal in Azure, available on port 5050, is ready for use.
Example IP:http://00.00.000:5050



Idea
To start working with your newly deployed SmartGateway, refer to the following manuals





    

    • Related Articles
      • 

    • Azure - One Connect Deployment Prerequisites
      Before you Begin: The following deployment manuals assumes a basic understanding of Kubernetes concepts. For more information, refer to Kubernetes core concepts for Azure Kubernetes Service (AKS). Before you begin: If you don't have an Azure account, ...
      • 

    • OneConnect - Docker Deployment Guide
      OneConnect – Docker Deployment Guide This article explains how to deploy OneConnect using Docker on a Linux virtual machine. 1) Prerequisites Before starting the deployment, make sure you meet the following requirements: Download the compressed files ...
      • 

    • One Connect Cloud Deployment
      Prerequisites Download the required .zip folders attached at the end of the document: sql.zip one-connect.zip kafka-compose.zip Requirements for the Virtual Machine System: Linux Architecture: 64-bit processors (x86_64) support Instance ...
      • 

    • OneConnect - SmartGateway Network Architecture
      The SmartGateway Network architecture provides a secure and scalable connectivity layer between on-premise systems, cloud environments, and modern data platforms. It ensures reliable data exchange across AWS Customer Account, Onibex, and SAP Rise, ...
      • 

    • AWS - EKS EC2 One Connect Deployment Manual with Terraform
      This manual provides step-by-step instructions for deploying an Amazon EKS (Elastic Kubernetes Service) cluster using Terraform. It includes the configuration of essential components such as AWS credentials, infrastructure provisioning, EBS CSI ...
      •