Skip to content
Netilion Extension Platform

Quickstart

Quickstart: Migrate your applications to Azure

  1. Reach out to the Netilion Platform team, to request a new project in Azure. Once the requirements are collected, the following resources will be provisioned for deployment -

    1. A kubernetes namespace, with a reserved amount of compute resources
    2. Keyvault(s) for secret management
    3. Data persistence, based on thr requirements of the project(redis, for example)
    4. Repositories in Gitlab to store helm charts of the project
    5. An Azure AD group for access management to the kubernetes cluster
    6. A container registry repository, to store the docker image(s)
    7. Any additional resources that might need to be provisioned based on the requirements of the project.

    At the end of this step, you should have access to the Azure portal to find your resources, and Gitlab(egit.endress.com) to find the deployment repositories.

  2. Once a project is created, first thing to do, would be to change your existing build pipeline to push your image(s) to the JFrog Artifactory repository provided to you during project creation. Please connect with us to receive the token to login to the artifactory.

  3. The next step would be to pull this image. In order to pull the image, you have to edit the helm chart(s)(usually the templates/deployment.yaml and values.yaml) in Gitlab to fit your project requirements. See here for more details about the template provided, and here is more information about the container registry(JFrog artifactors) we use.

  4. Once you have the helm chart configured to pull the correct image, and the kubernetes resources set, the next step would be to add environment variables and secrets to the Deployment as required by your application. The secret values should be added to the Keyvaults provided earlier, and here you will find documentation on how to add them, and how to synchronize them to your chart.

  5. If your project must be accessed from the internet, it will be through a Web Application Firewall. If mentioned in the requirements of the project, you will also get a ‘label´, to add as a selector to your helm resources. See here for more information. Here you can find documentation on how routing works.

  6. If you use redis cache, pleae check this information on how to configure.

  7. If you use Kafka, please check this information

  8. If you use MQTT broker, please check this information

  9. Once you are satisfied with your configuration of helm chart and templates, you can push the files to the respective branches per environment(´weu-qas´, for staging for example) and a deployment pipeline will start, to deploy the helm chart.

  10. Once the app is successfully deployed, you can login to azure to find your pods and services - more information here. Logs and metrics will be available in Logzio - more information here.