Deployment Architecture Upgrade

This document outlines the steps required for migrating the deployment architecture from V2 to V3.

Step 1: New environment setup with V3 Architecture

This is required for migration from V2 to V3 architecture

  1. Make sure to have all the pre-requisites ready as per the details present in the section pre-requisites

  2. Setup Wireguard Bastion host

  3. Setup wireguard client in your local and complete the configuration

  4. Observation cluster’s nginx setup

  5. Observation cluster applications setup

  6. Observation cluster keycloak-rancher integration

  7. MOSIP k8 cluster configuration

  8. MOSIP cluster nginx setup

  9. Setting up Monitoring for MOSIP cluster

  10. Setting up Alerting for MOSIP cluster

  11. Setting up Logging for MOSIP cluster

Step 2: Deployment of external services

(Required for V2 to V3 architecture migration)

  1. Setup postgres server

    Note:

    i. Deploy postgres server in a seperate node.

    ii. Make sure postgres initialisation is not done (only install postgres).

  2. Setup Keycloak server

    Note: Make sure keycloak initialisation is not done (only install keycloak).

  3. Setup Softhsm

  4. Setup ClamAV

  5. Setup ActiveMQ

  6. Setup docker registry secrets if you are using private dockers.

    Note: These instructions are only applicable if you need to access Private Docker Registries. You may disregard them if all of your Docker containers are downloaded from the public Docker Hub.

  7. Setup Captcha for the required domains.

  8. Setup Landing page for new MOSIP cluster.

Step 3: Backup and restoration of external services

This step is required for V2 to V3 architecture migration.

  1. Softhsm (only required if softhsm is used instead of real HSM)

    i. Backup keys

    ii. Restore old key

    iii. Update softhsm ida and softhsm kernel security pin

  2. Postgres

    i. Export

    ii. Import

    iii. secret creation

    iv. Increase postgres max_connections to 1000

  3. Keycloak

    i. Export

    ii. Import

  4. Minio

    i. Export the existing Minio as directory

    ii. Clone Minio

  5. Kafka

    i. setup external minio for backup.

    ii. backup kafka

    iii. restore kafka

  6. Conf-secrets

Update the secrets in existing secrets in conf-secrets namspace.

  1. Packets in landing to be copied from old environment to the upgraded environment or same NFS folder can be mounted to regproc packet server and group 1 stage groups. Refer here for more details.

  • dmz-sc.yaml

  • dmz-pkt-pv.yaml

  • dmz-pkt-pvc.yaml

  • dmz-landing-pv.yaml

  • dmz-landing-pvc.yaml

Last updated

Copyright Β© 2021 MOSIP. This work is licensed under a Creative Commons Attribution (CC-BY-4.0) International License unless otherwise noted.