Overview and Architecture

Overview

• MOSIP modules are deployed as microservices in a Kubernetes cluster.

• Wireguard is used as a trust network extension to access the admin, control, and observation panes.

• In case of on-field registration, WireGuard is extended to the registration client machines as one of the sources of trust.

• MOSIP uses Nginx server for:

  • SSL termination

  • Reverse Proxy

  • CDN/Cache management

  • Load balancing

• Kubernetes cluster is administered using the Rancher and rke tools.

• We have two Kubernetes clusters:

Observation cluster - This cluster is part of the observation plane and assists with administrative tasks. By design, this is kept independent from the actual cluster as a good security practice and to ensure clear segregation of roles and responsibilities. As a best practice, this cluster or its services should be internal and should never be exposed to the external world.

• Rancher is used for managing the MOSIP cluster.

• Keycloak in this cluster is used to manage user access and rights for the observation plane.

• It is recommended to configure log monitoring and network monitoring in this cluster.

• In case you have an internal container registry, then it should run here.

MOSIP cluster - This cluster runs all the MOSIP components and certain third-party components like the kafka, keycloak etc.

• MOSIP External Components

• MOSIP Services

Architecture diagram

Deployment repos

These are the repos that we would use for installing and configuring the MOSIP deployment. For detailed steps, please follow the guide. This section is for reference.

• k8s-infra : contains the scripts to install and configure a Kubernetes cluster with required monitoring, logging, and alerting tools.

• mosip-infra : contains the deployment scripts to run charts in a defined sequence.

• mosip-config : contains all the configuration files required by the MOSIP modules.

• mosip-helm : contains packaged Helm charts for all the MOSIP modules.