Skip to content
Netilion Extension Platform

Overview

For every application running on the NEXT platform, a project context is created by the NEXT team after discussing the customer requirements. The project context(aka configuration) is the central place where the access management and configuration of resources are managed.

The name of the project together with the responsible company is used as identifier of the project: [company]-[project-name]. The project configuration targets one environment of the NEXT platform, but can be cloned to the other environments.

For every project, a standard set of dedicated resources are created:

  1. A Kubernetes namespace with a reserved amount of compute resources
  2. A Key Vault for secret management
  3. Repositories in a subgroup in GitLab, to store deployment files for the applications

Access to the above mentioned Azure resources will be granted through a user group from the E+H Microsoft Entra ID(previously called Azure Active Directory), and to the GitLab resources is granted separately through a GitLab group. Both these groups can be managed independently by the project team.

NEXT Platform environments

We currently maintain a staging and production environment, hosted in the Azure data center in the West Europe region. Additionally, a production environment is planned to be setup in India. The European environments is connected to the respective staging and production environment of Netilion. For the Indian environment a new instance of Netilion will be setup.

Each environment has a dedicated Kubernetes cluster, a Kafka broker and an MQTT Broker. The GitLab instance egit and the container registry are shared across all environments.